Eliminate Unused JavaScript Code

How to optimize fit.kitchen.at

Nuxt SiteScore: 89/100Analyzed January 2026

Eliminate Unused JavaScript Code

High Impact+8 points estimated

Why It Matters

Unused JavaScript wastes 224 KiB and delays LCP by 600ms, severely impacting page performance.

How to Fix

Analyze your Nuxt bundle using @nuxt/devtools to identify unused code. Split large chunks by implementing dynamic imports for components and pages. Configure webpack-bundle-analyzer to remove unused dependencies from your build process.

0Needs Improvement

What This Score Means

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

3.6s
Needs Improvement

Good: < 2.5s

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

INP

Interaction to Next Paint

156ms
Good

Good: < 200ms

Measures how quickly the page responds to user interactions

CLS

Cumulative Layout Shift

0.03
Good

Good: < 0.1

Measures visual stability - how much content shifts during page load

AI Performance Analysis

This Nuxt/Vue site has good performance with a score of 89/100, but there's still room for improvement. The biggest issue is excessive unused JavaScript code, which wastes 224 KB and adds 600ms to loading time, directly impacting the Largest Contentful Paint (3.6 seconds). The site is also serving oversized images that are larger than their display dimensions, wasting an additional 201 KB of bandwidth. Cleaning up unused JavaScript bundles and properly sizing images could push this site into the excellent performance range and improve user experience significantly.

Other Optimization Recommendations

Optimize Recipe Image Sizing

High Impact+6 points estimated

Why It Matters:

Oversized recipe images waste 201 KiB and delay LCP by 300ms due to serving 800x600 images for 378x284 display.

How to Fix:

Configure Nuxt Image module to generate proper responsive breakpoints with sizes='(max-width: 480px) 100vw, (max-width: 640px) 50vw, 378px'. Update your recipe card component to use format='webp' and quality='80' parameters. Implement proper srcset generation for different screen densities.

Remove Unused CSS Rules

Medium Impact+3 points estimated

Why It Matters:

Cookiebot dialog CSS contains 82% unused rules, wasting 11 KiB of network resources unnecessarily.

How to Fix:

Configure PurgeCSS in your Nuxt config to remove unused Cookiebot styles. Move cookie consent CSS to a separate chunk that loads only when needed. Use Nuxt's css extraction to defer non-critical stylesheets below the fold.

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

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