LCP
Largest Contentful Paint
3.5s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Render Blocking CSS
How to optimize web.stag.dtv.onl
Eliminate Render Blocking CSS
High Impact+12 points estimated
Why It Matters
CSS files are blocking initial render, delaying FCP by 400ms and preventing content from appearing quickly.
How to Fix
In your Nuxt config, inline critical CSS for above-the-fold content using @nuxtjs/critters. Defer non-critical CSS like swiper-vue.j0Ydk9q6.css using media='print' onload='this.media="all"'. Remove unused CSS rules (88 KiB identified) by purging Tailwind CSS and external stylesheets.
0Needs Improvement
What This Score Means
A score of 80 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
174ms
Good
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 website has decent performance with a score of 80/100, but has significant room for improvement in loading speed. The biggest issue is render-blocking CSS files that are delaying the page's initial paint by over 400ms, particularly a large Swiper component stylesheet. The site is also bloated with 594KB of unused JavaScript and 88KB of unused CSS that could be removed or deferred to improve loading times. Additionally, the Time to Interactive is concerningly slow at 10.4 seconds, meaning users have to wait a long time before they can properly interact with the page, which could hurt user experience and conversions.
Other Optimization Recommendations
Reduce Unused JavaScript Payload
High Impact+10 points estimatedWhy It Matters:
594 KiB of unused JavaScript is delaying LCP by 150ms and increasing bundle size unnecessarily.
How to Fix:
Code-split your Nuxt application using dynamic imports for non-critical components. Tree-shake unused code from index-CTLE3WE9-1777896204612.js and BXQMJ5Lt.js. Lazy load Google Sign-In and Apple ID authentication scripts only when authentication is needed.
Optimize LCP Image Priority
Medium Impact+8 points estimatedWhy It Matters:
The LCP element (Nokia X20 image) lacks fetchpriority=high, causing unnecessary delay in resource loading.
How to Fix:
Add fetchpriority='high' to your LCP image in the Nuxt template. Use Nuxt Image component with priority prop for above-the-fold images. Preload the LCP image URL using <link rel='preload' as='image'> in your app.head configuration.
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
Reduce Unused JavaScript Payload
594 KiB of unused JavaScript is delaying LCP by 150ms and increasing bundle size unnecessarily.
Optimize LCP Image Priority
The LCP element (Nokia X20 image) lacks fetchpriority=high, causing unnecessary delay in resource loading.
Optimize Image Assets and Caching
Oversized logo image and poor cache headers waste 29KB and slow repeat visits.
Fix Forced Reflow Issues
365ms of forced reflows block the main thread and degrade rendering performance significantly.