LCP
Largest Contentful Paint
5.8s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Update JavaScript Build Target
How to optimize learn.wowlearnings.org
Update JavaScript Build Target
Medium Impact+8 points estimated
Why It Matters
Legacy polyfills add 40KB of unnecessary code that modern browsers don't need, slowing LCP by 300ms.
How to Fix
Update your Next.js target in next.config.js to 'es2022' or newer. Configure Babel to exclude polyfills for modern features like Array.prototype.at and Object.hasOwn. Use browserslist to target only browsers you actually support, removing outdated polyfills.
0Needs Improvement
What This Score Means
A score of 65 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
302ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.01
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Next.js site has poor performance with a score of 65/100, meaning users experience slow loading times and delayed interactivity. The biggest problem is excessive unused JavaScript (285 KiB) that's blocking the page from loading quickly, causing your Largest Contentful Paint to take 5.8 seconds when it should be under 2.5 seconds. The site is also loading 29 KiB of unused CSS and has render-blocking resources that delay initial page display by 580ms. Cleaning up unused code, optimizing JavaScript bundles, and deferring non-critical resources could improve your score by 20+ points and make the site feel much faster for users.
Other Optimization Recommendations
Eliminate Render Blocking CSS
High Impact+15 points estimatedWhy It Matters:
CSS files are blocking initial page render, delaying LCP by 600ms and preventing users from seeing content.
How to Fix:
In your Next.js app, move critical CSS inline using styled-jsx or CSS-in-JS. Use dynamic imports for non-critical CSS files. Configure next.config.js to optimize CSS chunks and enable experimental.optimizeCss for better code splitting.
Remove Unused JavaScript Code
High Impact+12 points estimatedWhy It Matters:
285KB of unused JavaScript is wasting bandwidth and delaying LCP by 750ms with slow parsing times.
How to Fix:
Enable tree-shaking in Next.js by using ES6 imports and dynamic imports for large components. Move Google Analytics to a web worker or use Next.js Script component with strategy='lazyOnload'. Use webpack-bundle-analyzer to identify and remove unused dependencies from your React components.
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
Eliminate Element Render Delay
LCP element has 3.2 second render delay causing the poor 7-second LCP score.
Optimize JavaScript Bundle Size
Heavy JavaScript parsing takes 900ms and creates 990ms of blocking time, preventing user interactions.
Fix Render-Blocking Font Loading
Google Fonts are blocking first paint for 1.65 seconds, severely delaying LCP and FCP.
Optimize Image Delivery and Sizing
Images are oversized and poorly compressed, wasting 289 KiB of bandwidth with no impact on visual quality.