26.7 sec in total
1.1 sec
24.4 sec
1.2 sec
Click here to check amazing Vivo content for Malaysia. Otherwise, check out these important facts you probably never knew about vivo.my
vivo,smartphones, malaysia
Visit vivo.myWe analyzed Vivo.my page load time and found that the first response time was 1.1 sec and then it took 25.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
vivo.my performance score
1123 ms
50 ms
881 ms
1178 ms
580 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 39% of them (37 requests) were addressed to the original Vivo.my, 23% (22 requests) were made to Static.xx.fbcdn.net and 16% (15 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Vivoglobal.com.
Page size can be reduced by 424.6 kB (18%)
2.4 MB
1.9 MB
In fact, the total size of Vivo.my main page is 2.4 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. 60% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 17.7 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 8.4 kB, which is 39% 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 17.7 kB or 83% of the original size.
Potential reduce by 58.5 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.
Potential reduce by 187.2 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 187.2 kB or 69% of the original size.
Potential reduce by 161.1 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.my needs all CSS files to be minified and compressed as it can save up to 161.1 kB or 87% of the original size.
Number of requests can be reduced by 35 (38%)
92
57
The browser has sent 92 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 26 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
vivo.my
1123 ms
analytics.js
50 ms
global-base.css
881 ms
service.css
1178 ms
products-base.css
580 ms
jquery.js
1490 ms
sprite.js
588 ms
vivo-common.js
908 ms
vivo-main.js
1206 ms
swfobject.js
905 ms
jquery.cookie.js
1200 ms
mousewheel.js
1232 ms
touchSwipe.min.js
1230 ms
xshot.js
1474 ms
home.css
1522 ms
highlight.css
2046 ms
jquery.fancybox.css
1526 ms
jquery.fancybox.pack.js
1844 ms
products.css
3294 ms
vivo-high.js
1777 ms
collect
24 ms
h-x5pro-shadow.png
2606 ms
h-x5pro-t1.png
3931 ms
h-x5pro-t2.png
2601 ms
h-y37-circle11.png
4546 ms
h-y37-circle12.png
5130 ms
h-y37-circle13.png
6556 ms
h-y37-circle14.png
5155 ms
h-y37-circle21.png
6351 ms
h-y37-circle22.png
5630 ms
h-y37-circle23.png
8448 ms
h-y37-circle24.png
9553 ms
h-y37-title1.png
5615 ms
h-y37-title2.png
6089 ms
h-y37-figure.png
20213 ms
h-x5pro-wave.png
4436 ms
X5Pro-%20vivo%20Grand%20Launch%20Malaysia%202015.gif
8764 ms
vivo-logo.png
385 ms
h-x5pro-figure.png
2593 ms
h-y22l-mobile.png
2620 ms
h-y22l-title1.png
600 ms
h-y22l-title2.png
363 ms
vivo-website-Y35-368x240px-01.png
1159 ms
x5-pro-video.jpg
1464 ms
vivo-website-Y51-368x240px-01.png
2306 ms
store2.jpg
2305 ms
store1.jpg
2547 ms
h-y22l-bg.jpg
6206 ms
key-event-video-ico.png
2242 ms
event-split-bg.png
2481 ms
event-weibo-ico.png
2507 ms
vivo-sns-ico.png
2519 ms
vivo-footer-logo.jpg
2529 ms
vivo-lan-en-ico.jpg
2708 ms
h-x5pro-bg.jpg
6422 ms
collect
249 ms
likebox.php
501 ms
3nB4xc2_6jL.css
409 ms
DHQqLLtVOYz.css
486 ms
emc7iBXdI_a.css
622 ms
rIiqPPB00f-.css
667 ms
SRSW8M763HA.js
802 ms
ullQFyhrQFI.js
1040 ms
y97Ig99UVTs.js
714 ms
KHAtULXOQuz.js
721 ms
XlY_wsDnClE.js
799 ms
rR4Qw0p7TFQ.js
1246 ms
ULtnh-HfQSw.js
752 ms
d_-F4IIjJo3.js
797 ms
FOagnU9QnXq.js
1244 ms
Cw6QosZRsiU.js
1245 ms
i8XO-4kv8i7.js
1239 ms
z5eMxBRE-Ji.js
1241 ms
7YklgZdHLYS.js
1239 ms
12923152_557602574400606_2150814147272518979_n.jpg
504 ms
10393752_372642102896655_678910614788553820_n.png
570 ms
11666259_415965988610728_7532583492756531327_n.jpg
666 ms
10354686_10150004552801856_220367501106153455_n.jpg
763 ms
11694914_839013339561706_4436468969101580212_n.jpg
803 ms
12800170_135253410199829_5474695245983295970_n.jpg
768 ms
11892073_1643418092597121_5175836605558166234_n.jpg
767 ms
12688177_194768554219246_3758192174461247259_n.jpg
760 ms
12933020_1709598025996589_7396517631913338180_n.jpg
803 ms
10322653_470633586465216_5175226645401809776_n.jpg
947 ms
12795494_1691121631163545_8490725490848925634_n.jpg
877 ms
10533456_199825447040507_2862082488806795612_n.jpg
1437 ms
12512346_1006424456071640_8616536468121339034_n.jpg
898 ms
12924377_124748131258118_4098649634405137261_n.jpg
956 ms
12933069_1589458184705692_2991561707625270381_n.jpg
1124 ms
hdYxvZtlnwH.png
252 ms
wL6VQj7Ab77.png
264 ms
1JLnMyDN79z.png
249 ms
FASTu8Ostla.png
110 ms
VXcANLwwL5J.js
87 ms
vivo.my SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vivo.my 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 Vivo.my 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.
vivo.my
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: