LCP
Largest Contentful Paint
5.8s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix LCP Image Loading
How to optimize preview.desenvolvimentomit.com.br
Fix LCP Image Loading
High Impact+18 points estimated
Why It Matters
LCP element has 5.2 seconds of resource load delay, causing poor user experience.
How to Fix
Add priority={true} to your Next.js Image component for above-the-fold images. Implement preload hints for the LCP image using next/head. Optimize your image optimization settings in next.config.js and consider using a CDN with better performance than your current setup.
0Poor
What This Score Means
A score of 47 falls in the "Poor" 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
1230ms
Poor
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 47/100, indicating significant user experience issues. The biggest problem is excessive unused JavaScript code (224 KiB of waste) combined with heavy JavaScript execution times of 2.4 seconds, which is blocking the page from becoming interactive and causing a slow Largest Contentful Paint of 5.8 seconds. The site is also suffering from render-blocking CSS and multiple LinkedIn tracking requests that create unnecessary network delays. Removing unused JavaScript code, optimizing the main bundle size, and deferring non-critical scripts could potentially improve loading times by 900ms and dramatically enhance the user experience.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+25 points estimatedWhy It Matters:
224 KiB of unused JavaScript is blocking page load and delaying LCP by 900ms.
How to Fix:
Use Next.js dynamic imports to code-split large chunks like 7405-1ba6c8fc89ebb6ad.js (93% unused). Implement tree shaking by reviewing imports and removing unused dependencies. Configure webpack bundle analyzer to identify bloated modules and lazy load non-critical components.
Optimize JavaScript Execution Time
High Impact+20 points estimatedWhy It Matters:
2.4 seconds of JavaScript execution time creates 1,310ms Total Blocking Time, severely impacting responsiveness.
How to Fix:
Break down large chunks fe84f330 and 9720 using React.lazy() and Suspense for route-based code splitting. Move heavy computations to Web Workers or defer them using setTimeout/requestIdleCallback. Optimize React components by implementing useMemo and useCallback for expensive operations.
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.