LCP
Largest Contentful Paint
5.0s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce JavaScript Execution Time
How to optimize forte.forte.bluheadless.eu.stage.filoblutest.com
Next.js SiteScore: 50/100Analyzed February 2026
Reduce JavaScript Execution Time
High Impact+25 points estimated
Why It Matters
Main thread is blocked for 4.6 seconds with 2.4s of JavaScript execution time, causing a Total Blocking Time of 1,150ms and severely impacting user interaction.
How to Fix
Implement dynamic imports in Next.js to code-split large components. Remove duplicate JavaScript modules (115KB+ wasted from @mui/material across bundles). Use Next.js bundle analyzer to identify and eliminate unused code from the 107KB of unused JavaScript in _app bundle.
0Needs Improvement
What This Score Means
A score of 50 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
660ms
Poor
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/React site has poor performance with a score of 50/100, indicating significant user experience issues. The biggest problem is excessive JavaScript execution taking 4.6 seconds to process, which is blocking the main thread and causing a devastating 1,150ms delay before users can interact with the page. The site is also suffering from a slow Largest Contentful Paint of 5.0 seconds due to poor resource loading delays and unoptimized images that could be compressed by 384KB. Immediate fixes should focus on reducing JavaScript bundle sizes, eliminating duplicate code across multiple chunks, and optimizing image compression to dramatically improve loading speeds.
Other Optimization Recommendations
Optimize LCP Image Loading
High Impact+15 points estimatedWhy It Matters:
LCP is delayed to 5.0 seconds due to a 2.4 second resource load delay and oversized hero image (309KB).
How to Fix:
Add fetchpriority='high' to the hero image as indicated by LCP discovery audit. Increase image compression to reduce the 197KB wasted bytes. Implement Next.js Image component with priority prop for the hero image to enable preloading.
Implement Efficient Caching Strategy
Medium Impact+8 points estimatedWhy It Matters:
Poor cache lifetimes waste 1,380KB on repeat visits, slowing down returning user experience.
How to Fix:
Configure Next.js static asset caching with longer cache headers (1 year for immutable assets). Set up CDN cache headers for images to extend beyond current 1-hour TTL. Use Next.js built-in automatic static optimization for better caching of static pages.
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
Reduce Main Thread Blocking Time
JavaScript execution blocks the main thread for 10.5 seconds, creating 4.34 seconds of total blocking time.
Eliminate Render-Blocking CSS Resources
Two CSS files are delaying initial page render and LCP by 490ms in the critical path.
Remove Unused JavaScript Code
1,636 KiB of unused JavaScript is blocking LCP by 2.85 seconds and preventing user interactions.
Optimize Hero Image Loading
The main hero image is 102KB oversized and delays LCP by 400ms with poor responsive sizing.
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