LCP
Largest Contentful Paint
5.9s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix LCP Image Loading Strategy
How to optimize preview.desenvolvimentomit.com.br
Fix LCP Image Loading Strategy
High Impact+25 points estimated
Why It Matters
The LCP image has lazy loading enabled and takes 5.9 seconds to load, severely impacting user experience.
How to Fix
Remove loading='lazy' from the hero image and add fetchpriority='high'. In Next.js, use priority={true} prop on the Image component. Ensure the LCP image is discoverable in the initial HTML by avoiding conditional rendering that requires JavaScript.
0Needs Improvement
What This Score Means
A score of 68 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
315ms
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 Next.js site has poor performance with a score of 68/100, indicating significant user experience issues. The biggest problem is an extremely slow Largest Contentful Paint of 5.9 seconds, primarily caused by a lazy-loaded hero image that isn't discoverable in the initial HTML and lacks proper priority hints. The site is also loading 223 KiB of unused JavaScript across multiple chunks, which could save over 1 second of load time if removed or deferred. To improve performance, remove lazy loading from the main hero image, add fetchpriority="high" to it, eliminate unused JavaScript, and consider inlining or deferring the render-blocking CSS that's adding 270ms of delay.
Other Optimization Recommendations
Eliminate Unused JavaScript Bundles
High Impact+15 points estimatedWhy It Matters:
223 KiB of unused JavaScript is delaying LCP by 1.05 seconds and blocking user interactions.
How to Fix:
Implement dynamic imports for the large chunks (5063, 9720, 5044) that show 47-93% waste. Use Next.js code splitting with dynamic() for non-critical components. Enable tree shaking by ensuring imports are specific rather than importing entire libraries.
Optimize Render-Blocking CSS
Medium Impact+8 points estimatedWhy It Matters:
A 34KB CSS file is blocking initial render and delaying First Contentful Paint by 270ms.
How to Fix:
Inline critical CSS for above-the-fold content directly in the HTML head. Use Next.js built-in CSS optimization by splitting CSS into page-specific bundles. Consider using CSS-in-JS solutions or CSS modules to automatically eliminate unused styles.
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
Optimize JavaScript Execution Time
2.2 seconds of JavaScript execution time is creating 580ms of Total Blocking Time, hurting user interactivity.
Reduce Unused JavaScript Payload
285KB of unused JavaScript is blocking the main thread and delaying LCP by 1.05 seconds.
Remove Legacy JavaScript Polyfills
Unnecessary polyfills add 40KB of code that modern browsers don't need, slowing down execution.
Optimize JavaScript Bundle Splitting
2.9 seconds of JavaScript execution time blocks the main thread and delays Time to Interactive by 11.2 seconds.