LCP
Largest Contentful Paint
5.1s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix Critical Rendering Path
How to optimize web.stag.dtv.onl
Fix Critical Rendering Path
High Impact+18 points estimated
Why It Matters
Render-blocking CSS delays First Contentful Paint by 440ms and forces sequential resource loading.
How to Fix
Inline critical CSS for above-the-fold content in Nuxt using @nuxtjs/critters. Use Vue's dynamic imports to load component-specific CSS (MenuTree, ProductListSkeleton) only when needed. Add preload hints for essential fonts like Inter to prevent render blocking.
0Poor
What This Score Means
A score of 36 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
303ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.02
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Nuxt/Vue website has severe performance issues with a critically low score of 36/100. The biggest problem is excessive JavaScript execution that's blocking the main thread for nearly 11 seconds, primarily caused by Google reCAPTCHA and oversized JavaScript bundles that are mostly unused code. The site takes over 5 seconds to display meaningful content and 23 seconds to become fully interactive, creating a frustrating user experience. Removing unused JavaScript (saving over 1MB), optimizing the reCAPTCHA implementation, and reducing CSS bloat could dramatically improve performance by several seconds and boost the score by 30+ points.
Other Optimization Recommendations
Eliminate Massive JavaScript Payload
High Impact+25 points estimatedWhy It Matters:
JavaScript execution blocks the main thread for 10.9 seconds and creates 2,040ms of blocking time, severely delaying user interactions.
How to Fix:
Remove duplicate reCAPTCHA scripts (3 identical 371KB files detected). Configure Nuxt to code-split large bundles using dynamic imports. Remove unused JavaScript from B4ZVMGEs.js (53% unused code). Defer non-critical third-party scripts like Facebook Pixel and Apple Auth until after page load.
Optimize LCP Image Loading
High Impact+15 points estimatedWhy It Matters:
Resource load delay of 2.6 seconds for LCP image pushes Largest Contentful Paint to 5.1 seconds.
How to Fix:
Add fetchpriority='high' and loading='eager' to hero banner image (already partially implemented). Use Nuxt Image module to serve WebP/AVIF formats automatically. Convert the 148KB GIF banner to video format for 50% size reduction. Implement proper image sizing to eliminate layout shifts.
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
Implement Efficient Asset Caching
66 KiB of static assets have no cache headers, missing opportunities to improve repeat visit performance and LCP by 500ms.
Minimize Main Thread Blocking Time
8.3 seconds of main thread work creates 1,910ms Total Blocking Time, severely impacting user interaction responsiveness.
Reduce Unused JavaScript Payloads
192 KiB of unused JavaScript is blocking page load, delaying both FCP and LCP by 900ms with potential 19-point score improvement.
Reduce Unused JavaScript Payload
594 KiB of unused JavaScript is delaying LCP by 150ms and increasing bundle size unnecessarily.