LCP
Largest Contentful Paint
3.0s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Add Priority Hint to LCP Image
How to optimize corridor.soccer
Add Priority Hint to LCP Image
High Impact+3 points estimated
Why It Matters
The hero image lacks fetchpriority='high', which could improve LCP timing and user perception of loading speed.
How to Fix
Add fetchpriority='high' attribute to the Corridor Soccer Association logo image in your Next.js Image component. Update the component to include priority={true} prop which automatically adds fetchpriority='high' for above-the-fold images.
0Good
What This Score Means
A score of 94 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
111ms
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 performs well overall with a score of 94/100, but has room for improvement in loading speed. The biggest issue is slow Largest Contentful Paint at 3.0 seconds, primarily caused by render-blocking CSS files that delay page rendering by an estimated 600ms. The main hero image (Corridor Soccer Association logo) is oversized for its display dimensions, wasting 47KB of unnecessary data transfer, and could benefit from adding fetchpriority=high to load faster. Additionally, the site is loading 204KB of unused JavaScript code that could be removed or deferred to further optimize performance.
Other Optimization Recommendations
Optimize Hero Image Sizing
High Impact+5 points estimatedWhy It Matters:
The LCP image wastes 47KB by serving oversized dimensions (1280x1671 vs displayed 350x457), delaying LCP by 450ms.
How to Fix:
Update your Next.js Image component's sizes prop to match actual display dimensions. Set sizes='(max-width: 768px) 350px, 457px' and ensure your image source provides appropriately sized variants. Consider using fill prop with object-fit for responsive containers.
Remove Unused CSS and JavaScript
High Impact+8 points estimatedWhy It Matters:
204KB of unused JavaScript and 24KB of unused CSS are blocking rendering and delaying both FCP by 600ms and LCP by 300ms.
How to Fix:
Run Next.js bundle analyzer to identify unused code chunks. Split large components using dynamic imports with ssr: false for client-only code. Remove unused Tailwind CSS classes by configuring purge options in tailwind.config.js to scan only necessary files.
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.
Eliminate Render-Blocking CSS Resources
CSS files are blocking initial page render and delaying LCP by 600ms.
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.