Optimize Cookiebot Script Loading

How to optimize fit.kitchen.at

Nuxt SiteScore: 58/100Analyzed January 2026

Optimize Cookiebot Script Loading

High Impact+20 points estimated

Why It Matters

The render-blocking Cookiebot script is delaying FCP and LCP by 300ms with a 1.7-second network chain.

How to Fix

Move Cookiebot to load asynchronously using Nuxt's script tag with 'defer' attribute in nuxt.config.js head section. Consider using @nuxtjs/gtm for better script management. Implement cookie banner as a non-blocking component that loads after page interaction.

0Needs Improvement

What This Score Means

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

8.2s
Poor

Good: < 2.5s

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

INP

Interaction to Next Paint

318ms
Needs Improvement

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 website has poor performance with a score of 58/100, primarily due to extremely slow loading times. The biggest problem is the Largest Contentful Paint taking 8.2 seconds, which is mainly caused by a blocking cookie consent script (Cookiebot) that prevents the page from rendering properly. The site is also loading 246 KiB of unused JavaScript and serving oversized images that waste 201 KiB of bandwidth. Deferring or replacing the cookie consent solution, removing unused code, and properly sizing images could improve the score by 30+ points and dramatically enhance user experience.

Other Optimization Recommendations

Remove Unused JavaScript Bundles

High Impact+25 points estimated

Why It Matters:

Unused JavaScript is consuming 246 KiB and delaying LCP by 1.2 seconds with blocking execution time.

How to Fix:

Analyze your Nuxt bundles using webpack-bundle-analyzer to identify unused code. Enable tree-shaking in nuxt.config.js with 'build.optimization.splitChunks'. Use dynamic imports for non-critical components with Vue's defineAsyncComponent().

Fix Image Responsive Sizing

Medium Impact+12 points estimated

Why It Matters:

Images are 201 KiB oversized, served at 800x600 but displayed at 378x284, impacting LCP by 150ms.

How to Fix:

Update your Nuxt Image configuration to generate properly sized images using @nuxt/image module. Set appropriate sizes attribute matching your CSS breakpoints. Use 'fit: cover' and 'quality: 80' in your nuxt.config.js image options for optimal compression.

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