LCP
Largest Contentful Paint
5.6s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Remove Unused Code and Dependencies
How to optimize payfast.stg.greenn.com.br
Nuxt SiteScore: 71/100Analyzed February 2026
Remove Unused Code and Dependencies
Medium Impact+8 points estimated
Why It Matters
Unused JavaScript (238 KiB) and CSS (55 KiB) are bloating bundle size without providing value.
How to Fix
Enable Nuxt's tree-shaking by setting build.extractCSS to false and using ES modules. Remove unused vue-tel-input CSS (77% unused). Use webpack-bundle-analyzer to identify and eliminate unused Facebook Pixel code or move to client-side only rendering.
0Needs Improvement
What This Score Means
A score of 71 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
205ms
Needs Improvement
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 application has below-average performance with a score of 71/100. The biggest problem is an extremely slow Largest Contentful Paint of 5.6 seconds, which means users wait nearly 6 seconds to see the main content load - well beyond Google's recommended 2.5 seconds. The site is also wasting significant bandwidth by loading 238KB of unused JavaScript and 55KB of unused CSS, while images are poorly optimized and oversized for their display dimensions. Optimizing image delivery (which could save 650ms on LCP), removing unused code, and implementing proper caching could dramatically improve both the user experience and search rankings.
Other Optimization Recommendations
Optimize Image Delivery and Formats
High Impact+12 points estimatedWhy It Matters:
Images are causing 650ms LCP delay and wasting 110 KiB due to oversized dimensions and outdated formats.
How to Fix:
Implement Nuxt Image module with responsive sizing using srcset attributes. Convert images to WebP/AVIF formats and resize the logo from 1563x521 to actual display size (175x58). Use fetchpriority='high' only for LCP images and lazy loading for others.
Eliminate Render Blocking CSS
High Impact+10 points estimatedWhy It Matters:
CSS files are blocking first contentful paint by 550ms, delaying critical page rendering.
How to Fix:
Use Nuxt's CSS inlining for critical styles by configuring nitro.inlineDynamicImports. Move non-critical component CSS (Button, Card, Whatsapp) to async loading using dynamic imports. Consider extracting critical CSS for above-the-fold content.
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 Effective Caching Strategy
Missing cache headers are forcing repeat downloads of 600 KiB of resources that could be cached.
Remove Unused JavaScript Code
Unused JavaScript is adding 175 KiB of bloat and delaying LCP by 750ms while blocking the main thread.
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