15.1 sec in total
125 ms
14.5 sec
545 ms
Visit master--qaclaroco.myvtexdev.com now to see the best up-to-date Master Qaclaroco Myvtexdev content and also check out these interesting facts you probably never knew about master--qaclaroco.myvtexdev.com
Visit master--qaclaroco.myvtexdev.comWe analyzed Master--qaclaroco.myvtexdev.com page load time and found that the first response time was 125 ms and then it took 15 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
master--qaclaroco.myvtexdev.com performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value11.5 s
0/100
25%
Value14.3 s
1/100
10%
Value1,560 ms
13/100
30%
Value0.326
35/100
15%
Value10.2 s
25/100
10%
125 ms
9987 ms
299 ms
305 ms
308 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Master--qaclaroco.myvtexdev.com, 80% (48 requests) were made to Qaclaroco.vtexassets.com and 10% (6 requests) were made to Storecomponents.vtexassets.com. The less responsive or slowest element that took the longest time to load (10 sec) belongs to the original domain Master--qaclaroco.myvtexdev.com.
Page size can be reduced by 573.9 kB (82%)
702.4 kB
128.6 kB
In fact, the total size of Master--qaclaroco.myvtexdev.com main page is 702.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% 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. HTML takes 512.6 kB which makes up the majority of the site volume.
Potential reduce by 440.3 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 440.3 kB or 86% of the original size.
Potential reduce by 0 B
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. Master Qaclaroco Myvtexdev images are well optimized though.
Potential reduce by 133.5 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. Master--qaclaroco.myvtexdev.com needs all CSS files to be minified and compressed as it can save up to 133.5 kB or 80% of the original size.
Number of requests can be reduced by 48 (84%)
57
9
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Master Qaclaroco Myvtexdev. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
master--qaclaroco.myvtexdev.com
125 ms
master--qaclaroco.myvtexdev.com
9987 ms
vtex.store-theme@3.41.0$style.common.min.css
299 ms
vtex.store-theme@3.41.0$style.small.min.css
305 ms
vtex.store-theme@3.41.0$style.notsmall.min.css
308 ms
vtex.store-theme@3.41.0$style.large.min.css
288 ms
vtex.store-theme@3.41.0$style.xlarge.min.css
311 ms
common.min.css
365 ms
Container.min.css
366 ms
0.min.css
364 ms
0.min.css
365 ms
1.min.css
394 ms
HighlightOverlay.min.css
394 ms
NotificationBar.min.css
405 ms
Spinner.min.css
401 ms
3.min.css
403 ms
SearchBar.min.css
389 ms
1.min.css
400 ms
Minicart.min.css
400 ms
Logo.min.css
402 ms
vtex.product-list@0.25.0$overrides.css
434 ms
vtex.minicart@2.54.1$overrides.css
400 ms
vtex.store-theme@3.41.0$overrides.css
402 ms
polyfill.min.js
629 ms
polyfill.min.js
626 ms
index.min.js
532 ms
runtime.js
532 ms
prop-types.min.js
510 ms
react.production.min.js
508 ms
react-dom.production.min.js
517 ms
react-dom-server.browser.production.min.js
516 ms
react-intl.min.js
515 ms
history.min.js
515 ms
ramda.min.js
516 ms
ls.unveilhooks.min.js
516 ms
lazysizes.min.js
517 ms
cssrelpreload.min.js
526 ms
common.min.js
535 ms
graphql.min.js
527 ms
apollo.min.js
396 ms
index.min.js
310 ms
asset.min.js
312 ms
asset.min.js
307 ms
asset.min.js
305 ms
asset.min.js
345 ms
asset.min.js
323 ms
asset.min.js
323 ms
asset.min.js
323 ms
rc.js
229 ms
banner-principal.png
157 ms
sessions
1345 ms
store-theme-logo.png
85 ms
animate.min.css
44 ms
34.min.js
55 ms
211.min.js
55 ms
box.png
103 ms
delivery-fast.png
750 ms
store.png
736 ms
coupon.png
736 ms
155691-300-300
1739 ms
master--qaclaroco.myvtexdev.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
[aria-*] attributes do not have valid values
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
Document doesn't have a <title> element
No form fields have multiple labels
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Some elements have a [tabindex] value greater than 0
master--qaclaroco.myvtexdev.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
master--qaclaroco.myvtexdev.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
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
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Master--qaclaroco.myvtexdev.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 Spanish language. Our system also found out that Master--qaclaroco.myvtexdev.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.
master--qaclaroco.myvtexdev.com
Open Graph description is not detected on the main page of Master Qaclaroco Myvtexdev. 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: