Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize vivo.com.br
Large PNG images consume 6.2MB and delay LCP, with product images being 3x larger than necessary.
Convert product images to WebP format for 40% size reduction. Implement responsive images with srcset to serve appropriate sizes (385x385 instead of 1200x1200). Add explicit width/height attributes to prevent layout shifts.
A score of 21 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 site has critical performance issues with an extremely poor score of 21/100. The biggest problem is massive unused CSS (316 KiB) and JavaScript (786 KiB) that's blocking the initial page render, causing a devastating 9.9-second load time for the main content. The site is also loading enormous unoptimized images (over 6 MB worth) that could be reduced by using modern formats like WebP and proper sizing. Cleaning up the unused code, optimizing images, and implementing proper caching could dramatically improve this score by 50+ points and provide users with a usable experience instead of the current 35+ second wait times.
Why It Matters:
Unused code blocks rendering for 2.1 seconds and wastes 1.1MB of bandwidth, severely delaying LCP.
How to Fix:
Remove 97% unused CSS from clientlib-base.css (311KB savings). Code-split JavaScript bundles to load only required functionality. Implement tree-shaking to eliminate dead code from third-party libraries like Facebook Pixel and TikTok tracking.
Why It Matters:
Critical CSS and JavaScript block initial page render for 2.7 seconds, preventing users from seeing content.
How to Fix:
Inline critical CSS for above-the-fold content. Move non-essential JavaScript like analytics and tracking scripts to load asynchronously. Defer elastic-apm-rum.js and other monitoring tools until after page interactive.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
Google Tag Manager scripts contain 139KB of unused code, slowing LCP by 600ms and wasting processing time.
17MB of video content has zero cache lifetime, forcing full re-downloads on every visit and wasting 69MB of bandwidth.
JavaScript files are blocking initial page render, delaying FCP by 750ms and preventing users from seeing content.
136KB of unused JavaScript and 63KB of unused CSS waste bandwidth and slow down page parsing.
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.