Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize descomplica.com.br
The main hero section causes 0.288 CLS score due to content shifting during load, representing 95% of total layout shift issues.
Add explicit width and height attributes to all images in the hero section. Use CSS aspect-ratio or min-height to reserve space for dynamic content. Implement Next.js Image component with priority={true} for above-the-fold images to prevent shifts.
A score of 41 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.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This Next.js site has severe performance issues with a poor score of 41/100. The biggest problem is excessive JavaScript blocking the main thread for over 3 seconds, causing the page to take nearly 20 seconds to become fully interactive. The site loads 399KB of unused JavaScript from Google Analytics and other third-party scripts, while also suffering from major layout shifts (0.302 CLS score) that make content jump around as it loads. Reducing JavaScript payloads, removing unused code, and fixing layout shifts by adding proper image dimensions could dramatically improve load times and user experience.
Why It Matters:
399 KiB of unused JavaScript and 3.3s of main thread blocking time severely impact Time to Interactive (19.9s) and user experience.
How to Fix:
Implement Next.js dynamic imports for non-critical components using next/dynamic. Remove duplicate Google Tag Manager instances (3 similar scripts loading). Use webpack-bundle-analyzer to identify and eliminate unused code from your Next.js bundles.
Why It Matters:
Font display issues cause 30ms delay to First Contentful Paint and contribute to layout shifts during text rendering.
How to Fix:
Add font-display: swap to your custom Aprova-Black font CSS declaration. Implement font metric overrides in your Next.js _document.js to match fallback fonts. Preload critical fonts using Next.js Head component with rel='preload'.
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.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Next.js Speed Tests
Font display issues cause 30ms delay to First Contentful Paint and contribute to layout shifts during text rendering.
399 KiB of unused JavaScript and 3.3s of main thread blocking time severely impact Time to Interactive (19.9s) and user experience.
Unsized images are causing 0.258 CLS score, making content jump and hurting user experience.
CSS files are blocking page rendering for 1.9 seconds, severely delaying LCP by preventing content from appearing.