LCP
Largest Contentful Paint
8.6s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize LCP Image Discovery
How to optimize payfast.greenn.com.br
Optimize LCP Image Discovery
Medium Impact+12 points estimated
Why It Matters
Your LCP image loads 313ms slower because it's not discoverable from initial HTML.
How to Fix
Add preconnect for s3.greenn.com.br in nuxt.config.js app.head.link array. Apply fetchpriority='high' to the product image in your Vue component. Use Nuxt's NuxtImg component with priority attribute to optimize the hero product image delivery.
0Needs Improvement
What This Score Means
A score of 54 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.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 54/100, indicating significant user experience issues. The biggest problem is extremely slow interactivity - it takes nearly 12 seconds for the page to become fully interactive, while the largest content doesn't appear until 8.6 seconds. The site is bloated with unused code, wasting 60KB of CSS (77% unused) and 348KB of JavaScript, plus images are oversized for their display dimensions. Quick wins include removing unused CSS and JavaScript, properly sizing images, and implementing better caching strategies, which could collectively improve load times by several seconds and boost the performance score substantially.
Other Optimization Recommendations
Optimize CSS Bundle and Delivery
High Impact+18 points estimatedWhy It Matters:
77% of your largest CSS file (60KB) is unused, blocking render and delaying FCP by 300ms.
How to Fix:
Configure Nuxt's CSS optimization in nuxt.config.js with 'experimental: { inlineSSRStyles: false }' to enable tree-shaking. Use PurgeCSS with @nuxtjs/tailwindcss to remove unused styles. Split component-specific CSS into separate chunks using dynamic imports for Card.vue component.
Remove Unused JavaScript Code
High Impact+16 points estimatedWhy It Matters:
348KB of unused JavaScript delays LCP by 1.35 seconds and blocks user interactions.
How to Fix:
Enable Nuxt's tree-shaking with 'build: { analyze: true }' to identify unused code. Move Facebook Pixel to useHead() composable with defer attribute. Split large chunks by implementing dynamic imports for heavy components like CSeQ0MZH.js using defineAsyncComponent().
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.