LCP
Largest Contentful Paint
3.2s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Remove Unused Code and Modernize JavaScript
How to optimize fithub.id
Remove Unused Code and Modernize JavaScript
Medium Impact+10 points estimated
Why It Matters
335 KiB of unused JavaScript and 57 KiB of legacy polyfills unnecessarily increase bundle size.
How to Fix
Use Next.js bundle analyzer to identify dead code in Google Tag Manager and analytics scripts. Update build target in next.config.js to exclude legacy browser support. Implement dynamic imports for non-critical features using Next.js code splitting.
0Needs Improvement
What This Score Means
A score of 70 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
411ms
Needs Improvement
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 70/100, primarily due to excessive JavaScript execution blocking the main thread for 3.3 seconds. The biggest issue is JavaScript bloat from third-party scripts like Google Analytics, Facebook Pixel, and TikTok tracking, which are consuming over 335KB of unused code and creating a 14.5-second delay before the page becomes fully interactive. Removing unused JavaScript, implementing better caching policies (currently missing 242KB of cacheable resources), and cleaning up 25KB of unused CSS could dramatically improve performance and reduce the painful 1+ second blocking time that makes the site feel sluggish to users.
Other Optimization Recommendations
Optimize Third-Party JavaScript Loading
High Impact+25 points estimatedWhy It Matters:
Third-party scripts consume 2.2s execution time and block main thread with 1,055ms Total Blocking Time.
How to Fix:
Implement lazy loading for Facebook Pixel and Google Analytics using Next.js Script component with strategy='afterInteractive'. Move TikTok pixel to load after user interaction. Use Partytown to offload scripts to web workers.
Implement Efficient Caching Strategy
High Impact+15 points estimatedWhy It Matters:
Poor cache lifetimes waste 242 KiB on repeat visits, directly impacting LCP by 150ms.
How to Fix:
Configure Next.js to set proper cache headers for static assets in next.config.js. Extend Facebook Pixel cache lifetime from 20 minutes to 24 hours. Use CDN edge caching for font files and configure immutable cache headers.
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.