LCP
Largest Contentful Paint
7.5s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize JavaScript Execution Performance
How to optimize olecams.com
Next.js SiteScore: 52/100Analyzed January 2026
Optimize JavaScript Execution Performance
Medium Impact+8 points estimated
Why It Matters
2.3 seconds of JavaScript execution blocks the main thread, creating 700ms of Total Blocking Time.
How to Fix
Move Google Analytics and tracking scripts to load asynchronously using Next.js Script component with strategy='afterInteractive'. Break down large JavaScript tasks in dd3eb256d83950cf.js into smaller chunks using setTimeout or requestIdleCallback. Consider server-side rendering more content to reduce client-side JavaScript work.
0Needs Improvement
What This Score Means
A score of 52 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
320ms
Needs Improvement
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 52/100, indicating significant user experience issues. The biggest problem is a page redirect that's wasting 770ms before users even reach the content, combined with 644KB of unused JavaScript that's severely slowing down page loading times. The site's Largest Contentful Paint takes 7.5 seconds (extremely slow) and Time to Interactive is 15.5 seconds, meaning users wait over 15 seconds before they can properly interact with the page. Eliminating the redirect, removing unused JavaScript code, and optimizing the JavaScript build process could dramatically improve performance by several seconds and boost the score by 30+ points.
Other Optimization Recommendations
Eliminate Multiple Page Redirects
High Impact+15 points estimatedWhy It Matters:
Redirects add 770ms delay before any content can load, significantly impacting both FCP and LCP.
How to Fix:
Update your Next.js configuration to serve the Spanish version directly without redirecting from the root domain. Add a 'locale' setting in next.config.js and ensure proper routing setup. Update internal links to point directly to /es paths.
Reduce Unused JavaScript Bundles
High Impact+12 points estimatedWhy It Matters:
644KB of unused JavaScript delays LCP by 800ms and wastes bandwidth on unnecessary code.
How to Fix:
Enable Next.js dynamic imports for components not needed immediately. Use next/dynamic with ssr: false for client-only components. Implement code splitting at the page level and analyze your bundle with @next/bundle-analyzer to identify oversized chunks.
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
Eliminate Duplicate JavaScript Modules
175 KiB of duplicated JavaScript from Nike Design System components is loaded multiple times across bundles.
Fix LCP Image Discovery
The LCP image is not discoverable in the initial HTML, causing a 4-second resource load delay.
Remove Unused JavaScript Code
460 KiB of unused JavaScript is blocking the main thread for 7.3 seconds and delaying LCP by 2.4 seconds.
Fix Page Redirects Chain
Multiple redirects add 1.53 seconds delay before the page even starts loading, directly impacting both FCP and LCP.
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