LCP
Largest Contentful Paint
10.4s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Implement Effective Caching Strategy
How to optimize payfast.stg.greenn.com.br
Nuxt SiteScore: 66/100Analyzed February 2026
Implement Effective Caching Strategy
Medium Impact+12 points estimated
Why It Matters
Missing cache headers are forcing repeat downloads of 600 KiB of resources that could be cached.
How to Fix
Configure your S3 bucket to serve images with long cache headers (Cache-Control: max-age=31536000). In your Nuxt config, set up proper cache headers for static assets. For the main product image, add versioning to the filename to enable aggressive caching while maintaining update capability.
0Needs Improvement
What This Score Means
A score of 66 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
171ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.01
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 66/100, primarily due to extremely slow loading times with Largest Contentful Paint taking 10.4 seconds. The biggest issue is inefficient image delivery, where a 608KB product image is oversized for its display dimensions and lacks modern formatting like WebP, causing an estimated 3.2-second delay. The site also suffers from render-blocking CSS files and 175KB of unused JavaScript that could be removed or deferred. Fixing image optimization alone could save over 600KB and dramatically improve loading speed, while addressing caching policies and removing unused code would provide additional performance gains.
Other Optimization Recommendations
Optimize Image Delivery and Formats
High Impact+25 points estimatedWhy It Matters:
Images are causing a 3.2 second delay to LCP and consuming 634 KiB of unnecessary bandwidth.
How to Fix:
Convert the main product image (Ur9nPRKNPw.jpg) to WebP format to save 548 KiB. Resize images to match their display dimensions - the product image is 800x450 but displays at 158x89. In Nuxt, use the @nuxt/image module with <NuxtImg> component to automatically optimize and serve responsive images.
Remove Unused JavaScript Code
High Impact+18 points estimatedWhy It Matters:
Unused JavaScript is adding 175 KiB of bloat and delaying LCP by 750ms while blocking the main thread.
How to Fix:
Analyze your Nuxt bundles using 'npx nuxi analyze' to identify unused code. Split large components using dynamic imports with lazy loading. Remove unused dependencies from package.json and configure tree-shaking in your Nuxt config to eliminate dead code from the final bundle.
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
Remove Unused JavaScript Code
Unused JavaScript is adding 175 KiB of bloat and delaying LCP by 750ms while blocking the main thread.
Remove Unused Code and Dependencies
Unused JavaScript (238 KiB) and CSS (55 KiB) are bloating bundle size without providing value.
Eliminate Render Blocking CSS
CSS files are blocking first contentful paint by 550ms, delaying critical page rendering.
Optimize Image Delivery and Formats
Images are causing a 3.2 second delay to LCP and consuming 634 KiB of unnecessary bandwidth.
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