LCP
Largest Contentful Paint
3.6s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Render Blocking CSS
How to optimize pagespeed.deployhq.com
Eliminate Render Blocking CSS
High Impact+12 points estimated
Why It Matters
CSS files are blocking initial render and delaying LCP by 2.2 seconds.
How to Fix
In Next.js, move critical CSS inline using styled-jsx or CSS-in-JS. Split large CSS chunks using dynamic imports with next/dynamic. Preload the Inter font using next/font/google instead of Google Fonts link to eliminate the font chain dependency.
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
98ms
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 your First Contentful Paint by 2.2 seconds, causing users to wait nearly 3 seconds before seeing any content. The site is also loading 25KB of unused JavaScript code and using outdated JavaScript polyfills that aren't necessary for modern browsers. Optimizing CSS delivery, implementing font preloading, and updating your build process to remove legacy code could easily push your score into the 90s and improve user experience substantially.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+8 points estimatedWhy It Matters:
37% of JavaScript bundle is unused, wasting 25KB and delaying LCP by 150ms.
How to Fix:
Enable tree shaking in Next.js webpack config. Use dynamic imports for components not needed on initial render. Run bundle analyzer with @next/bundle-analyzer to identify and remove unused dependencies from the 9c23f44fff36548a.js chunk.
Modernize JavaScript Build Target
Medium Impact+4 points estimatedWhy It Matters:
Legacy JavaScript polyfills add unnecessary 13KB for modern browsers.
How to Fix:
Update Next.js config to target modern browsers by setting browserslist to exclude IE and old Chrome versions. Remove polyfills for Array.prototype.at, flat, flatMap and other modern features. Use next/swc compiler with ES2020+ target to eliminate transpilation overhead.
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
Modernize JavaScript Build Target
Legacy JavaScript polyfills add unnecessary 13KB for modern browsers.
Remove Unused JavaScript Code
37% of JavaScript bundle is unused, wasting 25KB and delaying LCP by 150ms.
Code Split Unused JavaScript
99KB of unused JavaScript is being loaded unnecessarily, contributing to slower Time to Interactive (4.1s).
Preload Critical Font Resources
The JetBrains Mono font (22KB) is on the critical path with 1.85s load time, potentially causing layout shifts.