LCP
Largest Contentful Paint
2.1s
Good
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Update JavaScript Build Target
How to optimize mestregeo.com.br
Update JavaScript Build Target
Medium Impact+0.5 points estimated
Why It Matters
Legacy polyfills waste 11KB and slow LCP by 150ms for modern browsers.
How to Fix
Update Next.js browserslist in package.json to target modern browsers (>95% support). Configure SWC compiler to exclude ES2020+ polyfills by setting target: 'es2020' in next.config.js. Remove unnecessary polyfills from @babel/preset-env configuration.
0Good
What This Score Means
A score of 98 falls in the "Good" 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
87ms
Good
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 Next.js site has excellent performance with a score of 98/100, but there are still some quick wins available. The biggest issue is that 91% of your CSS file (22 KiB) is unused code that's blocking the initial page render, potentially delaying how quickly users see content by about 280ms. Additionally, your JavaScript includes unnecessary polyfills for modern browser features, wasting 11 KiB, and Google Analytics scripts contain significant unused code. Removing unused CSS, updating your build process to avoid legacy JavaScript polyfills, and deferring non-critical scripts could push your already-high score even closer to perfect while improving your Core Web Vitals.
Other Optimization Recommendations
Remove Unused CSS Rules
High Impact+1 point estimatedWhy It Matters:
91% of CSS is unused, blocking render and delaying LCP by 300ms.
How to Fix:
Configure Next.js CSS tree-shaking by enabling experimental.optimizeCss in next.config.js. Split CSS into page-specific modules using CSS Modules or styled-components. Use PurgeCSS plugin to remove unused Tailwind/Bootstrap classes automatically.
Defer Render-Blocking CSS
High Impact+1 point estimatedWhy It Matters:
The main CSS file blocks initial render, delaying both LCP and FCP by 100ms.
How to Fix:
Move critical above-the-fold CSS inline using Next.js styled-jsx or extract to <style> tags. Load non-critical CSS asynchronously using next/dynamic with ssr: false option. Implement CSS code-splitting by route using Next.js automatic CSS chunking.
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 Next.js Speed Tests
Next.js Performance Resources
Defer Render-Blocking CSS
The main CSS file blocks initial render, delaying both LCP and FCP by 100ms.
Remove Unused CSS Rules
91% of CSS is unused, blocking render and delaying LCP by 300ms.
Fix Element Render Delay Issue
The LCP element has a massive 2.5-second render delay, indicating JavaScript is blocking rendering of critical content.
Reduce Unused JavaScript Bundle Size
24KB of unused JavaScript is wasting network resources and delaying LCP by 150ms.