Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize payfast.greenn.com.br
Critical resources have no cache headers, forcing users to re-download 600KB on every visit.
Configure Nuxt's nitro.storage with appropriate cache headers for static assets. Set Cache-Control headers for images (1 year) and CSS/JS (1 month). Use Nuxt's built-in static asset optimization by placing images in the public directory.
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.
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 site has poor performance with a score of 65/100, primarily due to extremely slow loading times that hurt user experience. The biggest problem is the Largest Contentful Paint taking 10.5 seconds, largely caused by an oversized 608KB product image that could be reduced by over 600KB through modern formats like WebP and proper sizing. The site is also loading 175KB of unused JavaScript code and has render-blocking CSS files that delay the initial page display by nearly 300ms. Fixing the image optimization alone could improve loading speed by 3.5+ seconds and significantly boost the performance score.
Why It Matters:
The main product image (608KB) is severely oversized and delays LCP by 3.55 seconds.
How to Fix:
Use Nuxt Image module with responsive breakpoints and WebP format. Add srcset with appropriate sizes for mobile/desktop. Implement server-side image optimization or use a CDN like Cloudinary with Nuxt's @nuxtjs/cloudinary module.
Why It Matters:
175KB of unused JavaScript delays LCP by 750ms and blocks the main thread unnecessarily.
How to Fix:
Enable Nuxt's tree-shaking by setting nitro.experimental.wasm = true. Use dynamic imports for heavy components with defineAsyncComponent(). Run nuxt analyze to identify unused dependencies and remove them from your bundle.
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
Images without explicit dimensions cause layout shifts and prevent proper space reservation during page load.
Multiple redirects delay page load by 21.1 seconds, severely impacting both LCP and FCP metrics.
Missing cache headers force users to re-download 222 KiB on every visit, slowing repeat page loads.
Poor image optimization is causing 152 KiB waste and 900ms LCP delay for critical product images.