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
Medium Impact+8 points estimated
Why It Matters
Legacy JavaScript polyfills are adding unnecessary 13KB for modern browsers that don't need these features.
How to Fix
Update your Next.js config to target modern browsers by setting browserslist to exclude older browsers. Remove polyfills for Array.prototype.at, Array.prototype.flat, Object.hasOwn and other baseline features. Configure Babel to use a higher ECMAScript target like ES2020+ in next.config.js.
0Needs Improvement
What This Score Means
A score of 83 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
31ms
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 83/100, but there's significant room for improvement. The biggest problem is render-blocking CSS and font requests that are delaying both First Contentful Paint (3.1s) and Largest Contentful Paint (3.6s) by an estimated 2.4 seconds. The site is also shipping 25KB of unused JavaScript and 14KB of legacy JavaScript polyfills that aren't needed for modern browsers. Fixing the render-blocking resources by inlining critical CSS or deferring non-essential stylesheets, along with cleaning up the JavaScript bundle, could easily push this site into the 90+ performance range and deliver a much faster user experience.
Other Optimization Recommendations
Eliminate Render-Blocking CSS
High Impact+25 points estimatedWhy It Matters:
Render-blocking CSS is delaying LCP and FCP by 2.45 seconds, preventing users from seeing content quickly.
How to Fix:
In your Next.js app, move critical CSS inline using styled-jsx or CSS-in-JS solutions like styled-components. Load non-critical CSS asynchronously using dynamic imports or the rel='preload' attribute. Consider splitting your CSS bundle to only load above-the-fold styles initially.
Remove Unused JavaScript Code
High Impact+15 points estimatedWhy It Matters:
37% of your JavaScript bundle is unused, wasting 25KB and slowing LCP by 150ms.
How to Fix:
Use Next.js built-in bundle analyzer by running 'npm run build' with ANALYZE=true to identify unused code. Implement code splitting with dynamic imports for non-critical components. Review and remove unused dependencies from package.json, especially polyfills for modern browser features.
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
Optimize Image Compression and Sizing
Images are 25 KiB larger than necessary and using suboptimal compression settings.
Eliminate Render-Blocking CSS
CSS files are blocking first paint by 710ms, significantly delaying user perception of page load.
Optimize CSS Delivery Strategy
Render-blocking CSS files delay First Contentful Paint by 450ms, preventing critical content from appearing quickly.
Remove Unused JavaScript Code
69 KiB of unused JavaScript is delaying LCP by 450ms and blocking page interactivity.