LCP
Largest Contentful Paint
3.6s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce Unused JavaScript Bundle Size
How to optimize pagespeed.deployhq.com
Reduce Unused JavaScript Bundle Size
High Impact+12 points estimated
Why It Matters
24KB of unused JavaScript is wasting network resources and delaying LCP by 150ms.
How to Fix
Enable Next.js tree shaking by ensuring named imports instead of default imports. Use next-bundle-analyzer to identify unused code in your 67KB chunk. Implement dynamic imports for non-critical components using React.lazy() and Suspense to split your bundle.
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
45ms
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 are significant opportunities for improvement. The biggest issue is render-blocking CSS and font resources that are delaying both First Contentful Paint (2.9s) and Largest Contentful Paint (3.6s) by an estimated 2 seconds. The site is also loading 24KB of unused JavaScript and 13KB of legacy JavaScript polyfills that aren't needed for modern browsers. To boost performance, prioritize inlining critical CSS, deferring non-essential stylesheets, removing unused code, and updating the build process to target modern browsers - these changes could potentially improve your score into the 90s range.
Other Optimization Recommendations
Eliminate Render-Blocking CSS Resources
High Impact+15 points estimatedWhy It Matters:
Render-blocking CSS is delaying LCP and FCP by an estimated 2 seconds, significantly impacting Core Web Vitals.
How to Fix:
In your Next.js app, move critical CSS inline using next-optimized-images or custom CSS extraction. Defer non-critical CSS using dynamic imports or load it asynchronously with media='print' onload="this.media='all'". Consider splitting your 18KB CSS bundle into critical and non-critical parts.
Fix Element Render Delay Issue
High Impact+18 points estimatedWhy It Matters:
The LCP element has a massive 2.5-second render delay, indicating JavaScript is blocking rendering of critical content.
How to Fix:
Move the LCP element (text paragraph) to render server-side in Next.js using getServerSideProps or getStaticProps. Ensure critical content renders before JavaScript hydration. Consider using React 18's streaming SSR to prioritize above-the-fold content rendering.
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 Element Render Delay Issue
The LCP element has a massive 2.5-second render delay, indicating JavaScript is blocking rendering of critical content.
Add Explicit Image Dimensions
Missing width/height attributes on images can cause layout shifts during loading.
Remove Unused JavaScript Bundle
386 KiB of unused JavaScript delays page interactivity by 1.8 seconds.
Fix LCP Image Loading
Your LCP image takes 7.5 seconds to load, causing the worst Core Web Vital score.