LCP
Largest Contentful Paint
5.0s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce JavaScript Execution Time
How to optimize greenn.com.br
Nuxt SiteScore: 58/100Analyzed February 2026
Reduce JavaScript Execution Time
High Impact+15 points estimated
Why It Matters
1.5 seconds of JavaScript execution time is blocking user interactions and delaying TTI to 11.8 seconds.
How to Fix
Code-split your Nuxt application using dynamic imports for non-critical components. Move Google Analytics and TikTok tracking to load after page interactive using nuxt-gtag with defer option. Optimize the 362ms execution time in f1c1104.js by lazy-loading heavy components.
0Needs Improvement
What This Score Means
A score of 58 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
388ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.02
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Nuxt/Vue website has significant performance issues with a poor score of 58/100. The biggest problem is excessive JavaScript execution blocking the main thread for 2 seconds, causing a lengthy 11.8-second Time to Interactive and substantial input delay. The site is loading 317 KiB of unused JavaScript from Google Analytics and TikTok tracking scripts, while also serving 114 KiB of outdated JavaScript code (primarily from Facebook Pixel) that uses unnecessary polyfills for modern browsers. Removing unused JavaScript, updating to modern code without legacy transforms, and reducing main-thread work could improve the score by 30+ points and dramatically enhance user responsiveness.
Other Optimization Recommendations
Optimize Legacy JavaScript Polyfills
High Impact+12 points estimatedWhy It Matters:
114 KiB of unnecessary legacy JavaScript is slowing LCP by 150ms for modern browsers.
How to Fix:
Update your Nuxt build configuration to target modern browsers by setting build.transpile to exclude unnecessary polyfills. Use @nuxt/modern-mode or configure babel to skip transforms for ES6+ features. Review Facebook Pixel and other third-party scripts for modern alternatives.
Implement Efficient Resource Caching
Medium Impact+8 points estimatedWhy It Matters:
654 KiB of resources with poor cache policies are forcing unnecessary re-downloads on repeat visits.
How to Fix:
Configure your server or CDN to set longer cache headers for static assets (1 year for JS/CSS). Use Nuxt's built-in asset optimization with proper cache-control headers. Move Facebook Pixel config to be cached locally or use a more efficient implementation with better caching.
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 Proper Caching Strategy
Static assets have only 60-second cache lifetime, missing 2MB of potential cache savings and forcing unnecessary re-downloads.
Reduce Unused JavaScript Payloads
2.7MB of unused JavaScript is blocking rendering and adding 16 seconds to LCP, with moment.js locale files being 93% unused.
Remove Page Redirects Chain
Multiple redirects are adding 25.7 seconds to your page load time, severely impacting both LCP and FCP.
Implement Efficient Resource Caching
654 KiB of resources with poor cache policies are forcing unnecessary re-downloads on repeat visits.
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