LCP
Largest Contentful Paint
12.5s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce Unused JavaScript Bundle Size
How to optimize commissions.gg
Reduce Unused JavaScript Bundle Size
High Impact+20 points estimated
Why It Matters
756 KiB of unused JavaScript delays LCP by 3.9 seconds and wastes 3.9 seconds of load time.
How to Fix
Implement code splitting in your Next.js app using dynamic imports for non-critical components. Use Next.js bundle analyzer (@next/bundle-analyzer) to identify large chunks. Remove polyfills for modern baseline features (Array.at, Object.hasOwn) by updating your Babel/browserslist config to target modern browsers only.
0Poor
What This Score Means
A score of 39 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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
297ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.07
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Next.js site has severe performance issues with a score of only 39/100. The biggest problem is an extremely slow Largest Contentful Paint of 12.5 seconds, primarily caused by a redirect from the non-www to www version that adds 780ms delay, followed by render-blocking CSS files and excessive unused JavaScript (756 KiB). The site also suffers from poor caching policies and network dependency chains that create a waterfall effect, with the main thread being blocked for 2.8 seconds by JavaScript execution. Eliminating the redirect, optimizing JavaScript bundles, and implementing better caching could easily improve the score by 40+ points and dramatically enhance user experience.
Other Optimization Recommendations
Eliminate Redirect and Optimize Server Response
High Impact+25 points estimatedWhy It Matters:
The redirect from commissions.gg to www.commissions.gg wastes 780ms and delays both FCP and LCP by 800ms each.
How to Fix:
Configure your DNS/hosting to serve www.commissions.gg directly without redirects. In Next.js, add permanent redirects in next.config.js for the non-www domain. Enable text compression (gzip/brotli) on your server to reduce document latency by an additional 70ms.
Optimize Critical CSS Rendering
Medium Impact+12 points estimatedWhy It Matters:
Render-blocking CSS files delay FCP by 750ms and contribute to the poor initial paint performance.
How to Fix:
Inline critical CSS for above-the-fold content directly in your Next.js pages. Use next/dynamic with ssr: false for non-critical components that load heavy CSS. Consider extracting font CSS to a separate file and preloading it with <link rel='preload'> in your Next.js _document.js.
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.
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.
Optimize JavaScript Bundle Size
Heavy JavaScript parsing takes 900ms and creates 990ms of blocking time, preventing user interactions.