LCP
Largest Contentful Paint
6.2s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Modernize JavaScript Build Target
How to optimize staging.learn.wowlearnings.org
Modernize JavaScript Build Target
Medium Impact+8 points estimated
Why It Matters
40 KiB of legacy polyfills are unnecessarily increasing bundle size and LCP by 300ms.
How to Fix
Update your Next.js configuration to target modern browsers by setting target: 'es2018' in next.config.js. Remove polyfills for Array.from, Object.hasOwn, and other modern features that have broad browser support. Configure Babel to exclude unnecessary transforms for your target browser list.
0Needs Improvement
What This Score Means
A score of 59 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
182ms
Good
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 59/100, indicating significant issues that need attention. The biggest problem is excessive JavaScript execution time (3.4 seconds), which is severely slowing down the page and causing a sluggish user experience with a 6.2-second Largest Contentful Paint. The site is loading 285 KiB of unused JavaScript code and has render-blocking CSS files that could save nearly 1 second if optimized. Reducing JavaScript bundle sizes, removing unused code, and deferring non-critical scripts would provide the most significant performance improvements and could potentially boost the score by 25+ points.
Other Optimization Recommendations
Reduce JavaScript Bundle Size
High Impact+18 points estimatedWhy It Matters:
285 KiB of unused JavaScript is blocking LCP by 0.9 seconds and increasing TBT by 600ms.
How to Fix:
Configure Next.js dynamic imports for non-critical components using React.lazy(). Enable tree shaking by updating your build configuration to exclude unused code from Google Analytics and other third-party scripts. Use Next.js Bundle Analyzer to identify and code-split large chunks like 0r3l2thsvv249.js.
Eliminate Render-Blocking CSS
High Impact+15 points estimatedWhy It Matters:
CSS files are blocking initial render and delaying LCP by 950ms.
How to Fix:
Inline critical CSS directly in the Next.js pages using styled-jsx or CSS-in-JS. Move non-critical CSS like 03flt2h9ox8~p.css to load asynchronously using next/dynamic with ssr: false. Reduce unused CSS by removing unnecessary styles from your CSS bundle.
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.