LCP
Largest Contentful Paint
3.8s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize CSS Bundle Size
How to optimize shutoffware.com
Optimize CSS Bundle Size
Medium Impact+8 points estimated
Why It Matters
95% of your CSS (14 KiB) is unused, adding 300ms to LCP and wasting bandwidth.
How to Fix
Implement critical CSS extraction to inline above-the-fold styles. Use PurgeCSS or UnCSS to remove unused CSS rules from your stylesheet. Consider CSS-in-JS or CSS modules to load only component-specific styles.
0Needs Improvement
What This Score Means
A score of 83 falls in the "Needs Improvement" 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
19ms
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 good overall performance with a score of 83/100, but there are some significant optimization opportunities. The biggest issue is excessive unused JavaScript (133 KB of waste) that's slowing down page loading, particularly affecting the Largest Contentful Paint which takes 3.8 seconds - much slower than the recommended 2.5 seconds. The site is also loading 14 KB of unused CSS that could be removed or deferred. Cleaning up this unused code could potentially save over 1 second in loading time and provide a much snappier user experience.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+12 points estimatedWhy It Matters:
133 KiB of unused JavaScript delays LCP by 750ms and blocks the main thread unnecessarily.
How to Fix:
Analyze your build process to eliminate dead code from index-CfoOKaSt.js and index.esm-BYATNCU9.js. Use tree-shaking in your bundler configuration to remove unused exports. Split large bundles into smaller chunks and lazy-load non-critical components.
Reduce Network Chain Dependencies
Medium Impact+6 points estimatedWhy It Matters:
Long dependency chains create waterfall loading that extends total page load time to over 20 seconds.
How to Fix:
Preload critical JavaScript resources using <link rel="preload"> tags. Move Firebase initialization to run in parallel rather than sequentially. Consider bundling small JavaScript files together to reduce the number of network requests in the critical path.
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
Purge Unused CSS Rules
95% of your CSS file is unused, wasting 14KB of network bandwidth and blocking rendering.
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.