LCP
Largest Contentful Paint
11.4s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize LCP Image Delivery
How to optimize payfast.greenn.com.br
Optimize LCP Image Delivery
High Impact+25 points estimated
Why It Matters
The product image is causing an 11.4s LCP delay and wasting 606KB due to poor optimization and discovery.
How to Fix
Convert the product image to WebP format and resize from 800x450 to 158x89 for the displayed size. Add fetchpriority='high' to the LCP image element. Use Nuxt's <NuxtImg> component with format='webp' and sizes prop for automatic optimization.
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
124ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.03
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, indicating significant room for improvement. The biggest problem is an extremely slow Largest Contentful Paint of 11.4 seconds, primarily caused by an oversized product image (608KB) that could be reduced by over 600KB through proper compression and responsive sizing. The site is also loading 248KB of unused JavaScript and 60KB of unused CSS, which could save 1.2 seconds in load time if removed. Addressing the image optimization alone could improve LCP by 2.4 seconds, while cleaning up the unused code and implementing proper caching would provide substantial additional performance gains.
Other Optimization Recommendations
Eliminate Unused JavaScript Code
High Impact+18 points estimatedWhy It Matters:
248KB of unused JavaScript is blocking rendering and adding 1.2 seconds to LCP.
How to Fix:
Use Nuxt's tree-shaking by importing only needed functions instead of entire libraries. Enable code splitting with dynamic imports for route-specific components. Configure Nuxt's vite.build.rollupOptions to exclude unused dependencies from the main bundle.
Fix Render Blocking Resources
Medium Impact+12 points estimatedWhy It Matters:
Multiple CSS files are blocking first paint and delaying FCP by 950ms.
How to Fix:
Inline critical CSS for above-the-fold content using Nuxt's css configuration. Use async loading for non-critical CSS files like ContinuousDates and Textarea components. Implement Nuxt's experimental.inlineSSRStyles to reduce render-blocking requests.
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.