LCP
Largest Contentful Paint
6.8s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Image Delivery Strategy
How to optimize staging.learn.wowlearnings.org
Optimize Image Delivery Strategy
Medium Impact+8 points estimated
Why It Matters
Images are oversized for their display dimensions, wasting 31 KiB of unnecessary bandwidth.
How to Fix
Configure Next.js Image component with proper responsive breakpoints using 'sizes' prop. Generate multiple image sizes (240w, 480w, 640w) for different viewport widths. Set quality to 85 instead of 75 for better compression ratio. Implement proper aspect ratio containers to prevent layout shifts.
0Needs Improvement
What This Score Means
A score of 61 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
147ms
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 61/100, indicating significant user experience issues. The biggest problem is excessive unused JavaScript (282 KiB that could be removed), which is severely impacting page load times - your Largest Contentful Paint takes 6.8 seconds and Time to Interactive is a problematic 10.3 seconds. The site is loading unnecessary code from Google Analytics and several Next.js chunks that are mostly unused, plus there are render-blocking CSS files delaying initial page display. Removing unused JavaScript, optimizing CSS delivery, and code-splitting could potentially improve load times by over 1 second and dramatically boost your performance score.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+25 points estimatedWhy It Matters:
282 KiB of unused JavaScript is delaying LCP by 1.05 seconds and blocking critical page rendering.
How to Fix:
Use Next.js bundle analyzer to identify unused code in your chunks. Implement code splitting with dynamic imports for non-critical components. Remove or defer Google Analytics script until after page load. Configure webpack-bundle-analyzer to eliminate dead code in production builds.
Eliminate Render Blocking CSS
High Impact+20 points estimatedWhy It Matters:
CSS files are blocking initial page render and delaying both FCP and LCP by 800ms.
How to Fix:
Extract critical CSS for above-the-fold content and inline it in the HTML head. Use Next.js _document.js to inline critical styles. Convert non-critical CSS to load asynchronously using media='print' technique or loadCSS library. Remove 93% unused CSS from your main stylesheet.
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.