Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize fit.kitchen.at
The render-blocking Cookiebot script is delaying FCP and LCP by 300ms with a 1.7-second network chain.
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.
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.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
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.
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().
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.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Nuxt Speed Tests
Static assets have only 60-second cache lifetime, missing 2MB of potential cache savings and forcing unnecessary re-downloads.
2.7MB of unused JavaScript is blocking rendering and adding 16 seconds to LCP, with moment.js locale files being 93% unused.
Multiple redirects are adding 25.7 seconds to your page load time, severely impacting both LCP and FCP.
654 KiB of resources with poor cache policies are forcing unnecessary re-downloads on repeat visits.
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.