10.4 sec in total
946 ms
8.6 sec
827 ms
Visit vocokan.xpg.uol.com.br now to see the best up-to-date Vocokan XPG Uol content for Brazil and also check out these interesting facts you probably never knew about vocokan.xpg.uol.com.br
Visit vocokan.xpg.uol.com.brWe analyzed Vocokan.xpg.uol.com.br page load time and found that the first response time was 946 ms and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
vocokan.xpg.uol.com.br performance score
946 ms
2255 ms
403 ms
270 ms
30 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Vocokan.xpg.uol.com.br, 10% (10 requests) were made to Tpc.googlesyndication.com and 7% (7 requests) were made to Adclient.siga.uol.com.br. The less responsive or slowest element that took the longest time to load (3.9 sec) relates to the external source Www3.xpg.uol.com.br.
Page size can be reduced by 957.0 kB (33%)
2.9 MB
2.0 MB
In fact, the total size of Vocokan.xpg.uol.com.br main page is 2.9 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. 70% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 346.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 346.4 kB or 74% of the original size.
Potential reduce by 5.8 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. Vocokan XPG Uol images are well optimized though.
Potential reduce by 576.3 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 576.3 kB or 63% of the original size.
Potential reduce by 28.4 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. Vocokan.xpg.uol.com.br needs all CSS files to be minified and compressed as it can save up to 28.4 kB or 81% of the original size.
Number of requests can be reduced by 58 (63%)
92
34
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vocokan XPG Uol. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
luxo.html
946 ms
style.css
2255 ms
resp-style.css
403 ms
validation.css
270 ms
css
30 ms
jquery.min.js
37 ms
recaptcha_ajax.js
7 ms
api.js
20 ms
jquery.form.js
546 ms
jquery.validation.js
820 ms
jquery.validation.messages.js
406 ms
functions.js
534 ms
default.js
537 ms
tag.js
541 ms
recaptcha__pt_br.js
159 ms
rta.js
119 ms
gpt.js
117 ms
analytics.js
115 ms
uoltm.js
449 ms
xpg.js
471 ms
tac3a7a-negra.jpg
224 ms
115 ms
b.gif
190 ms
28-1920.jpg
3856 ms
arrow-form.png
191 ms
loading.gif
187 ms
arrow-btn-top-hover.png
185 ms
chc3a1-verde.jpg
220 ms
jura-savagnin.jpg
218 ms
acessc3b3rios.jpg
221 ms
banner-300x250.html
351 ms
SL0aFUFfkFMMdariYQ3_YYbN6UDyHWBl620a-IRfuBk.woff
159 ms
sprite.png
281 ms
201 ms
collect
86 ms
pubads_impl_82.js
87 ms
ads
205 ms
container.html
27 ms
astral.html
459 ms
xpg.js
313 ms
xpg.js
564 ms
mercurio.html
570 ms
parceiro-async.js
284 ms
expansion_embed.js
44 ms
ads
194 ms
css
114 ms
m_js_controller.js
96 ms
favicon
97 ms
abg.js
101 ms
googlelogo_color_112x36dp.png
53 ms
osd.js
50 ms
nessie_icon_thin_arrow_big_white.png
80 ms
x_button_blue2.png
44 ms
s
80 ms
5-AYViExptypIdFoLKAxTA.woff
78 ms
commons.js
284 ms
uol-dna.js
297 ms
xpg.js
454 ms
7663644962834948395
48 ms
ads
310 ms
logo-uol-52x52.png
740 ms
20anos.svg
1143 ms
uol-text-regular.woff
865 ms
uol-text-light.woff
1529 ms
uol-icones-setas.woff
1528 ms
r2
11 ms
container.html
19 ms
mercurio.js
599 ms
ads
201 ms
favicon
125 ms
nessie_icon_tiamat_black.png
65 ms
push
85 ms
activeview
20 ms
xpg_25.js
273 ms
ads
225 ms
15718864746214079727
28 ms
push
21 ms
pixel
26 ms
pixel
17 ms
backuol-300x250.html
145 ms
7847881046469421320
67 ms
push
24 ms
uol-300x250.html
144 ms
pixel
18 ms
uolaf.js
271 ms
activeview
12 ms
format9_g.html
554 ms
format9_g.html
700 ms
blp.css
270 ms
gen.js
266 ms
fb.js
270 ms
activeview
14 ms
activeview
40 ms
uolsigainit.min.js
270 ms
uolsigaretarget.min.js
272 ms
activeview
61 ms
e52235b9eba74a368818e01c18379504.jpeg
270 ms
5e07b0f89f98416499881e323ec5a91c.jpeg
392 ms
uoldna.html
546 ms
ui
31 ms
dna-persist.min.js
1000 ms
vocokan.xpg.uol.com.br SEO score
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vocokan.xpg.uol.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Vocokan.xpg.uol.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.
vocokan.xpg.uol.com.br
Open Graph description is not detected on the main page of Vocokan XPG Uol. 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: