LCP
Largest Contentful Paint
3.3s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix Multiple Page Redirects
How to optimize web.stag.dtv.onl
Fix Multiple Page Redirects
High Impact+25 points estimated
Why It Matters
The HTTP to HTTPS redirect is delaying LCP and FCP by 650ms, significantly impacting initial page load.
How to Fix
Update your Nuxt configuration to enforce HTTPS redirects at the server level using Nitro's redirect rules. Configure your hosting provider to handle redirects without additional round trips. Update all internal links to use HTTPS directly.
0Needs Improvement
What This Score Means
A score of 60 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
151ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.16
Needs Improvement
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Nuxt/Vue website has poor performance with a score of 60/100, primarily caused by excessive JavaScript execution that's blocking the page for over 5 seconds. The biggest issue is a problematic redirect from HTTP to HTTPS that wastes 630ms, combined with 115KB of unused CSS (mostly from reCAPTCHA) and over 1MB of unnecessary JavaScript code. Additionally, the site suffers from significant layout shifts as content loads, creating a jarring user experience. Fixing the redirect, removing unused code, and optimizing the main content area could easily improve the score by 25+ points and dramatically reduce the 24-second load time.
Other Optimization Recommendations
Eliminate Layout Shifts From Content
High Impact+15 points estimatedWhy It Matters:
Two major layout shifts with a CLS score of 0.158 are causing visual instability and poor user experience.
How to Fix:
Add explicit width and height attributes to all images in your Vue components. Use CSS aspect-ratio or min-height to reserve space for dynamically loaded content sections. Implement skeleton screens for the product listing areas that are causing the largest shifts.
Reduce Unused JavaScript and CSS
Medium Impact+12 points estimatedWhy It Matters:
Over 1MB of unused JavaScript and 115KB of unused CSS are bloating the initial bundle and blocking rendering.
How to Fix:
Configure Nuxt's code splitting to defer non-critical components using lazy loading. Remove or optimize the reCAPTCHA implementation to load only when needed. Use Nuxt's CSS extraction and purging features to eliminate unused Tailwind CSS classes from your production build.
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.