LCP
Largest Contentful Paint
8.3s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce JavaScript Bundle Size
How to optimize collect.fifa.com
Reduce JavaScript Bundle Size
High Impact+20 points estimated
Why It Matters
Unused JavaScript totals 1.6MB and blocks main thread for 4.7 seconds, causing 630ms input delay.
How to Fix
Enable tree shaking in Next.js build configuration. Code split large components using dynamic imports with React.lazy(). Remove legacy polyfills from Paysafe and other third-party scripts by updating to modern versions that support ES6+ baseline features.
0Poor
What This Score Means
A score of 32 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
625ms
Poor
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.12
Needs Improvement
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This FIFA Collect Next.js site has severe performance issues with a score of just 32/100. The biggest problem is an enormous 22MB page size combined with massive JavaScript execution blocking the main thread for over 76 seconds, causing extremely poor user experience with loading times exceeding 8 seconds. The site loads nearly 1.6MB of unused JavaScript and suffers from major layout shifts due to unsized images and consent banners, while serving unoptimized 4.5MB PNG images that could be compressed by 75% using modern formats like WebP. Reducing the JavaScript payload, optimizing images, and implementing proper caching could potentially improve the score by 40+ points and dramatically enhance user experience.
Other Optimization Recommendations
Optimize Large Image Assets
High Impact+25 points estimatedWhy It Matters:
Images consume over 22MB with the largest being 4.5MB, severely impacting LCP at 8.3 seconds.
How to Fix:
Convert PNG images to WebP/AVIF format using Next.js Image component with quality={75}. Implement responsive images with proper sizes attribute. Add fetchpriority='high' to the LCP image and ensure it's discoverable in initial HTML without lazy loading.
Fix Layout Shift Issues
Medium Impact+8 points estimatedWhy It Matters:
CLS score of 0.123 caused by carousel and cookie banner shifting content during load.
How to Fix:
Add explicit dimensions to carousel container using CSS aspect-ratio or fixed height. Preload critical fonts with font-display: swap and add fallback font metrics. Reserve space for OneTrust cookie banner with min-height CSS to prevent content jumps.
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
Fix Layout Shift Issues
CLS score of 0.123 caused by carousel and cookie banner shifting content during load.
Optimize Large Image Assets
Images consume over 22MB with the largest being 4.5MB, severely impacting LCP at 8.3 seconds.
Fix Critical Element Render Delay
The LCP element (H1 heading) has a massive 4.3 second render delay, severely impacting page load performance.
Update JavaScript Build Target
Legacy JavaScript polyfills add 20KB of unnecessary code since modern browsers support these features natively.