2.8 sec in total
165 ms
2.5 sec
124 ms
Visit search.mexgrocer.com now to see the best up-to-date Search Mexgrocer content for United States and also check out these interesting facts you probably never knew about search.mexgrocer.com
Advanced Search
Visit search.mexgrocer.comWe analyzed Search.mexgrocer.com page load time and found that the first response time was 165 ms and then it took 2.6 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.
search.mexgrocer.com performance score
165 ms
112 ms
261 ms
169 ms
61 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 8% of them (6 requests) were addressed to the original Search.mexgrocer.com, 24% (17 requests) were made to Cdn1.mexgrocer.com and 10% (7 requests) were made to Yui.yahooapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Lib.store.yahoo.net.
Page size can be reduced by 718.6 kB (69%)
1.0 MB
326.1 kB
In fact, the total size of Search.mexgrocer.com 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 781.6 kB which makes up the majority of the site volume.
Potential reduce by 42.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. 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 42.0 kB or 73% of the original size.
Potential reduce by 2 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. Search Mexgrocer images are well optimized though.
Potential reduce by 549.5 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 549.5 kB or 70% of the original size.
Potential reduce by 127.2 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. Search.mexgrocer.com needs all CSS files to be minified and compressed as it can save up to 127.2 kB or 81% of the original size.
Number of requests can be reduced by 48 (69%)
70
22
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Search Mexgrocer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
search.mexgrocer.com
165 ms
pdMobileRedirect.js
112 ms
jquery-1.7.2.min.js
261 ms
search-category-selector.js
169 ms
globalScript.js
61 ms
mex-global-scripts-2014.js
169 ms
sc-scripts.js
164 ms
mex-grocer-styles-2.css
179 ms
plusone.js
52 ms
functions.js.aspx
102 ms
XmlHttpLookup.js
99 ms
style.css
108 ms
dom-drag.js
103 ms
quant.js
12 ms
stop.lexity.js
111 ms
ga.mexgrocer.js
58 ms
nakamoa.mailchimp360.js
130 ms
lk.ca.1.0.js
132 ms
ywa.js
56 ms
ylc_1.9.js
11 ms
beacon-1.3.6.4.js
12 ms
recs-1.3.2.2.js
4 ms
cb=gapi.loaded_0
42 ms
mex-grocer-logo.gif
36 ms
search-go.gif
2072 ms
breadcrumbsbg.gif
31 ms
logo-small.gif
27 ms
main-sprite-optimized.png
123 ms
mailing-go.gif
53 ms
shoppingbadge.png
67 ms
creditcards.png
49 ms
paging-top.gif
220 ms
tab-bg.jpg
116 ms
main-sprite-optimized.png
16 ms
newsletter-bg.png
73 ms
sa-close.gif
107 ms
pixel;r=21444484;a=p-02whi_WBYhuM2;fpan=1;fpa=P0-346361424-1458496168765;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458496168764;tzo=-180;ref=;url=http%3A%2F%2Fsearch.mexgrocer.com%2F;ogl=title.%2Csite_name.mexgrocer%252Ecom%2Ctype.product%2Curl.http%3A%2F%2Fwww%252Emexgrocer%252Ecom%2Fadvanced-search%252Ehtml%2Cimage.%2Cdescription.
31 ms
prum.min.js
13 ms
refreshCookieLogin.php
154 ms
newsletter-signup.png
139 ms
gau.ee.js
31 ms
js
47 ms
site-dispatcher.html
12 ms
analytics.js
6 ms
ec.js
5 ms
gtmp_compiled_9-hatpZX8VY.js
7 ms
collect
11 ms
collect
54 ms
recs=
45 ms
wg-order
120 ms
tm2
20 ms
checkout-css-2014.css
106 ms
checkout-header-2014-2.js
108 ms
container.css
8 ms
common-16d82d0.js
95 ms
yahoo-min.js
8 ms
dom-min.js
12 ms
event-min.js
12 ms
element-min.js
12 ms
container-min.js
11 ms
cookie-min.js
11 ms
behavior-d6d353e.js
91 ms
checkout-footer-2014-5.js
104 ms
ga.mexgrocer.js
100 ms
gtmp_compiled_B7HPFKWOYMU.js
37 ms
gb2
56 ms
clear.gif
35 ms
ts_badge_v3.png
16 ms
ts_flyover_v2.png
27 ms
ts_flyover_stars.png
28 ms
dcc087ddec02f5542e0ea3be2f507256
16 ms
search.mexgrocer.com SEO score
EN
N/A
WINDOWS-1252
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Search.mexgrocer.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Search.mexgrocer.com main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
search.mexgrocer.com
Open Graph description is not detected on the main page of Search Mexgrocer. 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: