Remove Unused JavaScript Code

How to optimize web.stag.dtv.onl

Nuxt SiteScore: 55/100Analyzed May 2026Re-analyze this site

Remove Unused JavaScript Code

High Impact+12 points estimated

Why It Matters

349 KiB of unused JavaScript is increasing bundle size and slowing script evaluation by 1.35 seconds.

How to Fix

Use Nuxt's tree-shaking capabilities to eliminate dead code from C_aWqksD.js bundle. Implement dynamic imports for Google OAuth and Apple Sign In scripts to load only when needed. Configure Vite's rollup options to split vendor chunks more efficiently.

0Needs Improvement

What This Score Means

A score of 55 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

LCP

Largest Contentful Paint

12.8s
Poor

Good: < 2.5s

Measures how long it takes for the main content to appear on screen

INP

Interaction to Next Paint

157ms
Good

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 poor performance with a score of 55/100, indicating significant user experience issues. The biggest problem is render-blocking CSS files that are delaying page rendering by 1.4 seconds, combined with excessive unused JavaScript (349 KiB) and CSS (106 KiB) that's slowing down the initial load. The site's First Contentful Paint takes a sluggish 5.4 seconds and Largest Contentful Paint reaches an unacceptable 12.8 seconds, well beyond Google's recommended thresholds. Immediate improvements should focus on deferring non-critical CSS, removing unused code, and optimizing the large JavaScript bundles to potentially improve the performance score by 30+ points and dramatically enhance user experience.

Other Optimization Recommendations

Eliminate Render Blocking CSS Resources

High Impact+15 points estimated

Why It Matters:

Critical CSS files are blocking page render for 1.4 seconds, severely delaying First Contentful Paint and LCP.

How to Fix:

Use Nuxt's CSS extraction features to inline critical CSS in the <head>. Defer non-critical CSS files like ModalListProductProgram.css and MenuTree.css using media='print' onload technique. Configure Vite to optimize CSS chunking for better loading performance.

Optimize Image Delivery and Sizing

Medium Impact+8 points estimated

Why It Matters:

Oversized placeholder images waste 17KB and lack proper dimensions causing layout shifts.

How to Fix:

Use Nuxt Image module with responsive breakpoints for placeholder.png and logo.png. Convert images to WebP format using @nuxt/image providers. Add explicit width/height attributes to all img elements to prevent CLS issues.

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

More Nuxt Speed Tests

Nuxt Performance Resources

Frequently Asked Questions