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 Image Compression Settings
How to optimize 6a1bb3355882dc00081f107d..admirable.florentine.bf5b33.netlify.app
Optimize Image Compression Settings
Medium Impact+5 points estimated
Why It Matters
Poor image compression is wasting 25 KiB and impacting LCP performance by 200ms.
How to Fix
Increase compression quality in your Netlify image transform URLs by lowering the 'q' parameter from 80 to 65-70. For the hero background image, consider using a more aggressive compression or switching to AVIF format. Use Next.js Image component with optimized quality settings for automatic compression.
0Needs Improvement
What This Score Means
A score of 78 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
332ms
Needs Improvement
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 Next.js site has moderate performance issues with a score of 78/100. The biggest problem is excessive unused JavaScript from Google Analytics and other scripts, which is wasting 282 KB and creating a sluggish 9.3-second Time to Interactive. The site is also being held back by render-blocking CSS files and inefficient image compression that could save an additional 25 KB. Removing unused JavaScript code, optimizing image compression, and implementing proper caching strategies could improve the score by 15+ points and significantly speed up the user experience.
Other Optimization Recommendations
Remove Render Blocking CSS
High Impact+8 points estimatedWhy It Matters:
Critical CSS is blocking initial page render and delaying LCP by 200ms.
How to Fix:
In your Next.js app, inline critical CSS directly in the document head using styled-jsx or CSS-in-JS. Move non-critical styles to load asynchronously using next/dynamic or loadCSS. Consider code-splitting your CSS bundle to only load styles needed for above-the-fold content.
Eliminate Unused JavaScript Code
High Impact+12 points estimatedWhy It Matters:
282 KiB of unused JavaScript is blocking page load and delaying LCP by 600ms.
How to Fix:
Use Next.js bundle analyzer to identify unused code in your chunks. Remove or defer Google Tag Manager and analytics scripts using next/script with strategy='afterInteractive'. Split large bundles and implement dynamic imports for non-critical components using next/dynamic.
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 Next.js Speed Tests
Next.js Performance Resources
Extend Static Asset Cache Headers
Short cache lifetimes (4 hours) for static assets waste 89 KiB on repeat visits and slow down returning users.
Reduce Unused JavaScript Bundles
287 KiB of unused JavaScript is bloating your bundles and contributing to the 8.8-second Time to Interactive.
Optimize Element Render Delay
Element render delay of 2.8 seconds is causing your LCP to be severely impacted, representing the largest performance bottleneck.
Eliminate Unused JavaScript Code
282 KiB of unused JavaScript is blocking page load and delaying LCP by 600ms.