Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize clientflowatl.com
Render-blocking CSS delays FCP by 450ms and unused JavaScript wastes 42KB affecting LCP by 300ms.
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.
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.
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 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.
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.
Why 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.
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.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Nuxt Speed Tests
66 KiB of static assets have no cache headers, missing opportunities to improve repeat visit performance and LCP by 500ms.
8.3 seconds of main thread work creates 1,910ms Total Blocking Time, severely impacting user interaction responsiveness.
192 KiB of unused JavaScript is blocking page load, delaying both FCP and LCP by 900ms with potential 19-point score improvement.
594 KiB of unused JavaScript is delaying LCP by 150ms and increasing bundle size unnecessarily.