LCP
Largest Contentful Paint
5.7s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize CSS Delivery Strategy
How to optimize learn.wowlearnings.org
Optimize CSS Delivery Strategy
High Impact+20 points estimated
Why It Matters
Render-blocking CSS is delaying both FCP and LCP by 650ms with 93% unused rules.
How to Fix
Extract critical CSS for above-the-fold content using Next.js built-in CSS optimization. Move non-critical CSS to load asynchronously using next/dynamic with ssr: false. Remove unused CSS rules from the 27 KiB stylesheet using PurgeCSS in your Next.js build process.
0Poor
What This Score Means
A score of 22 falls in the "Poor" 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
845ms
Poor
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.35
Poor
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Next.js site has severe performance problems with a critically low score of 22/100. The biggest issue is excessive JavaScript execution taking over 8 seconds to process, which completely blocks user interactions and causes a devastating 23+ second delay before the page becomes usable. The site is loading nearly 4MB of data with 94% of CSS going unused, plus massive layout shifts from unsized images that make the page visually unstable. Removing unused JavaScript and CSS, optimizing the large image files, and adding proper image dimensions could dramatically improve performance and reduce the painfully long 44-second load time.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+25 points estimatedWhy It Matters:
324 KiB of unused JavaScript is blocking LCP for nearly 1 second and creating massive main thread blocking.
How to Fix:
Use Next.js bundle analyzer to identify unused code in chunks. Implement code splitting with dynamic imports for non-critical components. Remove or lazy load Google Analytics and other tracking scripts using Next.js Script component with strategy='afterInteractive'.
Fix Image Layout Shifts
Medium Impact+15 points estimatedWhy It Matters:
Unsized images in footer cause 0.352 CLS score, severely impacting user experience.
How to Fix:
Add explicit width and height props to Next.js Image components for app store badges. Use Next.js Image component instead of regular img tags for automatic optimization. Set proper aspect ratios and placeholder='blur' to prevent layout shifts during loading.
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 Layout Shift Issues
CLS score of 0.123 caused by carousel and cookie banner shifting content during load.
Reduce JavaScript Bundle Size
Unused JavaScript totals 1.6MB and blocks main thread for 4.7 seconds, causing 630ms input delay.
Optimize Large Image Assets
Images consume over 22MB with the largest being 4.5MB, severely impacting LCP at 8.3 seconds.
Fix Critical Element Render Delay
The LCP element (H1 heading) has a massive 4.3 second render delay, severely impacting page load performance.