LCP
Largest Contentful Paint
1.8s
Good
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Render-Blocking CSS Resources
How to optimize corridor.soccer
Eliminate Render-Blocking CSS Resources
High Impact+3 points estimated
Why It Matters
CSS files are blocking initial page render and delaying LCP by 600ms.
How to Fix
Inline critical CSS for above-the-fold content directly in the HTML head. Use Next.js dynamic imports to defer non-critical CSS. Consider splitting the large 28KB CSS file into route-specific chunks using Next.js automatic CSS code splitting.
0Good
What This Score Means
A score of 97 falls in the "Good" 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
149ms
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 excellent performance with a score of 97/100, indicating very fast loading times for users. The biggest issue is render-blocking CSS files that are delaying the initial page display by 600ms, particularly a large stylesheet that could be optimized or split to load critical styles first. While the site loads quickly overall, there are opportunities to reduce unused code - specifically 203KB of unused JavaScript and 24KB of unused CSS that could be removed or deferred to improve efficiency. Additionally, optimizing the main logo image could save 47KB of bandwidth, and addressing legacy JavaScript polyfills could reduce bundle size by another 12KB.
Other Optimization Recommendations
Remove Unused CSS and JavaScript
High Impact+2 points estimatedWhy It Matters:
207KB of unused JavaScript and 24KB of unused CSS are unnecessarily inflating bundle sizes.
How to Fix:
Analyze your Next.js bundle with @next/bundle-analyzer to identify unused code. Implement dynamic imports for components not needed on initial load. Use tree-shaking by ensuring imports are ES6 module format and remove unused CSS classes from your stylesheets.
Optimize Image Sizing and Delivery
Medium Impact+1 point estimatedWhy It Matters:
The corridor shield image is 48KB larger than needed for its display dimensions.
How to Fix:
Configure Next.js Image component with proper responsive sizes prop to serve appropriately sized images. Use Next.js built-in image optimization with multiple breakpoints. Consider using priority prop for above-the-fold images to preload them.
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 Image Sizing and Delivery
The corridor shield image is 48KB larger than needed for its display dimensions.
Add fetchpriority=high to LCP Image
The LCP element (background texture SVG) lacks priority hints, delaying critical resource loading.
Reduce JavaScript Execution Time
3.5 seconds of JavaScript execution time is blocking the main thread and causing 2.5 seconds of Total Blocking Time.
Eliminate Unused JavaScript Code
1.44MB of unused JavaScript is blocking LCP by 900ms and consuming unnecessary network bandwidth.