2.5 sec in total
291 ms
1.8 sec
374 ms
Click here to check amazing John Henry content for Mexico. Otherwise, check out these important facts you probably never knew about johnhenry.com.mx
Encuentra lo último en moda masculina al mejor precio en nuestra tienda en línea. Camisas, playeras, pantalones, sacos y mucho más.
Visit johnhenry.com.mxWe analyzed Johnhenry.com.mx page load time and found that the first response time was 291 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
johnhenry.com.mx performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value13.9 s
0/100
25%
Value10.7 s
7/100
10%
Value2,190 ms
6/100
30%
Value0
100/100
15%
Value19.8 s
2/100
10%
291 ms
52 ms
73 ms
67 ms
72 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 21% of them (15 requests) were addressed to the original Johnhenry.com.mx, 13% (9 requests) were made to Static.klaviyo.com and 10% (7 requests) were made to Cdn.shopify.com. The less responsive or slowest element that took the longest time to load (528 ms) relates to the external source Staticw2.yotpo.com.
Page size can be reduced by 367.3 kB (26%)
1.4 MB
1.0 MB
In fact, the total size of Johnhenry.com.mx main page is 1.4 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. 60% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 221.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 221.3 kB or 83% of the original size.
Potential reduce by 1.3 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. John Henry images are well optimized though.
Potential reduce by 144.4 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 144.4 kB or 14% of the original size.
Potential reduce by 279 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. Johnhenry.com.mx has all CSS files already compressed.
Number of requests can be reduced by 55 (86%)
64
9
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of John Henry. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.johnhenry.com.mx
291 ms
styles.css
52 ms
vendor.min.js
73 ms
theme.js
67 ms
preloads.js
72 ms
load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js
69 ms
features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js
71 ms
bss-pl-style.min.css
71 ms
shopify-perf-kit-unstable.min.js
237 ms
analytics.js
54 ms
smartmenu-v2.js
240 ms
slideshow-v2.js
303 ms
quickview-v1.js
302 ms
loader.js
431 ms
1f6bf9a9b092568288838bafc2db3e27.js
434 ms
trekkie.storefront.72278931d43be9cf54de64f928f82f2eef1fa047.min.js
184 ms
shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js
184 ms
shopify-boomerang-1.0.0.min.js
181 ms
Logo_JH-01_693670ab-9015-4da0-9bd8-576974b2dd36_640x.png
336 ms
collect
247 ms
tradegothic_n4.9046484b84e9d547f2568166c70f42465f6e8316.woff
246 ms
tradegothic_n7.ffb764894c72ccd893ba69107b7abacd51e7c216.woff
245 ms
tradegothicnext_n7.58165da5b0a47541ffa29bf3988b93a80f548b7e.woff
245 ms
sport2.jpg
108 ms
css
55 ms
MwQ5bhbm2POE2V9BOw.woff
16 ms
powr.js
232 ms
conekta_shopify.js
178 ms
f538ff546e3a610278568b0cc.js
235 ms
topbar-script_v4.js
176 ms
skeletopapp.js
173 ms
widget.js
528 ms
1541114423.js
192 ms
SizingPlugin.prod.js
192 ms
embedder.js
191 ms
globocheckout_init.js
79 ms
ec6daa18d9f049b2a730374f8.js
233 ms
site-683880-c88f3f95fc7816cdf64b7c1056a82643d2904d91.js
173 ms
widget.js
286 ms
avada-fsb.min.js
190 ms
widgets.js
453 ms
product_label_log.js
232 ms
johnhenrymmh.20230331184956.scripttag.js
170 ms
klaviyo.js
189 ms
instafeed-3bcbd0e72428174062271d36dedf19dc.js
231 ms
quickannouncementbar.js
158 ms
freeshippingbar.js
186 ms
site.js
17 ms
embedder.js
63 ms
scriptVersion.json
63 ms
fender_analytics.19c4683d5ea1c98d04df.js
69 ms
static.28446ee8cef515b22f21.js
70 ms
runtime.49d16a6a7981399b1cf3.js
24 ms
sharedUtils.42030bfca3a535006d81.js
66 ms
vendors~signup_forms~post_identification_sync~web_personalization~reviews~atlas.b0930143925bb765e2d3.js
61 ms
vendors~signup_forms~post_identification_sync~onsite-triggering.98adbd4f3c00592d4b9b.js
38 ms
vendors~signup_forms~onsite-triggering.f88945af9a706719d64b.js
64 ms
vendors~signup_forms.abacb7c1d6b75deab0ac.js
52 ms
default~signup_forms~onsite-triggering.39d05cf4fd44271c1730.js
36 ms
signup_forms.2fd5e9877647686cae47.js
67 ms
css
33 ms
jquery.min.js
67 ms
jquery.min.js
84 ms
json2.min.js
119 ms
ppop_bfpop-up_1024x1024.jpg
332 ms
styles.css
12 ms
683880
36 ms
settings-1723440940.json
28 ms
widget.css
270 ms
i
16 ms
open_sans.css
18 ms
johnhenry.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
ARIA toggle fields do not have accessible names
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
johnhenry.com.mx 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
Browser errors were logged to the console
Page has valid source maps
johnhenry.com.mx SEO score
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
EN
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Johnhenry.com.mx 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 Johnhenry.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.
johnhenry.com.mx
Open Graph data is detected on the main page of John Henry. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: