LCP
Largest Contentful Paint
6.8s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Responsive Image Sizes
How to optimize fit.kitchen.at
Nuxt SiteScore: 65/100Analyzed January 2026
Optimize Responsive Image Sizes
High Impact+15 points estimated
Why It Matters
Images are 133 KiB larger than needed for their display dimensions, delaying LCP by 150ms.
How to Fix
Configure Nuxt Image module with proper breakpoints: add 'sizes' prop matching your CSS breakpoints (378px mobile). Use '@nuxt/image' with 'fit=cover&f=webp' and implement multiple size variants. Set 'densities=[1,2]' for retina support.
0Needs Improvement
What This Score Means
A score of 65 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
268ms
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 65/100, indicating significant user experience issues. The biggest problem is excessive unused JavaScript (223 KiB) that's blocking page interactivity and causing the Largest Contentful Paint to take a slow 6.8 seconds. The site is also serving oversized images that waste 133 KiB of bandwidth and could be optimized with responsive sizing. Removing unused JavaScript code and implementing proper image optimization could potentially improve load times by nearly a second and boost the performance score substantially.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+25 points estimatedWhy It Matters:
223 KiB of unused JavaScript is delaying LCP by 900ms and blocking the main thread.
How to Fix:
Use Nuxt's tree-shaking by enabling 'experimental.payloadExtraction' and 'build.extractCSS'. Split your bundle with dynamic imports for routes and components. Remove unused libraries from your Nuxt modules array and audit third-party scripts.
Reduce Main Thread Blocking
Medium Impact+10 points estimatedWhy It Matters:
270ms maximum FID indicates long tasks are blocking user interactions after page load.
How to Fix:
Wrap heavy computations in Vue's 'nextTick()' or use Web Workers for data processing. Implement code splitting with Nuxt's lazy loading for components. Use 'setTimeout' to break up long-running JavaScript tasks into smaller chunks.
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
Implement Proper Caching Strategy
Static assets have only 60-second cache lifetime, missing 2MB of potential cache savings and forcing unnecessary re-downloads.
Reduce Unused JavaScript Payloads
2.7MB of unused JavaScript is blocking rendering and adding 16 seconds to LCP, with moment.js locale files being 93% unused.
Remove Page Redirects Chain
Multiple redirects are adding 25.7 seconds to your page load time, severely impacting both LCP and FCP.
Implement Efficient Resource Caching
654 KiB of resources with poor cache policies are forcing unnecessary re-downloads on repeat visits.
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