LCP
Largest Contentful Paint
5.8s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix Critical Resource Load Delay
How to optimize preview.desenvolvimentomit.com.br
Fix Critical Resource Load Delay
High Impact+25 points estimated
Why It Matters
LCP element has a 9.2 second resource load delay causing extremely poor user experience.
How to Fix
Add priority='high' to the LCP image in Next.js Image component. Implement preload links for critical images in next/head. Optimize the image source URL to avoid unnecessary redirects and use Next.js Image optimization.
0Needs Improvement
What This Score Means
A score of 64 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
336ms
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/React site has poor performance with a score of 64/100, indicating significant user experience issues. The biggest problem is an extremely slow Largest Contentful Paint of 5.8 seconds, primarily caused by a massive 9+ second resource load delay that's preventing the main image from appearing quickly. The site is also loading 224 KB of unnecessary JavaScript code that isn't being used, which could be eliminated to save over 1 second of load time. Addressing the image loading delay and removing unused JavaScript could potentially improve the performance score by 25+ points and dramatically enhance user experience.
Other Optimization Recommendations
Reduce Unused JavaScript Bundle Size
High Impact+18 points estimatedWhy It Matters:
Unused JavaScript wastes 224 KiB and delays LCP by 1.05 seconds.
How to Fix:
Implement Next.js dynamic imports for components not needed on initial load. Use code splitting with React.lazy() for heavy components. Configure webpack-bundle-analyzer to identify and remove unused dependencies from chunks 7405 and 9720.
Eliminate Render Blocking CSS
Medium Impact+8 points estimatedWhy It Matters:
CSS file blocks initial render and delays First Contentful Paint by 250ms.
How to Fix:
Move critical CSS inline using Next.js styled-jsx or CSS-in-JS solutions. Split CSS using Next.js automatic code splitting. Defer non-critical CSS using next/dynamic with ssr: false for below-the-fold components.
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.