LCP
Largest Contentful Paint
5.5s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce Unused JavaScript Bundles
How to optimize jxcs.space
Next.js SiteScore: 66/100Analyzed January 2026
Reduce Unused JavaScript Bundles
High Impact+15 points estimated
Why It Matters
152KB of unused JavaScript is wasting 910ms of load time and significantly impacting LCP and FCP.
How to Fix
Enable Next.js tree shaking by using named imports instead of default imports. Implement dynamic imports with next/dynamic for components not needed on initial load. Use Next.js bundle analyzer to identify and remove unused dependencies from your chunks.
0Needs Improvement
What This Score Means
A score of 66 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
101ms
Good
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 66/100, primarily due to slow loading times and inefficient resource delivery. The biggest issue is render-blocking CSS files (especially a large 90KB stylesheet) that delay content display, contributing to a sluggish 5.5-second Largest Contentful Paint and 2.8-second First Contentful Paint. The site is also bloated with 152KB of unused JavaScript code and lacks proper preconnect hints for external resources like Spotify and Steam APIs. Optimizing CSS delivery, removing unused JavaScript, and adding preconnect hints for key third-party origins could potentially improve load times by over 1.5 seconds and boost the performance score significantly.
Other Optimization Recommendations
Eliminate Render Blocking CSS
High Impact+18 points estimatedWhy It Matters:
CSS files are blocking initial render and delaying LCP by 800ms with the largest file being 90KB.
How to Fix:
Use Next.js CSS optimization by splitting the large CSS file into critical and non-critical parts. Inline critical CSS for above-the-fold content using next/head. Load non-critical CSS asynchronously with media='print' onload="this.media='all'" technique.
Add Resource Preconnect Headers
Medium Impact+8 points estimatedWhy It Matters:
External API calls to Spotify and Steam are adding 300-319ms delays without preconnection optimization.
How to Fix:
Add preconnect hints in your Next.js _document.js for critical origins: <link rel='preconnect' href='https://api.lanyard.rest' />, <link rel='preconnect' href='https://i.scdn.co' />, and <link rel='preconnect' href='https://avatars.steamstatic.com' />. Limit to 4 total preconnects for optimal performance.
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.
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.
Remove Unused JavaScript Code
172KB of unused JavaScript is delaying LCP by 1050ms and wasting bandwidth.
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