LCP
Largest Contentful Paint
9.5s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Update JavaScript Build Target
How to optimize 6a1ba49684c7cc0009a06d10..admirable.florentine.bf5b33.netlify.app
Update JavaScript Build Target
Medium Impact+12 points estimated
Why It Matters
Legacy JavaScript polyfills add 42 KiB of unnecessary code that delays LCP by 300ms.
How to Fix
Update your Next.js browserslist config to target modern browsers (>0.5%, not dead, not op_mini all). Remove polyfills for Array.flat, Object.hasOwn, and String.trim methods. Configure Babel to use 'preset-env' with modern browser targets to eliminate unnecessary transpilation.
0Needs Improvement
What This Score Means
A score of 65 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
134ms
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 Next.js site has poor performance with a score of 65/100, indicating significant user experience issues. The biggest problem is an extremely slow Largest Contentful Paint of 9.5 seconds, primarily caused by 432 KiB of unused JavaScript from Google Analytics and Tag Manager that's blocking the page load. The site is also suffering from unoptimized images (66 KiB of potential savings), legacy JavaScript polyfills that aren't needed for modern browsers (42 KiB savings), and render-blocking CSS resources. Removing unused JavaScript, optimizing image compression, and modernizing the JavaScript build process could potentially improve the performance score by 25+ points and dramatically reduce load times for users.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+25 points estimatedWhy It Matters:
432 KiB of unused JavaScript is delaying LCP by 1.8 seconds and blocking user interactions.
How to Fix:
Use Next.js bundle analyzer to identify unused code in Google Tag Manager scripts. Implement dynamic imports for non-critical features. Configure GTM to load only essential tags on initial page load, deferring analytics until after user interaction.
Optimize Images and Video Posters
High Impact+18 points estimatedWhy It Matters:
Uncompressed images waste 66 KiB and delay LCP by 450ms, especially the hero background.
How to Fix:
Increase compression on your Netlify image transforms by lowering quality from q=80 to q=60-65. Use Next.js Image component with priority={true} for hero images. Replace video poster images with optimized WebP versions at 60-70% quality.
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.
Optimize Image Compression Settings
Poor image compression is wasting 25 KiB and impacting LCP performance by 200ms.