LCP
Largest Contentful Paint
3.6s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Update JavaScript Build Target
How to optimize pagespeed.deployhq.com
Update JavaScript Build Target
Low Impact+3 points estimated
Why It Matters
Legacy JavaScript polyfills are adding 13KB of unnecessary code that modern browsers don't need.
How to Fix
Update your Next.js configuration to target modern browsers by setting target: 'es2017' or higher in your Babel config. Configure browserslist in package.json to exclude older browser versions you don't need to support. This will eliminate polyfills for Array.at, Object.hasOwn, and other modern features.
0Needs Improvement
What This Score Means
A score of 82 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
120ms
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 good performance with a score of 82/100, but there's significant room for improvement in loading speed. The biggest issue is render-blocking CSS and font files that are delaying both First Contentful Paint (2.9s) and Largest Contentful Paint (3.6s) by an estimated 1.9 seconds. The site is loading CSS files and Google Fonts synchronously, creating a chain of dependencies that blocks the page from rendering quickly. To improve performance, you should defer non-critical CSS, preload important fonts, and consider inlining critical CSS directly in the HTML to eliminate render-blocking resources.
Other Optimization Recommendations
Eliminate Render-Blocking CSS Resources
High Impact+15 points estimatedWhy It Matters:
Render-blocking CSS is delaying your LCP by 1.9 seconds, significantly impacting page load performance.
How to Fix:
Inline critical CSS for above-the-fold content directly in your Next.js component using styled-jsx or CSS-in-JS. Move non-critical CSS including the Google Fonts stylesheet to load asynchronously using next/head with media='print' onload='this.media="all"'. Consider using next/font to optimize Google Fonts loading with automatic font optimization.
Remove Unused JavaScript Code
Medium Impact+8 points estimatedWhy It Matters:
25KB of unused JavaScript is adding 150ms to your LCP and increasing bundle size unnecessarily.
How to Fix:
Use Next.js Bundle Analyzer to identify unused code in your chunks. Implement dynamic imports for components not needed on initial page load. Configure your Next.js build to use tree-shaking by ensuring you're importing only specific functions rather than entire libraries.
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
Reduce JavaScript Bundle Size
655KB of unused JavaScript increases load time by 3.1 seconds and blocks main thread execution.
Optimize LCP Image Implementation
Resource load delay of 4,613ms for LCP image makes it undiscoverable and prevents fast loading.
Fix Server Response and Redirects
TTFB of 1,028ms and redirect chain waste 1,830ms, severely delaying LCP by 20+ seconds.
Optimize Cache Strategy
Poor caching configuration forces users to re-download resources on repeat visits, missing opportunities for faster load times.