Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize olecams.com
Multiple redirects add 760ms delay to both LCP and FCP metrics.
Update your Next.js configuration to serve the Spanish version directly without redirects. In next.config.js, configure proper locale routing with 'redirect: false' for the default locale. Update internal links to point directly to '/es' URLs instead of root paths that redirect.
A score of 47 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.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This Next.js site has poor performance with a score of 47/100, indicating significant user experience issues. The biggest problem is excessive JavaScript blocking the page, with 6.1 seconds of main-thread work and 645 KiB of unused JavaScript code that's delaying your Largest Contentful Paint by 2.6 seconds. Additionally, the site has an unnecessary redirect that wastes 760ms on every page load, and the page takes a painfully long 16 seconds to become fully interactive. Removing unused JavaScript, eliminating the redirect, and optimizing your Next.js bundle could improve your score by 30+ points and dramatically speed up the site.
Why It Matters:
645 KiB of unused JavaScript delays LCP by 2.55 seconds and blocks user interactions.
How to Fix:
Use Next.js dynamic imports to code-split large components. Run 'npx next build --analyze' to identify unused chunks. Implement tree-shaking by importing only needed functions from libraries instead of entire packages. Configure webpack-bundle-analyzer to remove dead code from your build.
Why It Matters:
2.7 seconds of JavaScript execution creates 1.25 seconds of Total Blocking Time.
How to Fix:
Split large Next.js chunks using dynamic imports with loading states. Move third-party scripts like Clarity and GTM to load after page interactive using Next.js Script component with strategy='lazyOnload'. Optimize React components by implementing React.memo() for heavy rendering components.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Next.js Speed Tests
175 KiB of duplicated JavaScript from Nike Design System components is loaded multiple times across bundles.
The LCP image is not discoverable in the initial HTML, causing a 4-second resource load delay.
460 KiB of unused JavaScript is blocking the main thread for 7.3 seconds and delaying LCP by 2.4 seconds.
Multiple redirects add 1.53 seconds delay before the page even starts loading, directly impacting both FCP and LCP.
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.