LCP
Largest Contentful Paint
5.1s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize JavaScript Build Target
How to optimize learn.wowlearnings.org
Optimize JavaScript Build Target
Medium Impact+8 points estimated
Why It Matters
Legacy JavaScript polyfills add 40 KiB and 300ms to LCP while modern browsers don't need these transformations.
How to Fix
Update your Next.js config to target modern browsers by setting browserslist to exclude IE support. Configure Babel preset-env with 'last 2 versions' and enable Next.js SWC compiler for better performance. Remove unnecessary polyfills for Array.from, Object.hasOwn, and other modern features.
0Needs Improvement
What This Score Means
A score of 77 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
142ms
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 poor performance with a score of 77/100, primarily due to excessive unused code and render-blocking resources. The biggest problem is the extremely slow Largest Contentful Paint of 5.1 seconds, caused by 285 KiB of unused JavaScript and 29 KiB of unused CSS that block page rendering. The site is also loading oversized images and using legacy JavaScript polyfills unnecessarily for modern browsers. Cleaning up unused code, optimizing the CSS delivery, and properly sizing images could improve the score by 15-20 points and reduce load times by over 1 second.
Other Optimization Recommendations
Eliminate Render-Blocking CSS Resources
High Impact+15 points estimatedWhy It Matters:
CSS files are blocking initial render and delaying LCP by 600ms, preventing users from seeing content quickly.
How to Fix:
Inline critical CSS for above-the-fold content in your Next.js pages. Use next/dynamic with ssr: false for non-critical components. Split CSS using Next.js code splitting and load non-critical styles asynchronously with media='print' onload="this.media='all'".
Remove Unused JavaScript Code
High Impact+12 points estimatedWhy It Matters:
285 KiB of unused JavaScript is delaying LCP by 750ms and wasting bandwidth on unnecessary code execution.
How to Fix:
Use Next.js bundle analyzer to identify unused code in your chunks. Implement dynamic imports for Google Analytics and other third-party scripts. Configure webpack to tree-shake unused exports and consider lazy loading non-essential components with React.lazy().
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.