Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize web.stag.dtv.onl
66 KiB of static assets have no cache headers, missing opportunities to improve repeat visit performance and LCP by 500ms.
Configure your Nuxt server to set long-term cache headers for fonts and images (Cache-Control: max-age=31536000). Use Nuxt's static file handling to automatically version assets. Set up CDN caching rules for your web-stag.dtv.onl domain.
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.
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 Nuxt/Vue website has severe performance issues with a critically low score of 33/100. The biggest problem is excessive JavaScript execution taking 8.3 seconds of main-thread work, which is blocking user interactions and causing a painful 1,910ms Total Blocking Time. The site is loading 192KB of unused JavaScript and suffering from render-blocking CSS files that delay content visibility by over 4.6 seconds. Reducing JavaScript payloads, removing unused code, and implementing proper caching (currently missing entirely) could dramatically improve performance and user experience.
Why It Matters:
192 KiB of unused JavaScript is blocking page load, delaying both FCP and LCP by 900ms with potential 19-point score improvement.
How to Fix:
In your Nuxt config, enable tree-shaking and code splitting. Split the large IGXVVuY5.js bundle using dynamic imports. Configure Swiper to load only needed modules. Use Nuxt's built-in bundle analyzer to identify and remove dead code.
Why It Matters:
8.3 seconds of main thread work creates 1,910ms Total Blocking Time, severely impacting user interaction responsiveness.
How to Fix:
Optimize your Vue components to reduce forced reflows by batching DOM reads/writes. Use Nuxt's asyncData or fetch hooks to move heavy computations off the main thread. Implement virtual scrolling for long product lists using @tanstack/vue-virtual.
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.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Nuxt Speed Tests
8.3 seconds of main thread work creates 1,910ms Total Blocking Time, severely impacting user interaction responsiveness.
192 KiB of unused JavaScript is blocking page load, delaying both FCP and LCP by 900ms with potential 19-point score improvement.
594 KiB of unused JavaScript is delaying LCP by 150ms and increasing bundle size unnecessarily.
The LCP element (Nokia X20 image) lacks fetchpriority=high, causing unnecessary delay in resource loading.