LCP
Largest Contentful Paint
6.9s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize JavaScript Bundle Splitting
How to optimize descomplica.com.br
Optimize JavaScript Bundle Splitting
High Impact+18 points estimated
Why It Matters
Excessive JavaScript execution (1.8s) and unused code (336 KiB) severely impact TTI and TBT, blocking user interactions.
How to Fix
Configure Next.js bundle analyzer to identify unused code. Implement dynamic imports for non-critical components using next/dynamic. Split vendor chunks and defer third-party scripts like GTM and Facebook Pixel until after page load using Next.js Script component with strategy='afterInteractive'.
0Poor
What This Score Means
A score of 49 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
245ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.01
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 51/100, taking nearly 20 seconds to become fully interactive. The biggest problem is excessive JavaScript execution from third-party scripts (Google Analytics, Facebook Pixel, HubSpot), which blocks the main thread for 3.4 seconds and creates a 670ms delay for user interactions. The site could significantly improve by removing unused JavaScript (saving 336 KiB), optimizing images (saving 321 KiB), and implementing better caching strategies. Additionally, the 6.8-second Largest Contentful Paint indicates users wait too long to see meaningful content, primarily due to inefficient resource loading and network dependency chains.
Other Optimization Recommendations
Fix Preconnect and Cache Issues
High Impact+15 points estimatedWhy It Matters:
Poor caching (905 KiB savings) and unused preconnects delay LCP by 2.3 seconds and waste connection overhead.
How to Fix:
Remove unused preconnect to d3awytnmmfk53d.cloudfront.net and add preconnects for actual critical origins. Configure Next.js static assets with proper cache headers (31536000s for static chunks). Use CDN caching for framework bundles and implement service worker for repeat visits.
Optimize Image Delivery and Sizing
Medium Impact+8 points estimatedWhy It Matters:
Images lack proper dimensions causing layout shifts and 321 KiB of unnecessary bytes impact both LCP and CLS.
How to Fix:
Add explicit width/height attributes to all img elements, especially the logo and hero images. Use Next.js Image component with priority flag for LCP images. Increase compression on WebP images (39-55 KiB savings per image) and convert remaining PNG images to WebP format.
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
Fix Layout Shift Issues
Massive layout shifts (CLS: 0.903) are caused by content jumping during load, severely impacting user experience.
Remove Unused JavaScript Bundle
372 KiB of unused JavaScript is blocking rendering and delaying LCP by 900ms.
Optimize Server Response Time
Your server takes 2.3 seconds to respond, delaying both FCP and LCP by 2.2 seconds each.
Eliminate Layout Shifts from Images
Unsized images cause a massive 0.90 CLS score, creating jarring visual instability as content loads.