LCP
Largest Contentful Paint
3.0s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Purge Unused CSS Rules
How to optimize shutoffware.com
Purge Unused CSS Rules
Medium Impact+4 points estimated
Why It Matters
95% of your CSS file is unused, wasting 14KB of network bandwidth and blocking rendering.
How to Fix
Use PurgeCSS or similar tools to remove unused styles from your build process. Implement critical CSS extraction to inline above-the-fold styles. Consider CSS-in-JS solutions to automatically scope styles to used components only.
0Good
What This Score Means
A score of 90 falls in the "Good" range (50-89). While it is better than poor (0-49), you should aim for 90+ to provide an optimal user experience and maximize SEO benefits.
This site is slower than approximately 35% of similar sites. The main issues affecting performance are image optimization, JavaScript execution time, and layout stability.
Addressing these issues could improve your conversion rate by 15-20% and boost your search engine rankings.
Core Web Vitals Analysis
INP
Interaction to Next Paint
16ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.00
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This website has excellent performance with a score of 90/100, but still has room for improvement in Core Web Vitals timing. The biggest issue is slow content loading, with First Contentful Paint taking 2.7 seconds and Largest Contentful Paint reaching 3.0 seconds, which may feel sluggish to users. The site is loading nearly 46KB of unused JavaScript (47% waste) and 15KB of unused CSS (95% waste), which could save an estimated 300ms in loading time if optimized. Removing this dead code and potentially optimizing the network dependency chain that currently takes 320ms could significantly improve the user experience and push this site into the high-90s performance range.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+8 points estimatedWhy It Matters:
47% of your main JavaScript bundle is unused, wasting 300ms on LCP and 45KB of bandwidth.
How to Fix:
Use webpack-bundle-analyzer to identify unused code in your main bundle. Implement code splitting to load only required modules per route. Consider dynamic imports for features that aren't immediately needed on page load.
Optimize Critical Request Chain
High Impact+6 points estimatedWhy It Matters:
Your longest network chain takes 320ms through 4 levels of dependencies, delaying page rendering.
How to Fix:
Move the Firebase API call out of the critical rendering path by loading it after initial render. Preload essential JavaScript modules using <link rel="modulepreload">. Consider inlining critical CSS to reduce the dependency on external stylesheets.
Keep Your Site Fast After Optimization
Once your site is optimized, maintain that speed. Use DeployHQ for zero-downtime, automated deployments—so performance fixes and updates go live safely every time, without breaking your site.
Explore DeployHQ →Trusted by engineering teams shipping high-performance sites
Want to Analyze YOUR Website?
Get AI-powered performance insights with actionable fixes in 30 seconds
Related Performance Analyses
More Generic Speed Tests
Generic Performance Resources
Optimize Critical Request Chain
Your longest network chain takes 320ms through 4 levels of dependencies, delaying page rendering.
Optimize Network Request Chain
Your critical resource chain spans 4 levels deep, creating unnecessary delays in content rendering.
Reduce Network Chain Dependencies
Long dependency chains create waterfall loading that extends total page load time to over 20 seconds.
Optimize CSS Bundle Size
95% of your CSS (14 KiB) is unused, adding 300ms to LCP and wasting bandwidth.