57.9 sec in total
2.4 sec
55 sec
507 ms
Click here to check amazing Vivoglobal content for India. Otherwise, check out these important facts you probably never knew about vivoglobal.com
vivo
Visit vivoglobal.comWe analyzed Vivoglobal.com page load time and found that the first response time was 2.4 sec and then it took 55.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 13 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
vivoglobal.com performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value6.3 s
11/100
25%
Value4.8 s
67/100
10%
Value220 ms
88/100
30%
Value0.035
100/100
15%
Value5.8 s
67/100
10%
2380 ms
3403 ms
1202 ms
988 ms
3074 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 31% of them (33 requests) were addressed to the original Vivoglobal.com, 27% (28 requests) were made to Static.xx.fbcdn.net and 10% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (20.2 sec) belongs to the original domain Vivoglobal.com.
Page size can be reduced by 601.6 kB (29%)
2.1 MB
1.5 MB
In fact, the total size of Vivoglobal.com main page is 2.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 23.1 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. This page needs HTML code to be minified as it can gain 6.1 kB, which is 21% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 23.1 kB or 79% of the original size.
Potential reduce by 80.1 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. Vivoglobal images are well optimized though.
Potential reduce by 230.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 230.9 kB or 66% of the original size.
Potential reduce by 267.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. Vivoglobal.com needs all CSS files to be minified and compressed as it can save up to 267.5 kB or 86% of the original size.
Number of requests can be reduced by 39 (44%)
89
50
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vivoglobal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
vivoglobal.com
2380 ms
www.vivoglobal.com
3403 ms
base.css
1202 ms
vivo.layout.css
988 ms
vivo.media.css
3074 ms
envivo-layout-old.css
1198 ms
jquery.js
2942 ms
touchSwipe.min.js
2529 ms
vivo.main.js
1791 ms
vivo.high.layout.css
2158 ms
vivo.high.animate.css
9308 ms
bacba5e0180cd20d040ba938921d3328_854x480!.jpg
2215 ms
11084641_400380443466675_472576077_a.jpg
292 ms
vm-h-v3-shadow.png
4813 ms
vm-h-v3-figure.png
20151 ms
vm-h-v3-title.png
3491 ms
vm-h-x5pro-shadow.png
6415 ms
vm-h-x5pro-figure.png
20150 ms
vm-h-x5pro-title.png
7365 ms
vm-h-y37-figure.png
20148 ms
vm-h-y37-title.png
20147 ms
vm-h-y35-figure.png
20148 ms
vm-h-y35-title.png
9975 ms
vm-h-x5-figure.png
20146 ms
vm-h-x5-title.png
20147 ms
881c804734877384d17de96b309fbfbd_854x480!.jpg
3343 ms
7f75fc776426b066f00a399408b60fdc_854x480!.jpg
2103 ms
d883e8af79b2450385be03e48721ce0e_340x200!.jpg
1593 ms
dc0e6d45b2d00a8c01e4d5c323b25ff0_340x200!.jpg
1613 ms
26db33a4e170c38919913e2bd432ebc2_340x200!.jpg
2354 ms
9cd67784224e1f544c14b1b56fb87edb_340x200!.jpg
3215 ms
sdk.js
1435 ms
339 ms
vivo-gb-logo.png
16206 ms
vivo-gb-ico.png
15733 ms
vm-h-v3-bg.jpg
19749 ms
vm-h-x5pro-bg.jpg
19748 ms
vm-h-y37-bg.jpg
19748 ms
vm-h-y35-bg.jpg
18741 ms
vm-h-x5-bg.jpg
19748 ms
vivo-f-logo.jpg
16664 ms
myriadpro-light.woff
19747 ms
combined.css
62 ms
smoothDivScroll.css
119 ms
stack_161235.js
188 ms
jquery.min.js
120 ms
analytics.js
80 ms
stackpile.api-2ece4e50df.js
79 ms
12552373_1093891663978657_1333587269_n.jpg
530 ms
small_share_sprite.png
76 ms
11084641_400380443466675_472576077_a.jpg
270 ms
12407285_939127616123490_1401041868_n.jpg
889 ms
12519320_605307189617248_1259949924_n.jpg
414 ms
12424696_420355174824528_1461812723_n.jpg
416 ms
12479531_796777643779039_894023532_n.jpg
732 ms
collect
57 ms
collect
262 ms
nr-918.min.js
269 ms
424 ms
xd_arbiter.php
1403 ms
xd_arbiter.php
1831 ms
a53393d12f
164 ms
myriadpro-light.ttf
19943 ms
page.php
162 ms
3nB4xc2_6jL.css
447 ms
DHQqLLtVOYz.css
542 ms
r31N1ZFlqa-.css
616 ms
emc7iBXdI_a.css
772 ms
SRSW8M763HA.js
841 ms
ullQFyhrQFI.js
889 ms
y97Ig99UVTs.js
687 ms
rR4Qw0p7TFQ.js
930 ms
ULtnh-HfQSw.js
691 ms
6IFzBT9uHU-.js
919 ms
Gqzx6edLp88.js
798 ms
HQR5HcLW5FK.js
885 ms
dt0QadAXRnm.js
922 ms
KHAtULXOQuz.js
921 ms
12920395_1775461369348429_7373010926938850561_n.jpg
370 ms
10404422_1576921855869049_5933495158239961297_n.jpg
479 ms
hdYxvZtlnwH.png
137 ms
wL6VQj7Ab77.png
140 ms
1JLnMyDN79z.png
139 ms
235 ms
274 ms
t-wz8gw1xG1.png
77 ms
css;base64,
9 ms
LJCv51DxJBw.css
119 ms
YF_27oR5jov.css
249 ms
W4NL_XloU4d.js
120 ms
eACiSk3I2K6.js
118 ms
FOagnU9QnXq.js
272 ms
VXcANLwwL5J.js
77 ms
i8XO-4kv8i7.js
84 ms
12985432_1776600819234484_2984134396085499999_n.jpg
158 ms
12919686_1776202485940984_1823216392964010762_n.jpg
226 ms
1916253_1773755186185714_8982484746674169666_n.jpg
325 ms
12919721_1775522382675661_7315057249527594181_n.jpg
328 ms
12919918_1775522262675673_2351547719186334711_n.jpg
248 ms
12963558_1775522222675677_121479224285486488_n.jpg
246 ms
12920240_1775522499342316_1510296565931256585_n.jpg
245 ms
12920395_1775461369348429_7373010926938850561_n.jpg
315 ms
6zltWv6aFID.png
92 ms
Cg43IrsPc7P.png
90 ms
gm-8CYVMZ_l.png
89 ms
vivoglobal.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
vivoglobal.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
vivoglobal.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vivoglobal.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Vivoglobal.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.
vivoglobal.com
Open Graph description is not detected on the main page of Vivoglobal. 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: