29.7 sec in total
410 ms
25.9 sec
3.4 sec
Visit vtex.com.br now to see the best up-to-date Vtex content for Colombia and also check out these interesting facts you probably never knew about vtex.com.br
Confira todas as funcionalidades da plataforma VTEX e explore soluções de comércio, marketplace e gestão de pedidos em um só lugar.
Visit vtex.com.brWe analyzed Vtex.com.br page load time and found that the first response time was 410 ms and then it took 29.2 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 were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
vtex.com.br performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value4.8 s
31/100
25%
Value11.0 s
6/100
10%
Value840 ms
34/100
30%
Value0.144
77/100
15%
Value9.5 s
30/100
10%
410 ms
690 ms
172 ms
124 ms
116 ms
Our browser made a total of 142 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Vtex.com.br, 68% (97 requests) were made to Vtexstore.vteximg.com.br and 5% (7 requests) were made to Io.vtex.com.br. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Freegeoip.net.
Page size can be reduced by 1.2 MB (67%)
1.8 MB
612.0 kB
In fact, the total size of Vtex.com.br main page is 1.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 155.2 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 155.2 kB or 78% of the original size.
Potential reduce by 17.7 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. Vtex images are well optimized though.
Potential reduce by 862.0 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 862.0 kB or 71% of the original size.
Potential reduce by 184.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. Vtex.com.br needs all CSS files to be minified and compressed as it can save up to 184.1 kB or 84% of the original size.
Number of requests can be reduced by 40 (33%)
123
83
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vtex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
vtex.com.br
410 ms
www.vtex.com
690 ms
jquery-1.8.3.min.js
172 ms
swfobject.js
124 ms
vtex.ajax.wait.js
116 ms
vtex.common.js
113 ms
vtex-i18n.min.js
109 ms
vtex-utils.min.js
105 ms
dust-core-2.3.5.min.js
107 ms
vtex.tagmanager.helper.js
117 ms
vtex-events-all.min.js
103 ms
vtex-analytics.js
104 ms
vtex.min.js
145 ms
css
107 ms
css
329 ms
0-vtx-web-style.css
242 ms
form_contact.css
96 ms
modernizr.min.e89aeb57.js
95 ms
vtexadicional.css
139 ms
css
395 ms
v2.js
699 ms
form_contact.min.js
104 ms
0-vtx-web-application.js
484 ms
addthis_widget.js
949 ms
scripts.geral.min.js
3813 ms
Track.js
191 ms
thickbox.js
190 ms
json2.js
186 ms
vtex.viewPart.CallCenterDisclaimer.js
728 ms
vtex.viewPart.ajaxLoader_V2.js
373 ms
analytics.js
623 ms
01_home_full.jpg
1242 ms
brand-cea.fe14a7fb.png
250 ms
brand-ckj.0d05674d.png
253 ms
brand-electrolux.0829cb4b.png
254 ms
brand-sony.cf49a73a.png
262 ms
brand-loreal.685c226c.png
263 ms
brand-mambo.3a070f9f.png
259 ms
brand-consul.8ac4bc4e.png
475 ms
brand-brastemp.380c5914.png
476 ms
brand-avon.d2b71ee6.png
471 ms
brand-boticario.4c10fe61.png
478 ms
sec-end-to-end-bx01.jpg
485 ms
sec-end-to-end-bx02.jpg
490 ms
sec-end-to-end-bx03.jpg
480 ms
sec-end-to-end-bx04.jpg
486 ms
sec-end-to-end-bx05.jpg
491 ms
sec-end-to-end-bx06.jpg
495 ms
sec-end-to-end-bx07.jpg
496 ms
sec-end-to-end-bx08.jpg
504 ms
sec-end-to-end-bx09.jpg
499 ms
sec-end-to-end-bx10.jpg
495 ms
sec-end-to-end-bx01-item01.png
508 ms
sec-end-to-end-bx01-item02.png
515 ms
sec-end-to-end-bx02-item01.png
532 ms
sec-end-to-end-bx02-item02.png
526 ms
sec-end-to-end-bx02-item03.png
553 ms
sec-end-to-end-bx02-item04.png
702 ms
sec-end-to-end-bx02-item05.png
555 ms
sec-end-to-end-bx02-item06.png
698 ms
sec-end-to-end-bx03-item01.png
703 ms
sec-end-to-end-bx04-item01.png
705 ms
sec-end-to-end-bx04-item02.png
723 ms
sec-end-to-end-bx04-item03.png
736 ms
gtm.js
459 ms
getProfile
224 ms
sec-end-to-end-bx04-item04.png
513 ms
sec-end-to-end-bx08-item01.png
496 ms
sec-end-to-end-bx08-item02.png
510 ms
sec-end-to-end-bx07-item01.png
506 ms
sec-end-to-end-bx07-item02.png
504 ms
sec-end-to-end-bx07-item03.png
508 ms
sec-end-to-end-bx06-item01.png
504 ms
sec-end-to-end-bx06-item02.png
317 ms
sec-end-to-end-bx06-item03.png
321 ms
sec-end-to-end-bx05-item01.png
333 ms
sec-end-to-end-bx05-item02.png
350 ms
sec-end-to-end-bx09-item01.png
343 ms
sec-end-to-end-bx09-item02.png
341 ms
home-companie-fravega.ba1d2256.png
340 ms
home-companie-schumann.6b9cb205.png
414 ms
home-companie-whirlpool.f63bbf6a.png
431 ms
home-atuacao-cea.7bb3e613.png
412 ms
home-atuacao-boticario.87546e42.png
423 ms
home-atuacao-consul.7832a5ae.png
418 ms
home-atuacao-fravega.44c15163.png
422 ms
home-atuacao-personal.5eac3bf7.png
726 ms
home-atuacao-sony.cace28d0.png
414 ms
home-atuacao-opaline.9bfc3db0.png
412 ms
home-atuacao-viauno.943fc770.png
572 ms
home-atuacao-tienda.8d7db6ab.png
568 ms
home-atuacao-totto.f87dee56.png
576 ms
home-atuacao-comandato.9552027a.png
551 ms
home-atuacao-perrosygatos.70ebd8e8.png
625 ms
gothamrnd-book.c66a2099.woff
1292 ms
texgyreadventorregular.c50af236.woff
1520 ms
texgyreadventorbold.a471bb4d.woff
1515 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
1041 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
1051 ms
b_callandbuy.png
588 ms
ecommerce.js
262 ms
collect
215 ms
home-atuacao-jackvartanian.9097370a.png
479 ms
home-atuacao-kota.1a94aa84.png
476 ms
home-atuacao-maslu.fb502c0a.png
489 ms
home-atuacao-mosca.fa99e256.png
479 ms
home-atuacao-wong.a645ace2.png
458 ms
b_totto.png
459 ms
b_ge.png
883 ms
home-atuacao-kalua.54486dee.png
864 ms
mapa.39aa7aa6.png
880 ms
home-codificacao-gartner.be31334e.png
867 ms
home-codificacao-forrester.ddcbc6ce.png
869 ms
home-codificacao-pci.4a973cb3.png
869 ms
certificado.adf9e5ba.jpg
1120 ms
footer__logo-vtex.png
845 ms
footer__gb.png
1064 ms
floating-btn-form-contact.jpg
817 ms
sprite-general-s0f43a4ec9b.png
1044 ms
multi-modelo__img.png
1044 ms
sprites.f8ac915a.png
814 ms
637676.js
2447 ms
formContact-sa255a5e04d.png
764 ms
tag.js
502 ms
collect
448 ms
collect
484 ms
.jsonp
305 ms
storage.min.html
354 ms
7058613
341 ms
zones
216 ms
19767 ms
20126 ms
Track.aspx
597 ms
disclaimer
583 ms
79a188bc-0506-4c92-b705-c04d4e43969b
481 ms
300lo.json
390 ms
7058613
488 ms
customselect-arrow.91d8f999.gif
367 ms
sh.953eb77977227bfd253ee158.html
397 ms
layers.486057f6e3ab422798c9.js
164 ms
pt.js
79 ms
7058613
103 ms
vtex.com.br accessibility score
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
Buttons do not have an accessible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
vtex.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
vtex.com.br SEO score
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
Tap targets are not sized appropriately
EN
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vtex.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 Vtex.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.
vtex.com.br
Open Graph description is not detected on the main page of Vtex. 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: