4 sec in total
153 ms
3.6 sec
216 ms
Click here to check amazing Vandex content. Otherwise, check out these important facts you probably never knew about vandex.com.br
Visit vandex.com.brWe analyzed Vandex.com.br page load time and found that the first response time was 153 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
vandex.com.br performance score
153 ms
1323 ms
108 ms
87 ms
26 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 30% of them (23 requests) were addressed to the original Vandex.com.br, 14% (11 requests) were made to Pbs.twimg.com and 10% (8 requests) were made to Gp1.wac.edgecastcdn.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Vandex.com.br.
Page size can be reduced by 752.5 kB (31%)
2.4 MB
1.7 MB
In fact, the total size of Vandex.com.br 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. 65% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 25.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. 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 25.7 kB or 76% of the original size.
Potential reduce by 130.4 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. Vandex images are well optimized though.
Potential reduce by 407.6 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 407.6 kB or 69% of the original size.
Potential reduce by 188.7 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. Vandex.com.br needs all CSS files to be minified and compressed as it can save up to 188.7 kB or 86% of the original size.
Number of requests can be reduced by 35 (51%)
68
33
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vandex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
vandex.com.br
153 ms
index.php
1323 ms
style.css
108 ms
theme-cart66.css
87 ms
css
26 ms
cart66.css
87 ms
modernizr.js
88 ms
jquery.js
152 ms
theme.js
177 ms
view.js
64 ms
cart66-library.js
63 ms
widgets.js
130 ms
all.js
124 ms
bg-lines-alpha.png
128 ms
shadows.png
129 ms
Banner-Itunes-Ironia-ok3.jpg
1998 ms
Download_on_iTunes_Badge_PTBR_110x40_0824.png
1188 ms
slider-2.jpg
1577 ms
slider-1-ok3.jpg
1508 ms
icons-buttons.png
191 ms
Banner-Itunes-Ironia-ok3-120x66.jpg
1191 ms
slider-2-120x66.jpg
1196 ms
slider-1-ok3-120x66.jpg
1511 ms
media-icons-bg.png
1507 ms
icons-media.png
1509 ms
54896332
114 ms
image-carousel-nav.png
1387 ms
player.js
150 ms
player.css
118 ms
ga.js
71 ms
vuid.min.js
132 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
36 ms
timeline.5d8406ab2e764a871ed41bd9aa0b693f.js
156 ms
301 ms
xd_arbiter.php
105 ms
xd_arbiter.php
205 ms
artist_692775
677 ms
__utm.gif
43 ms
proxy.html
30 ms
syndication
108 ms
331234047122612224
273 ms
default-gray_60x60.png
21 ms
proxy.jpg
305 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
31 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
91 ms
56PzGMRV_normal.jpeg
164 ms
default_profile_5_normal.png
65 ms
kvKkDEXt_normal.jpeg
129 ms
Mv4fgDci_normal.jpg
58 ms
6rN2AFQj_normal.jpeg
158 ms
lsmt9oaogr36pk3hwt4e_normal.jpeg
128 ms
aLAfP3IZ_normal.jpeg
134 ms
54fOI2qj_normal.jpeg
115 ms
-3UDjVTs_normal.jpg
190 ms
Foto0328_normal.jpg
211 ms
CGwORHCWcAASn9p.jpg:small
246 ms
CFjG-gRVEAEY66m.jpg:small
213 ms
widgets.css
123 ms
html_widget_55.js
235 ms
widget_50_to_55.css
84 ms
css
61 ms
jot
31 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
47 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
50 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
56 ms
Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf
60 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
61 ms
__utm.gif
42 ms
widget_player.js
53 ms
__utm.gif
21 ms
angular.js
57 ms
bounce
12 ms
bounce
12 ms
logos-s7741599d19.png
204 ms
723x600xCareta-Vandex-Editada_FB_1269546979.jpg.pagespeed.b4.rn101.jpg
282 ms
723x600xCareta-Vandex-Editada_FB_1269546979.jpg.pagespeed.ic.rn101.jpg
283 ms
fontawesome-webfont.woff
177 ms
vandex.com.br SEO score
EN
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vandex.com.br can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Portuguese language. Our system also found out that Vandex.com.br 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.
vandex.com.br
Open Graph description is not detected on the main page of Vandex. 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: