LCP
Largest Contentful Paint
5.8s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix Layout Thrashing Issues
How to optimize learn.wowlearnings.org
Fix Layout Thrashing Issues
Medium Impact+12 points estimated
Why It Matters
Forced reflows are causing 485ms of main thread blocking, contributing to poor INP scores.
How to Fix
Review the JavaScript file causing reflows (0cnk-vj-0hm9p.js) and batch DOM reads/writes. Use CSS transforms instead of changing layout properties. Implement ResizeObserver for responsive changes rather than reading offsetWidth repeatedly during render cycles.
0Poor
What This Score Means
A score of 45 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
437ms
Needs Improvement
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 poor performance with a score of 45/100, indicating significant user experience issues. The biggest problem is excessive unused JavaScript (282 KiB of waste) that's blocking page rendering and delaying your Largest Contentful Paint to a slow 5.8 seconds - well above the recommended 2.5 seconds. The site is also suffering from render-blocking CSS files and inefficient JavaScript execution that keeps the main thread busy for 6.4 seconds. Removing unused JavaScript, especially from Google Tag Manager and Next.js chunks, along with optimizing CSS delivery could potentially improve your score by 30+ points and dramatically reduce load times for users.
Other Optimization Recommendations
Eliminate Render Blocking CSS
High Impact+18 points estimatedWhy It Matters:
Critical CSS blocks initial page render, delaying both FCP and LCP by 600ms.
How to Fix:
In your Next.js app, inline critical CSS for above-the-fold content using Critical CSS extraction. Move non-critical CSS like the 29KB unused stylesheet to load after first paint. Use next/dynamic for components with heavy styling to defer CSS loading until needed.
Remove Unused JavaScript Code
High Impact+15 points estimatedWhy It Matters:
282KB of unused JavaScript delays LCP by 900ms and increases Total Blocking Time significantly.
How to Fix:
Use Next.js tree shaking to eliminate dead code from your bundles. Replace Google Analytics with lighter alternatives like Plausible, or defer GTM loading until after page interaction. Split large chunks using dynamic imports and load components on-demand to reduce initial bundle size.
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 Critical CSS Rendering
Render-blocking CSS files delay FCP by 750ms and contribute to the poor initial paint performance.
Reduce Unused JavaScript Bundle Size
756 KiB of unused JavaScript delays LCP by 3.9 seconds and wastes 3.9 seconds of load time.
Eliminate Redirect and Optimize Server Response
The redirect from commissions.gg to www.commissions.gg wastes 780ms and delays both FCP and LCP by 800ms each.
Eliminate Element Render Delay
LCP element has 3.2 second render delay causing the poor 7-second LCP score.