LCP
Largest Contentful Paint
4.9s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Unused CSS Rules
How to optimize shutoffware.com
Eliminate Unused CSS Rules
High Impact+12 points estimated
Why It Matters
95% of your CSS (14 KiB) is unused and delays both FCP and LCP by 150ms.
How to Fix
Use PurgeCSS or similar tools to remove unused styles from index-BLH4v9if.css. Implement critical CSS inlining for above-the-fold content. Defer non-critical CSS loading using media='print' onload technique.
0Needs Improvement
What This Score Means
A score of 74 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
41ms
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 moderate performance issues with a score of 74/100, but users are experiencing frustratingly slow loading times. The biggest problem is excessive unused JavaScript code, particularly from Firebase authentication files, which is wasting 167 KB and significantly delaying when the main content appears (taking 4.9 seconds instead of the recommended 2.5 seconds). The site is also bloated with 95% unused CSS code and has render-blocking resources that prevent the page from displaying quickly. Cleaning up this unused code, optimizing JavaScript delivery, and improving caching could easily boost the performance score by 15-20 points and provide a much faster user experience.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+18 points estimatedWhy It Matters:
167 KiB of unused JavaScript is delaying LCP by 450ms and blocking critical rendering.
How to Fix:
Implement dynamic imports for Firebase auth to load only when needed. Split the vendor bundles to defer non-critical components. Use tree-shaking in your build process to eliminate dead code from vendor-firebase and vendor-misc bundles.
Optimize Firebase Loading Strategy
Medium Impact+8 points estimatedWhy It Matters:
Firebase auth iframe creates a long dependency chain that extends page load by 1.4 seconds.
How to Fix:
Lazy load Firebase authentication until user interaction is required. Move Firebase initialization to a web worker or defer until after critical content loads. Implement proper caching headers for Firebase resources with longer cache lifetimes.
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 Network Dependency Chain
Critical resources are chained with a 211ms dependency tree that delays page rendering.
Defer Render-Blocking CSS
The main CSS file blocks initial rendering and creates a 345ms delay in the critical path.
Optimize Firebase Loading Strategy
Firebase auth iframe creates a long dependency chain that extends page load by 1.4 seconds.
Eliminate Render Blocking Resources
CSS and font files are blocking initial render, delaying FCP by 900ms.