LCP
Largest Contentful Paint
7.7s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Image Delivery Pipeline
How to optimize payfast.greenn.com.br
Optimize Image Delivery Pipeline
High Impact+20 points estimated
Why It Matters
Poor image optimization is causing 152 KiB waste and 900ms LCP delay for critical product images.
How to Fix
Implement responsive images using Nuxt Image module with multiple sizes for the product image (currently 700x700 displayed as 158x158). Enable automatic WebP/AVIF conversion and compression. Add proper srcset attributes to serve appropriately sized images based on device.
0Needs Improvement
What This Score Means
A score of 67 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
146ms
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 67/100, primarily due to an extremely slow Largest Contentful Paint of 7.7 seconds. The biggest culprit is excessive unused JavaScript (211 KiB worth) that's blocking the page from loading quickly, combined with unoptimized images that could be compressed and resized to save 152 KiB. The site is also suffering from inefficient caching and render-blocking CSS files that delay the initial paint by 3.6 seconds. Removing unused JavaScript, optimizing images, and implementing proper caching could potentially improve the performance score by 25+ points and dramatically enhance user experience.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+25 points estimatedWhy It Matters:
Eliminating 211 KiB of unused JavaScript can improve LCP by 900ms and reduce blocking time significantly.
How to Fix:
Use Nuxt's tree-shaking by enabling 'build.analyze' to identify unused code. Split the large CHSsAhP0.js bundle using dynamic imports for non-critical components. Consider lazy-loading Facebook Pixel or moving it to a web worker to reduce main thread blocking.
Fix Critical Resource Caching
Medium Impact+12 points estimatedWhy It Matters:
Missing cache headers force users to re-download 222 KiB on every visit, slowing repeat page loads.
How to Fix:
Configure your CDN/server to set long-term cache headers (1 year) for static assets like images and JavaScript bundles. Set shorter cache (20 minutes) for Facebook scripts. Use Nuxt's built-in asset fingerprinting to enable safe long-term caching.
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
Implement Responsive Image Optimization
The hero image is oversized by 41KB and has insufficient caching, contributing to poor LCP performance.
Optimize Unused JavaScript Bundle
358KB of unused JavaScript is adding 2.4 seconds to LCP and blocking main thread execution.
Eliminate Render-Blocking CSS
Critical CSS files are blocking initial render for 1.2 seconds, severely delaying both FCP and LCP.
Fix Forced Reflow Issues
Forced reflows cause 91ms of layout thrashing, degrading user experience and potentially affecting CLS scores.