LCP
Largest Contentful Paint
4.7s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Make LCP Image Discoverable
How to optimize gaming.tracker.pages.dev
Make LCP Image Discoverable
Medium Impact+8 points estimated
Why It Matters
LCP image requires JavaScript execution to be discovered, delaying the critical image request.
How to Fix
Move the primary game cover image from JavaScript-rendered content to the initial HTML document. Consider server-side rendering the first few game cards or add a <link rel='preload'> for the LCP image. Remove the unused preconnect to fonts.gstatic.com and replace with a preload for your critical image.
0Needs Improvement
What This Score Means
A score of 52 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
512ms
Poor
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.29
Poor
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This gaming tracker site has poor performance with a score of 52/100, indicating significant issues that need immediate attention. The biggest problem is extremely slow content loading, with the Largest Contentful Paint taking 4.7 seconds - well above the recommended 2.5 seconds. The main culprits are oversized images (wasting 32KB of downloads) and images without proper width/height attributes, which cause layout shifts as content loads. Additionally, the site has an unused preconnect to Google Fonts and some render-blocking CSS that delays initial rendering. Fixing image sizing, adding explicit dimensions to prevent layout shifts, and optimizing the critical rendering path could improve the performance score by 25+ points and dramatically enhance user experience.
Other Optimization Recommendations
Add Explicit Image Dimensions
High Impact+15 points estimatedWhy It Matters:
Unsized images cause a 0.293 CLS score from layout shifts as images load asynchronously.
How to Fix:
Add width='178' height='267' attributes to all .cover-image elements based on their displayed dimensions. Update your Svelte component to include these dimensions in the img tag. This prevents layout jumping when images load and improves visual stability.
Optimize Image Responsive Sizing
High Impact+12 points estimatedWhy It Matters:
Images are 32KB larger than needed, delaying LCP by 300ms with oversized detail images.
How to Fix:
Generate additional responsive image sizes at 178px and 311px widths to match actual display dimensions. Update your srcset to include these optimized sizes. Ensure your image processing pipeline creates images that match the CSS-rendered dimensions rather than serving 400x600 images for 311x467 displays.
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 Generic Speed Tests
Generic Performance Resources
Eliminate Forced Layout Reflows
JavaScript is forcing 125ms of layout reflows, blocking the main thread and degrading user interaction responsiveness.
Optimize Image Delivery and Sizing
Images are causing 2,367 KiB of wasted bytes and delaying LCP by 400ms, with the hero image alone accounting for 1.6MB.
Reduce Unused JavaScript and CSS
545 KiB of unused JavaScript and 208 KiB of unused CSS are blocking rendering and delaying LCP by 2.35 seconds.
Fix LCP Image Discovery Issues
The LCP image has a 2.4 second resource load delay because it's not discoverable in the initial HTML and lacks priority hints.