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
Redirects delay page load by 770ms and significantly impact LCP by preventing the browser from starting content rendering.
Update your Next.js middleware or authentication logic to serve the final destination directly. If using NextAuth.js, configure the callbackUrl to avoid the dashboard redirect. Set up proper route handling in your pages/_app.js to prevent unnecessary redirects during authentication flow.
A score of 50 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.
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 50/100, indicating significant user experience issues. The biggest problem is excessive JavaScript blocking the page - the site takes 5.9 seconds for the largest content to appear and 9.4 seconds to become fully interactive, with 1.5 seconds of total blocking time preventing user interactions. The most impactful fixes would be removing unnecessary JavaScript polyfills (saving 40KB), eliminating page redirects (saving 770ms), and reducing unused JavaScript code (saving 353KB), which together could improve load times by over 2 seconds. Additionally, render-blocking CSS files are delaying initial page display by an estimated 580ms, suggesting the site's build process needs optimization to serve leaner, modern code bundles.
Why It Matters:
Unnecessary polyfills waste 40KB and delay LCP by 300ms for modern browsers that already support these features.
How to Fix:
Update your Next.js target configuration in next.config.js to exclude polyfills for modern browsers (set target: 'es2017' or higher). Configure your build process to conditionally load polyfills only for older browsers using differential serving. Remove polyfills for Array.at, Array.flat, Object.fromEntries which have wide browser support.
Why It Matters:
CSS files block initial page render for 580ms, preventing users from seeing content and delaying both LCP and FCP.
How to Fix:
Inline critical CSS for above-the-fold content directly in your Next.js page head. Use Next.js dynamic imports to load non-critical CSS asynchronously. Split your CSS chunks and defer loading of non-essential styles using next/dynamic with ssr: false for components not immediately visible.
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.