LCP
Largest Contentful Paint
3.0s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Render Blocking Resources
How to optimize pagespeed.deployhq.com
Eliminate Render Blocking Resources
High Impact+8 points estimated
Why It Matters
CSS files are blocking initial render and delaying LCP by 2.55 seconds.
How to Fix
In your Next.js app, move critical CSS inline using styled-jsx or CSS-in-JS. Preload the Google Fonts using next/font for automatic optimization. Consider splitting CSS and loading non-critical styles asynchronously using next/dynamic.
0Needs Improvement
What This Score Means
A score of 89 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
108ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.03
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Next.js site has good overall performance with a score of 89/100, but there's a critical issue blocking optimal loading speeds. The biggest problem is render-blocking CSS and font files that are delaying both First Contentful Paint (2.9s) and Largest Contentful Paint (3.0s) by an estimated 2.5 seconds. The site is loading Google Fonts and CSS files synchronously, which prevents the page from rendering until these resources finish downloading. To significantly improve Core Web Vitals, you should inline critical CSS, preload fonts, and defer non-essential stylesheets to move these resources out of the critical rendering path.
Other Optimization Recommendations
Optimize JavaScript Bundle Size
High Impact+5 points estimatedWhy It Matters:
25KB of unused JavaScript is being loaded unnecessarily, impacting performance.
How to Fix:
Enable tree-shaking in your Next.js build configuration. Use dynamic imports with next/dynamic for components not needed on initial load. Analyze your bundle with @next/bundle-analyzer to identify and remove unused dependencies.
Fix Forced Reflow Issues
Medium Impact+3 points estimatedWhy It Matters:
JavaScript is forcing layout recalculations that block the main thread and hurt user interactions.
How to Fix:
Batch DOM reads and writes to avoid layout thrashing. Use CSS transforms instead of changing geometric properties. Implement React's useLayoutEffect sparingly and consider moving calculations to useEffect when possible.
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 JavaScript Execution Performance
7.6 seconds of JavaScript execution time creates 2.3 seconds of blocking time, preventing user interactions.
Modernize JavaScript Build Target
Legacy JavaScript polyfills add 13 KiB and 150ms to LCP for features modern browsers support natively.
Remove Unused JavaScript Code
140 KiB of unused JavaScript delays LCP by 950ms and blocks user interactions.
Fix Forced Reflow Issues
DOM queries after style changes cause 206ms of forced reflows, degrading rendering performance.