LCP
Largest Contentful Paint
4.5s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize LCP Image Discovery
How to optimize shutoffware.com
Optimize LCP Image Discovery
High Impact+10 points estimated
Why It Matters
The main logo image lacks priority hints and isn't discoverable from initial HTML, delaying LCP.
How to Fix
Add fetchpriority='high' attribute to the ShutOffWare logo image. Ensure the LCP image source is directly in the HTML rather than loaded via JavaScript. Consider inlining the SVG logo or preloading it with <link rel='preload'> in the document head.
0Needs Improvement
What This Score Means
A score of 75 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
53ms
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 below-average performance with a score of 75/100, indicating significant room for improvement. The biggest problem is slow content loading, with the First Contentful Paint taking 3.8 seconds and Largest Contentful Paint taking 4.5 seconds - both well above Google's recommended thresholds. The main culprits are unused JavaScript (147 KB of wasted code from Firebase and React libraries), render-blocking CSS and fonts that delay initial page rendering by nearly 900ms, and the site's logo image lacking priority loading hints. Cleaning up unused code, minifying JavaScript files, and optimizing the loading sequence of critical resources could dramatically improve loading speeds and user experience.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+12 points estimatedWhy It Matters:
147 KiB of unused JavaScript is delaying LCP by 750ms and FCP by 450ms.
How to Fix:
Analyze Firebase and React bundles to remove unused features. Use tree shaking with webpack/Vite to eliminate dead code. Consider lazy loading Firebase auth only when authentication is needed. Split vendor bundles and load them asynchronously where possible.
Eliminate Render Blocking Resources
Medium Impact+8 points estimatedWhy It Matters:
CSS and font files are blocking initial render, delaying FCP by 900ms.
How to Fix:
Inline critical CSS styles directly in the HTML head. Load Google Fonts asynchronously using font-display: swap. Move non-critical CSS to load after first paint using media='print' onload trick or async CSS loading.
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 Unused CSS Rules
95% of your CSS (14 KiB) is unused and delays both FCP and LCP by 150ms.