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 Resources
How to optimize pagespeed.deployhq.com
Eliminate Render-Blocking CSS Resources
High Impact+15 points estimated
Why It Matters
Render-blocking CSS is delaying LCP by 1.95 seconds, preventing the page from displaying content quickly.
How to Fix
Inline critical CSS for above-the-fold content directly in the HTML head. Use Next.js dynamic imports to defer non-critical CSS files. Move Google Fonts loading to use next/font/google for automatic optimization and preloading.
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
43ms
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 one major issue holding it back from excellent performance. The biggest problem is render-blocking CSS and font files that are preventing the page from displaying content quickly, delaying both First Contentful Paint (2.9s) and Largest Contentful Paint (3.6s) by nearly 2 seconds. The site is loading CSS files and Google Fonts synchronously, which blocks the browser from rendering anything until these resources finish downloading. Deferring or inlining critical CSS and optimizing font loading could potentially save almost 2 seconds of load time and push this site into the 90+ performance range.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+10 points estimatedWhy It Matters:
37% of JavaScript (25KB) is unused, adding unnecessary download time and blocking LCP by 150ms.
How to Fix:
Run Next.js bundle analyzer to identify unused code in chunks/0ff423a9fcc0186e.js. Enable tree shaking by ensuring imports are ES6 modules. Split large chunks using dynamic imports for route-based code splitting.
Update JavaScript Build Target
Medium Impact+5 points estimatedWhy It Matters:
Legacy JavaScript polyfills add 14KB of unnecessary code for modern browsers that support ES6+ features natively.
How to Fix:
Update Next.js target in next.config.js to 'es2020' or newer to remove polyfills for Array.at, Object.hasOwn, and other modern features. Configure Babel to exclude unnecessary transforms for your target browser support.
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
Fix Render Blocking Resources
Critical CSS files are blocking initial page render and delaying LCP by 200ms.
Reduce JavaScript Execution Time
JavaScript takes 10.5 seconds to execute, blocking the main thread and preventing user interactions for 4.3 seconds.
Eliminate Unused JavaScript Code
Removing 3,139 KiB of unused JavaScript will reduce network transfer time and improve LCP by 12 seconds.
Implement Long-term Asset Caching
Poor caching strategy wastes 74KB on repeat visits and slows LCP by 300ms.