LCP
Largest Contentful Paint
4.5s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize LCP Image Resource Loading
How to optimize preview.desenvolvimentomit.com.br
Optimize LCP Image Resource Loading
High Impact+8 points estimated
Why It Matters
The hero image has 1.2 seconds of resource load delay, significantly impacting your 4.5s LCP score.
How to Fix
Add preload hints for the hero image using Next.js Head component: <link rel='preload' as='image' href='...' />. Optimize the image sizing strategy by using responsive breakpoints in your Next.js Image component. Consider using priority={true} prop on the hero image.
0Needs Improvement
What This Score Means
A score of 80 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
170ms
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 moderate performance with a score of 80/100, but has significant Core Web Vitals issues that hurt user experience. The biggest problem is unused JavaScript code totaling 259 KB, which is delaying your Largest Contentful Paint to 4.5 seconds - well above the recommended 2.5 second threshold. Your site is also suffering from render-blocking CSS files and poor caching strategies that force users to re-download resources on repeat visits. Removing unused JavaScript bundles and optimizing your Next.js code splitting could improve loading times by 750ms and dramatically boost your performance score.
Other Optimization Recommendations
Remove Unused JavaScript Bundles
High Impact+12 points estimatedWhy It Matters:
259 KiB of unused JavaScript is delaying LCP by 750ms and blocking user interactions.
How to Fix:
Use Next.js bundle analyzer to identify unused code in chunks 9673, 5738, and 9720. Implement dynamic imports for components that aren't immediately needed. Enable tree-shaking in your webpack config and split vendor bundles more granularly.
Eliminate Render-Blocking CSS Chain
Medium Impact+5 points estimatedWhy It Matters:
Critical CSS file is blocking First Contentful Paint by 300ms through network dependency chain.
How to Fix:
Extract above-the-fold CSS and inline it in your Next.js _document.js file. Use Next.js built-in CSS optimization or implement critical CSS extraction with tools like Critters. Load non-critical styles asynchronously using media='print' onload technique.
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.