LCP
Largest Contentful Paint
10.5s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Implement Proper Browser Caching
How to optimize payfast.greenn.com.br
Implement Proper Browser Caching
Medium Impact+12 points estimated
Why It Matters
Critical resources have no cache headers, forcing users to re-download 600KB on every visit.
How to Fix
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.
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
176ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.00
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
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.
Other Optimization Recommendations
Optimize Product Image Delivery
High Impact+25 points estimatedWhy 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.
Remove Unused JavaScript Code
High Impact+18 points estimatedWhy 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.
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 LCP Image Discovery Issues
The LCP image isn't discoverable in initial HTML and lacks priority hints, delaying first paint by 8.5 seconds.
Eliminate Unused CSS and JavaScript
650KB of unused code blocks rendering for 2.7 seconds and wastes 419KB of JavaScript execution time.
Optimize Massive Image Payloads
The 2.8MB notification banner image alone causes 5.4 second LCP delay and consumes excessive bandwidth.
Implement Efficient Asset Caching
66 KiB of static assets have no cache headers, missing opportunities to improve repeat visit performance and LCP by 500ms.