Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize learn.wowlearnings.org
Course thumbnail images are 80% larger than needed for their display dimensions, wasting 36 KiB of bandwidth.
Configure Next.js Image component with proper responsive breakpoints using the sizes prop. Generate multiple image variants (284x160, 568x320) for different screen densities. Enable Next.js image optimization with quality=85 and format='webp' for modern browsers.
A score of 47 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.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This Next.js site has poor performance with a score of 47/100, indicating significant user experience issues. The biggest problem is excessive unused JavaScript (293 KiB of wasted code) combined with slow JavaScript execution time of 2.7 seconds, which is causing your Largest Contentful Paint to suffer at 7.2 seconds and Time to Interactive to reach a painful 9.5 seconds. The site is also being slowed down by render-blocking CSS files and forced reflows that are making the page feel unresponsive. Removing unused JavaScript, optimizing your Next.js build configuration, and addressing the CSS blocking issues could potentially improve your score by 30+ points and dramatically reduce loading times.
Why It Matters:
293 KiB of unused JavaScript is blocking LCP by 1.15 seconds and delaying initial paint.
How to Fix:
Use Next.js bundle analyzer to identify unused code chunks. Implement dynamic imports for components below the fold. Remove or defer Google Analytics and other tracking scripts until after page load. Configure webpack to split bundles more efficiently in next.config.js.
Why It Matters:
CSS files are blocking initial render by 470ms and preventing fast First Contentful Paint.
How to Fix:
Move critical CSS inline in the Next.js _document.js file for above-the-fold content. Use Next.js built-in CSS optimization to defer non-critical stylesheets. Remove 94% unused CSS rules from 00mjga._82gl4.css by purging unused Tailwind classes or splitting component-specific styles.
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.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Next.js Speed Tests
Render-blocking CSS files delay FCP by 750ms and contribute to the poor initial paint performance.
756 KiB of unused JavaScript delays LCP by 3.9 seconds and wastes 3.9 seconds of load time.
The redirect from commissions.gg to www.commissions.gg wastes 780ms and delays both FCP and LCP by 800ms each.
LCP element has 3.2 second render delay causing the poor 7-second LCP score.