22.2 sec in total
92 ms
21 sec
1.1 sec
Visit vtex.com 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
A complete, connected, and composable platform. Build, manage and deliver advanced B2B, B2C and Marketplace commerce experiences without the complexity.
Visit vtex.comWe analyzed Vtex.com page load time and found that the first response time was 92 ms and then it took 22.1 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 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
vtex.com performance score
name
value
score
weighting
Value2.3 s
73/100
10%
Value2.6 s
87/100
25%
Value8.9 s
15/100
10%
Value1,270 ms
19/100
30%
Value0.144
77/100
15%
Value10.5 s
23/100
10%
92 ms
111 ms
77 ms
105 ms
102 ms
Our browser made a total of 140 requests to load all elements on the main page. We found that 3% of them (4 requests) were addressed to the original Vtex.com, 69% (96 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 (19.9 sec) relates to the external source Freegeoip.net.
Page size can be reduced by 1.1 MB (65%)
1.6 MB
576.5 kB
In fact, the total size of Vtex.com main page is 1.6 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 893.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 893.9 kB or 72% of the original size.
Potential reduce by 181 B
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 needs all CSS files to be minified and compressed as it can save up to 181 B or 67% of the original size.
Number of requests can be reduced by 40 (33%)
122
82
The browser has sent 122 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.
www.vtex.com
92 ms
jquery-1.8.3.min.js
111 ms
swfobject.js
77 ms
vtex.ajax.wait.js
105 ms
vtex.common.js
102 ms
vtex-i18n.min.js
71 ms
vtex-utils.min.js
72 ms
dust-core-2.3.5.min.js
70 ms
vtex.tagmanager.helper.js
107 ms
vtex-events-all.min.js
70 ms
vtex-analytics.js
73 ms
vtex.min.js
104 ms
css
69 ms
css
201 ms
0-vtx-web-style.css
152 ms
form_contact.css
91 ms
modernizr.min.e89aeb57.js
137 ms
css
377 ms
v2.js
652 ms
form_contact.min.js
134 ms
0-vtx-web-application.js
395 ms
addthis_widget.js
187 ms
scripts.geral.min.js
717 ms
Track.js
187 ms
thickbox.js
132 ms
json2.js
185 ms
vtex.viewPart.CallCenterDisclaimer.js
184 ms
vtex.viewPart.ajaxLoader_V2.js
184 ms
vtexadicional.css
140 ms
analytics.js
248 ms
gtm.js
210 ms
getProfile
194 ms
sprite-general-s0f43a4ec9b.png
226 ms
01_home_full.jpg
340 ms
brand-cea.fe14a7fb.png
156 ms
brand-ckj.0d05674d.png
153 ms
brand-electrolux.0829cb4b.png
154 ms
brand-sony.cf49a73a.png
156 ms
brand-loreal.685c226c.png
159 ms
brand-mambo.3a070f9f.png
158 ms
brand-consul.8ac4bc4e.png
159 ms
brand-brastemp.380c5914.png
201 ms
brand-avon.d2b71ee6.png
212 ms
brand-boticario.4c10fe61.png
213 ms
sec-end-to-end-bx01.jpg
270 ms
sec-end-to-end-bx02.jpg
471 ms
sec-end-to-end-bx03.jpg
305 ms
sec-end-to-end-bx04.jpg
300 ms
sec-end-to-end-bx05.jpg
276 ms
sec-end-to-end-bx06.jpg
310 ms
sec-end-to-end-bx07.jpg
297 ms
sec-end-to-end-bx08.jpg
308 ms
sec-end-to-end-bx09.jpg
312 ms
sec-end-to-end-bx10.jpg
395 ms
sec-end-to-end-bx01-item01.png
332 ms
sec-end-to-end-bx01-item02.png
330 ms
sec-end-to-end-bx02-item01.png
395 ms
sec-end-to-end-bx02-item02.png
397 ms
sec-end-to-end-bx02-item03.png
397 ms
sec-end-to-end-bx02-item04.png
393 ms
sec-end-to-end-bx02-item05.png
400 ms
sec-end-to-end-bx02-item06.png
395 ms
sec-end-to-end-bx03-item01.png
452 ms
sec-end-to-end-bx04-item01.png
465 ms
sec-end-to-end-bx04-item02.png
458 ms
sec-end-to-end-bx04-item03.png
464 ms
sec-end-to-end-bx04-item04.png
462 ms
sec-end-to-end-bx08-item01.png
321 ms
sec-end-to-end-bx08-item02.png
323 ms
sec-end-to-end-bx07-item01.png
449 ms
sec-end-to-end-bx07-item02.png
451 ms
sec-end-to-end-bx07-item03.png
470 ms
sec-end-to-end-bx06-item01.png
444 ms
sec-end-to-end-bx06-item02.png
446 ms
sec-end-to-end-bx06-item03.png
444 ms
gothamrnd-book.c66a2099.woff
440 ms
texgyreadventorregular.c50af236.woff
446 ms
texgyreadventorbold.a471bb4d.woff
449 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
153 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
173 ms
ecommerce.js
74 ms
collect
96 ms
637676.js
265 ms
sec-end-to-end-bx05-item01.png
398 ms
sec-end-to-end-bx05-item02.png
396 ms
tag.js
121 ms
sec-end-to-end-bx09-item01.png
399 ms
sec-end-to-end-bx09-item02.png
387 ms
collect
36 ms
multi-modelo__img.png
343 ms
home-companie-fravega.ba1d2256.png
335 ms
collect
302 ms
home-companie-schumann.6b9cb205.png
312 ms
home-companie-whirlpool.f63bbf6a.png
310 ms
home-atuacao-cea.7bb3e613.png
309 ms
home-atuacao-boticario.87546e42.png
307 ms
home-atuacao-consul.7832a5ae.png
304 ms
home-atuacao-fravega.44c15163.png
305 ms
home-atuacao-personal.5eac3bf7.png
283 ms
home-atuacao-sony.cace28d0.png
281 ms
home-atuacao-opaline.9bfc3db0.png
227 ms
home-atuacao-viauno.943fc770.png
221 ms
home-atuacao-tienda.8d7db6ab.png
223 ms
home-atuacao-totto.f87dee56.png
223 ms
home-atuacao-comandato.9552027a.png
221 ms
home-atuacao-perrosygatos.70ebd8e8.png
221 ms
b_callandbuy.png
220 ms
home-atuacao-jackvartanian.9097370a.png
165 ms
.jsonp
635 ms
home-atuacao-kota.1a94aa84.png
162 ms
home-atuacao-maslu.fb502c0a.png
630 ms
home-atuacao-mosca.fa99e256.png
630 ms
home-atuacao-wong.a645ace2.png
156 ms
b_totto.png
154 ms
b_ge.png
630 ms
home-atuacao-kalua.54486dee.png
625 ms
mapa.39aa7aa6.png
511 ms
home-codificacao-gartner.be31334e.png
504 ms
home-codificacao-forrester.ddcbc6ce.png
512 ms
home-codificacao-pci.4a973cb3.png
503 ms
certificado.adf9e5ba.jpg
508 ms
footer__logo-vtex.png
501 ms
footer__gb.png
503 ms
sprites.f8ac915a.png
500 ms
floating-btn-form-contact.jpg
499 ms
19895 ms
19743 ms
Track.aspx
194 ms
disclaimer
195 ms
79a188bc-0506-4c92-b705-c04d4e43969b
231 ms
300lo.json
122 ms
customselect-arrow.91d8f999.gif
89 ms
sh.953eb77977227bfd253ee158.html
60 ms
storage.min.html
163 ms
7058613
384 ms
zones
382 ms
layers.486057f6e3ab422798c9.js
30 ms
pt.js
41 ms
7058613
85 ms
7058613
95 ms
vtex.com 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 best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
vtex.com 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 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 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
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: