Tools & Wizards About Us
vivo.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

vivo.com

vivo Official Site

Page Load Speed

6.1 sec in total

First Response

569 ms

Resources Loaded

5.3 sec

Page Rendered

302 ms

vivo.com screenshot

About Website

Visit vivo.com now to see the best up-to-date Vivo content for China and also check out these interesting facts you probably never knew about vivo.com

Explore a wide range of vivo products including smartphones, earphones, accessories. Click now to find out about vivo X, V, Y, T Series phones and more about vivo！

Visit vivo.com

Key Findings

We analyzed Vivo.com page load time and found that the first response time was 569 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

vivo.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value1,810 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

vivo.com

569 ms

vivo.com

968 ms

en

2450 ms

vcm.js

917 ms

optimize.js

38 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 11% of them (4 requests) were addressed to the original Vivo.com, 36% (13 requests) were made to Asia-exstatic.vivoglobal.com and 17% (6 requests) were made to Asia-exstatic-vivofs.vivo.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Vivo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 109.8 kB (32%)

Content Size

338.6 kB

After Optimization

228.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vivo.com main page is 338.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 136.9 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 77.8 kB

  • Original 99.2 kB
  • After minification 99.2 kB
  • After compression 21.4 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 77.8 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 61 B

  • Original 136.9 kB
  • After minification 136.9 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Vivo images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.9 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 32.0 kB or 60% of the original size.

CSS Optimization

-0%

Potential reduce by 51 B

  • Original 49.6 kB
  • After minification 49.6 kB
  • After compression 49.5 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Vivo.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 19 (66%)

Requests Now

29

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vivo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

vivo.com

vivo.com

569 ms

vivo.com

vivo.com

968 ms

en

en

2450 ms

vcm.js

vcm.js

917 ms

optimize.js

optimize.js

38 ms

vicon_175da95.css

vicon_175da95.css

213 ms

vivo_1fbb853.css

vivo_1fbb853.css

214 ms

video-js.min_37aa469.css

video-js.min_37aa469.css

215 ms

vivo_385d841.css

vivo_385d841.css

215 ms

jquery.min.3.3.1_7679e5a.js

jquery.min.3.3.1_7679e5a.js

216 ms

global_a024cc7.js

global_a024cc7.js

216 ms

f89703d01cdca05da0224500e6a93f92.woff

f89703d01cdca05da0224500e6a93f92.woff

274 ms

d295e9f197e005385fa15e12fb43ab69.woff

d295e9f197e005385fa15e12fb43ab69.woff

274 ms

AvenirNextRegular_2d26b87.woff

AvenirNextRegular_2d26b87.woff

3 ms

vivo-icons_6dc2f08.woff

vivo-icons_6dc2f08.woff

5 ms

67f73d40f5fc305e60859adb91a0ff4b.jpg

67f73d40f5fc305e60859adb91a0ff4b.jpg

230 ms

e46f65acec125759fb05686eb80e5fe2.svg

e46f65acec125759fb05686eb80e5fe2.svg

223 ms

bd03ce1ba63649eaf6ecdad3058c343d.svg

bd03ce1ba63649eaf6ecdad3058c343d.svg

225 ms

ef210fc6b03ff4397cdf7082295bca10.svg

ef210fc6b03ff4397cdf7082295bca10.svg

219 ms

index.pack_9b12171.js

index.pack_9b12171.js

8 ms

public_17cd1b1.js

public_17cd1b1.js

6 ms

web-vitals.iife_51bd166.js

web-vitals.iife_51bd166.js

7 ms

video-js.min_e5cdd6f.js

video-js.min_e5cdd6f.js

33 ms

index.pack_8265b8e.js

index.pack_8265b8e.js

31 ms

text

text

724 ms

gtm.js

gtm.js

97 ms

analytics.js

analytics.js

108 ms

gtm.js

gtm.js

75 ms

fbevents.js

fbevents.js

168 ms

gtm.js

gtm.js

104 ms

gtm.js

gtm.js

104 ms

aa24ae7b58f88.js

aa24ae7b58f88.js

167 ms

js

js

128 ms

collect

collect

209 ms

collect

collect

45 ms

ga-audiences

ga-audiences

30 ms

Accessibility Review

vivo.com accessibility score

60

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Form elements do not have associated labels

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a valid value for its [lang] attribute.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

vivo.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

vivo.com SEO score

84

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vivo.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Vivo.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

vivo.com

Open Graph description is not detected on the main page of Vivo. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: