LCP
Largest Contentful Paint
10.1s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Remove Unused JavaScript Bundles
How to optimize web.stag.dtv.onl
Remove Unused JavaScript Bundles
High Impact+30 points estimated
Why It Matters
Unused JavaScript accounts for 1,512 KiB of wasted bytes and blocks main thread for 3.1 seconds, severely degrading LCP and interactivity.
How to Fix
Enable tree-shaking in your Nuxt build configuration. Use dynamic imports for YouTube embeds and heavy components. Configure Webpack bundle splitting to load only required code per route. Remove duplicate YouTube player scripts.
0Poor
What This Score Means
A score of 33 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
361ms
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 Nuxt/Vue e-commerce site has severe performance problems with a critically low score of 33/100. The biggest issue is massive amounts of unused JavaScript (1,512 KiB of wasted code), particularly from YouTube embeds and the main application bundle, which is causing an extremely slow Time to Interactive of 22.8 seconds and poor Core Web Vitals across the board. The site is also suffering from render-blocking CSS files that delay the First Contentful Paint by 1.2 seconds, and 106 KiB of unused CSS that could be eliminated. Removing or deferring unnecessary JavaScript, especially YouTube components that may not be critical for initial page load, and optimizing the CSS delivery could potentially improve the performance score by 40+ points and dramatically reduce load times from the current 10+ seconds.
Other Optimization Recommendations
Eliminate Render-Blocking CSS Resources
High Impact+25 points estimatedWhy It Matters:
Critical CSS files are blocking initial page render, delaying FCP by 1,200ms and significantly impacting user experience.
How to Fix:
Implement critical CSS inlining for above-the-fold content in your Nuxt config. Use asyncData or fetch hooks to load non-critical CSS asynchronously. Split CSS bundles and defer loading of component-specific stylesheets until needed.
Optimize LCP Image Loading
High Impact+20 points estimatedWhy It Matters:
The LCP image lacks fetchpriority optimization and contributes to a 10.1 second LCP score, failing Core Web Vitals thresholds.
How to Fix:
Add fetchpriority='high' to the main carousel image element. Implement @nuxt/image module with automatic WebP conversion and responsive sizing. Preload the LCP image using link rel='preload' in the document head.
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 Nuxt Speed Tests
Nuxt Performance Resources
Fix Resource Load Delays
LCP is delayed by 2.55 seconds due to resource load delays, making the page feel unresponsive.
Remove Unused CSS and JavaScript
795KB of unused JavaScript and 90KB of unused CSS waste bandwidth and slow down parsing.
Fix Critical Rendering Path
Render-blocking CSS delays First Contentful Paint by 440ms and forces sequential resource loading.
Eliminate Massive JavaScript Payload
JavaScript execution blocks the main thread for 10.9 seconds and creates 2,040ms of blocking time, severely delaying user interactions.