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
Critical resource chains create a 612ms delay as resources wait for dependencies to load sequentially.
Preload the cf.errors.css file using '<link rel="preload" href="https://vivo.com.br/cdn-cgi/styles/cf.errors.css" as="style">' in the HTML head. Consider bundling critical CSS directly into the main HTML document. Review if the Cloudflare error CSS is necessary for the primary user experience.
A score of 99 falls in the "Good" 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 website has excellent performance with a score of 99/100, indicating a very fast and well-optimized site. The main issue is a render-blocking CSS file (cf.errors.css) that's preventing the page from displaying immediately, though it's only causing a minor 163ms delay. The site could benefit from extending cache lifetimes for static resources, which would save about 10KB on repeat visits and make the page even faster for returning users. Overall, this is a high-performing site with only minor optimization opportunities remaining.
Why It Matters:
The cf.errors.css file is blocking initial page render and delaying content visibility by 163ms.
How to Fix:
Inline the critical CSS from cf.errors.css directly in the HTML head section since it's only 4.9KB. Alternatively, add 'media="print" onload="this.media='all'"' to the stylesheet link to make it non-blocking. Remove or defer this Cloudflare error stylesheet if it's not essential for the main page content.
Why It Matters:
Short cache durations force repeat downloads of 10KB worth of static resources, slowing return visits.
How to Fix:
Configure Cloudflare or server caching to extend cache headers for static assets to at least 1 year (31536000 seconds). Set cf.errors.css and cf-no-screenshot-error.png cache lifetime from 2 hours to 1 year since these rarely change. Update beacon.min.js cache from 1 day to longer duration through Cloudflare settings.
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.