LCP
Largest Contentful Paint
12.0s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix Image Dimensions and Loading
How to optimize clientflowatl.com
Fix Image Dimensions and Loading
High Impact+25 points estimated
Why It Matters
Unsized images cause 0.371 CLS score and delay LCP by 4.65 seconds with poor image optimization.
How to Fix
Add explicit width and height attributes to all img elements, especially the brand logo and main content images. Remove loading='lazy' from above-the-fold images and add fetchpriority='high' to the LCP image. In your Nuxt config, configure @nuxt/image module to automatically optimize and serve WebP formats.
0Poor
What This Score Means
A score of 46 falls in the "Poor" 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
136ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.37
Poor
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 46/100. The biggest problem is an extremely slow Largest Contentful Paint of 12 seconds, caused by oversized images that lack proper dimensions and aren't optimized for web delivery. The site's main logo image is nearly 1MB but only displays at 225x75 pixels, and several images are causing significant layout shifts as they load without specified dimensions. Optimizing and properly sizing images, adding explicit width/height attributes, and improving caching could reduce load times by several seconds and dramatically improve the user experience.
Other Optimization Recommendations
Optimize Critical Resource Loading
High Impact+18 points estimatedWhy It Matters:
Render-blocking CSS delays FCP by 450ms and unused JavaScript wastes 42KB affecting LCP by 300ms.
How to Fix:
Move critical CSS inline in your Nuxt app.vue or use 'nitro.inlineDynamicImports: true' in nuxt.config.js. Split JavaScript bundles using dynamic imports for non-critical components. Remove unused code from the main bundle by analyzing with webpack-bundle-analyzer.
Implement Efficient Caching Strategy
Medium Impact+12 points estimatedWhy It Matters:
Poor cache lifetimes waste 645KB on repeat visits and could improve LCP by 3.15 seconds.
How to Fix:
Configure longer cache headers for static assets in your deployment setup (Netlify/Vercel headers file or server config). Set cache-control headers to 'max-age=31536000' for images and assets. Use Nuxt's built-in static asset optimization with proper hashing for cache busting.
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
Related Performance Analyses
More Nuxt Speed Tests
Nuxt Performance Resources
Fix Resource Load Delays
LCP is delayed by 2.55 seconds due to resource load delays, making the page feel unresponsive.
Remove Unused CSS and JavaScript
795KB of unused JavaScript and 90KB of unused CSS waste bandwidth and slow down parsing.
Fix Critical Rendering Path
Render-blocking CSS delays First Contentful Paint by 440ms and forces sequential resource loading.
Eliminate Massive JavaScript Payload
JavaScript execution blocks the main thread for 10.9 seconds and creates 2,040ms of blocking time, severely delaying user interactions.