3 sec in total
778 ms
1.7 sec
537 ms
Click here to check amazing Vick content for Mexico. Otherwise, check out these important facts you probably never knew about vick.com.mx
Obtén eficaz alivio para síntomas como congestión nasal, fiebre, garganta irritada y otros, causados por la gripa y tos.
Visit vick.com.mxWe analyzed Vick.com.mx page load time and found that the first response time was 778 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
vick.com.mx performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value6.6 s
8/100
25%
Value9.1 s
13/100
10%
Value2,480 ms
4/100
30%
Value0.075
95/100
15%
Value21.8 s
1/100
10%
778 ms
139 ms
17 ms
14 ms
15 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 35% of them (40 requests) were addressed to the original Vick.com.mx, 45% (52 requests) were made to Media.vick.com.mx and 5% (6 requests) were made to Cookieconsent.pg.com. The less responsive or slowest element that took the longest time to load (778 ms) belongs to the original domain Vick.com.mx.
Page size can be reduced by 594.5 kB (57%)
1.0 MB
442.6 kB
In fact, the total size of Vick.com.mx main page is 1.0 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. 50% of websites need less resources to load. Javascripts take 504.6 kB which makes up the majority of the site volume.
Potential reduce by 102.0 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. This page needs HTML code to be minified as it can gain 33.8 kB, which is 28% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 102.0 kB or 85% of the original size.
Potential reduce by 5.9 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. Vick images are well optimized though.
Potential reduce by 338.8 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 338.8 kB or 67% of the original size.
Potential reduce by 147.6 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. Vick.com.mx needs all CSS files to be minified and compressed as it can save up to 147.6 kB or 79% of the original size.
Number of requests can be reduced by 62 (55%)
112
50
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vick. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.vick.com.mx
778 ms
mainstyles.css
139 ms
sifr.css
17 ms
jquery.autocomplete.css
14 ms
sifr.js
15 ms
noscript.css
16 ms
swfobject2_1.js
29 ms
WebResource.axd
18 ms
ScriptResource.axd
33 ms
ScriptResource.axd
27 ms
jquery-1.4.2.js
28 ms
easySlider1.5.js
17 ms
jquery.timers-1.0.0.js
21 ms
main.js
37 ms
Welcome.js
28 ms
jquery.autocomplete.js
31 ms
jQuery.equalHeights.js
31 ms
jquery.cookie.js
36 ms
tag.js
8 ms
blank.gif
162 ms
IMG_L_T001_87916452.jpg
127 ms
CalloutFB.aspx
353 ms
tag
47 ms
close.jpg
25 ms
page-bg.gif
62 ms
header-bg.jpg
28 ms
arrow-search.png
52 ms
search-labelbg.png
29 ms
img_i_search.gif
49 ms
access-bg.png
27 ms
arrow-down.gif
56 ms
sprite.png
57 ms
btn_register-now.gif
56 ms
btn_log-in.gif
107 ms
IMG_I_Mexico.gif
77 ms
IMG_M_button_arrow_link.png
74 ms
content-bg.jpg
79 ms
IMG_C_SymptomForecaster_es.png
83 ms
cold-flutracker-mx.gif
81 ms
cold-flu-allergy.jpg
92 ms
IMG_I_article.gif
90 ms
IMG_I_tip.gif
91 ms
IMG_P_CF_Vick_Miel_120ml_C.png
84 ms
IMG_P_CF_44exp_120ml_C.png
88 ms
IMG_P_CF_44exp_inf_120ml_C.png
103 ms
IMG_P_CF_VPY_C.png
108 ms
IMG_P_CF_VPY_MyC_s_C.png
104 ms
IMG_P_CF_VPY_MyL_s_C.png
108 ms
IMG_P_CF_VPF_C.png
105 ms
IMG_P_CF_VPF_Inhaler_C.png
166 ms
IMG_P_CF_VTD_M_C.png
110 ms
IMG_P_CF_VTD_N_C.png
116 ms
IMG_P_CF_VTD_L_C.png
129 ms
IMG_P_CF_VTD_C_C.png
167 ms
about_us.png
130 ms
about-us3.jpg
132 ms
bg-seguinos.png
162 ms
facebook.png
174 ms
youtube.png
161 ms
IMG_M_vick_logo_MX.png
159 ms
fd3acb10c6de91dfa638ad9e2fa03a4cbec107a5.js
6 ms
home_banner_right.png
222 ms
IMG_C_VCK_Family_3b_210x138.png
152 ms
IMG_P_VPF_D.png
150 ms
278afe2d73add98b2852b30170b81e0cd7f64e79.js
21 ms
IMG_P_VTD_M_D.png
134 ms
IMG_P_VPY_D.png
133 ms
IMG_P_VPY_MyT_s_D.png
182 ms
IMG_P_VPY_MyC_s_D.png
187 ms
IMG_P_VTD_D.png
188 ms
0a0c400eac8fce00ad48e836979c2062b70bff40.js
19 ms
IMG_C_VCK_Family_1b_244x149.png
169 ms
IMG_C_NF_SolutionFinder_mexico.png
163 ms
IMG_C_SymptomForecaster_es.png
161 ms
IMG_C_youtube.png
164 ms
footer-bg.gif
166 ms
footerbox-bg.jpg
179 ms
iframe_api
31 ms
tag
20 ms
gw.js
182 ms
analytics.js
30 ms
mrcookie.min.js
82 ms
www-widgetapi.js
71 ms
collect
37 ms
collect
33 ms
collect
33 ms
69 ms
ct2
9 ms
notice-banner.html
134 ms
mainstyles.css
39 ms
jquery-1.4.2.js
86 ms
jquery.timers-1.0.0.js
71 ms
main.js
88 ms
jquery.autocomplete.js
94 ms
iepngfix_tilebg.js
88 ms
jQuery.equalHeights.js
94 ms
swfobject2_1.js
81 ms
IMG_P_VPF_Inhaler_D.png
61 ms
page-bg.gif
56 ms
header-bg.jpg
62 ms
arrow-search.png
63 ms
search-labelbg.png
59 ms
access-bg.png
60 ms
arrow-down.gif
59 ms
content-bg.jpg
57 ms
bg-seguinos.png
66 ms
sprite.png
72 ms
footer-bg.gif
67 ms
footerbox-bg.jpg
70 ms
opt-in-new.min.css
27 ms
cookieframe.min.js
32 ms
tag.js
39 ms
mister_cookie.png
23 ms
buttons.png
24 ms
963700939.js
104 ms
vick.com.mx 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
button, link, and menuitem elements do not have accessible names.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
vick.com.mx best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
vick.com.mx SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vick.com.mx can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Vick.com.mx 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.
vick.com.mx
Open Graph description is not detected on the main page of Vick. 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: