Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize gaming.tracker.pages.dev
45% of JavaScript (20KB) in main bundle is unused, increasing parse time and delaying FCP by 150ms.
Configure SvelteKit's code splitting to defer non-critical chunks. Use dynamic imports for features not needed on initial page load. Run bundle analyzer to identify and remove dead code from the Bsq8Px5l.js chunk.
A score of 83 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 gaming tracker website has decent performance with a score of 83/100, but there are several opportunities for improvement. The biggest issue is forced reflows in JavaScript that are causing layout thrashing and contributing to a poor First Input Delay of 230ms, which could make the site feel unresponsive to user interactions. Additionally, the site is serving oversized images that are 31KB larger than necessary and has 20KB of unused JavaScript that's slowing down the initial page load. Optimizing image sizes, fixing the JavaScript layout issues, and removing unused code could push this site into the 90+ performance range and deliver a noticeably smoother user experience.
Why It Matters:
Images are 27% larger than needed for display dimensions, directly delaying LCP by 200ms.
How to Fix:
Generate multiple WebP sizes (200w, 300w, 400w) for game covers. Update srcset to match actual display dimensions (315x472) instead of serving 400x600 images. Use CSS object-fit: cover to maintain aspect ratios while serving appropriately sized images.
Why It Matters:
JavaScript is causing 113ms of forced reflows that block the main thread and increase potential input delay.
How to Fix:
Cache DOM measurements before making style changes in your SvelteKit components. Batch DOM reads and writes separately using requestAnimationFrame. Replace direct offsetWidth/offsetHeight queries with ResizeObserver API for dynamic layout calculations.
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 Generic Speed Tests
Code is triggering expensive layout recalculations that block the main thread for 213ms total.
20KB of unused JavaScript increases parse time and delays interactivity without providing value.
Oversized images delay LCP by 150ms and waste 31KB of data transfer.
JavaScript is causing 113ms of forced reflows that block the main thread and increase potential input delay.