LCP
Largest Contentful Paint
5.9s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Render Blocking CSS Resources
How to optimize jxcs.space
Next.js SiteScore: 38/100Analyzed January 2026
Eliminate Render Blocking CSS Resources
High Impact+12 points estimated
Why It Matters
Render blocking CSS is delaying LCP by 900ms and preventing initial page paint.
How to Fix
Move critical CSS inline in Next.js using styled-jsx or CSS-in-JS. Load remaining CSS asynchronously with media='print' then switching to media='all' onload. Use Next.js dynamic imports for component-specific CSS chunks.
0Poor
What This Score Means
A score of 38 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
99ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.04
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Next.js/React site has severe performance problems with a critically low score of 38/100. The biggest issue is excessive JavaScript blocking the main thread for over 39 seconds, causing the page to become interactive only after 37+ seconds - an unacceptable user experience. The site is loading 169KB of unused JavaScript code, with render-blocking CSS files delaying initial page rendering, while poor image optimization (oversized Spotify album art and Steam avatars) further degrades performance. Immediate priorities should be removing unused JavaScript, deferring non-critical scripts, optimizing images to appropriate sizes and modern formats, and implementing code splitting to dramatically reduce the initial bundle size.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+15 points estimatedWhy It Matters:
172KB of unused JavaScript is delaying LCP by 1050ms and wasting bandwidth.
How to Fix:
Enable tree shaking in Next.js webpack config with sideEffects: false. Use dynamic imports for components that aren't immediately needed. Analyze bundle with @next/bundle-analyzer to identify and remove unused dependencies from the three problematic chunks.
Add Preconnect Hints for External Origins
Medium Impact+8 points estimatedWhy It Matters:
Missing preconnect hints are causing 300-320ms delays when fetching resources from external domains.
How to Fix:
Add <link rel='preconnect' href='https://cdn.akamai.steamstatic.com'> and similar tags for api.lanyard.rest and avatars.steamstatic.com in Next.js Head component. Limit to the 3 most critical origins to avoid performance degradation.
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
Add Resource Preconnect Headers
External API calls to Spotify and Steam are adding 300-319ms delays without preconnection optimization.
Reduce Unused JavaScript Bundles
152KB of unused JavaScript is wasting 910ms of load time and significantly impacting LCP and FCP.
Eliminate Render Blocking CSS
CSS files are blocking initial render and delaying LCP by 800ms with the largest file being 90KB.
Add Preconnect Hints for External Origins
Missing preconnect hints are causing 300-320ms delays when fetching resources from external domains.
Frequently Asked Questions
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