87.7 sec in total
205 ms
67 sec
20.5 sec
Click here to check amazing Merchantwarehouse content for United States. Otherwise, check out these important facts you probably never knew about merchantwarehouse.com
Our semi-integrated unified commerce solution connects every channel, so merchants can engage their customers while shopping online and in-store.
Visit merchantwarehouse.comWe analyzed Merchantwarehouse.com page load time and found that the first response time was 205 ms and then it took 87.5 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 4 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
merchantwarehouse.com performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value12.8 s
0/100
25%
Value18.2 s
0/100
10%
Value18,290 ms
0/100
30%
Value0.06
98/100
15%
Value26.0 s
0/100
10%
205 ms
634 ms
2397 ms
2397 ms
2560 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Merchantwarehouse.com, 22% (20 requests) were made to Cayan.com and 8% (7 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source 1.tl813.com.
Page size can be reduced by 1.3 MB (44%)
2.9 MB
1.6 MB
In fact, the total size of Merchantwarehouse.com main page is 2.9 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.4 MB which makes up the majority of the site volume.
Potential reduce by 43.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 43.2 kB or 72% of the original size.
Potential reduce by 1.1 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. Merchantwarehouse images are well optimized though.
Potential reduce by 881.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 881.8 kB or 65% of the original size.
Potential reduce by 373.4 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. Merchantwarehouse.com needs all CSS files to be minified and compressed as it can save up to 373.4 kB or 84% of the original size.
Number of requests can be reduced by 51 (72%)
71
20
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Merchantwarehouse. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
merchantwarehouse.com
205 ms
cayan.com
634 ms
css
2397 ms
font-awesome.min.css
2397 ms
vyc0bfg.js
2560 ms
GetResource.ashx
1720 ms
GetResource.ashx
2178 ms
jquery.min.js
2368 ms
api.js
4097 ms
conversion.js
4099 ms
WebResource.axd
2091 ms
GetResource.ashx
2153 ms
ScriptResource.axd
2334 ms
ScriptResource.axd
2144 ms
unslider-min.js
4065 ms
bootstrap.min.js
4062 ms
plugins.js
2118 ms
application.js
4037 ms
sf14g.js
1765 ms
xvt2n8my9ytb.js
3048 ms
prum.min.js
1582 ms
recaptcha__en.js
16346 ms
gtm.js
19804 ms
Cayan-logo-tagline.svg
1579 ms
ico-unified.svg
1465 ms
IMG-unified-commerce.svg
17050 ms
IMG-unified-commerce-tablet.svg
8922 ms
IMG-unified-commerce-mobile.svg
10489 ms
st.js
19520 ms
sdk.js
19260 ms
LeFlHvsZjXu2c3ZRgBq9nKCWcynf_cDxXwCLxiixG1c.ttf
19260 ms
PIbvSEyHEdL91QLOQRnZ14nF5uFdDttMLvmWuJdhhgs.ttf
0 ms
tl813.js
20366 ms
BG-home-06262017.jpg
17797 ms
ICO-video.svg
17514 ms
lg-cubes.png
17796 ms
IMG-quote-party-city.jpg
19029 ms
IMG-home-genius-devices.png
17797 ms
LogHits
7850 ms
3881 ms
p.gif
10435 ms
fontawesome-webfont.woff
9597 ms
ByLA_FLEa-16SpQuTcQn4J0EAVxt0G0biEntp43Qt6E.ttf
5472 ms
d
1231 ms
d
7190 ms
d
7188 ms
d
9381 ms
d
9381 ms
d
8991 ms
blank
220 ms
7603 ms
analytics.js
7497 ms
conversion_async.js
4066 ms
hotjar-586872.js
8810 ms
munchkin.js
8752 ms
aquant.js
8752 ms
fbevents.js
3629 ms
uwt.js
7295 ms
6003 ms
tl813.js
5447 ms
0sTQzbapM8j.js
7362 ms
track
5560 ms
track
7343 ms
159556987786386
2407 ms
tl813.asp
1953 ms
639 ms
1691 ms
insight.min.js
3729 ms
dot.gif
2985 ms
collect
1713 ms
collect
3345 ms
log
3612 ms
munchkin.js
1416 ms
pixel;r=799907998;a=p-T-g4VqTm0mnbf;labels=_fp.event.Homepage;rf=3;fpan=1;fpa=P0-1097644217-1504628094900;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1504628094899;tzo=-180;ref=;url=https%3A%2F%2Fcayan.com%2F;ogl=logo.%2FSite%2FMedia%2FCayan%2FSite-Content%2FLogo-150x150%252Epng%2Clogo.%2FSite%2FMedia%2FCayan%2FSite-Content%2FLogo-250x250%252Epng%2Clogo.%2FSite%2FMedia%2FCayan%2FSite-Content%2FLogo-500x500%252Epng
3294 ms
modules-f524bccd859bfc7e394e1123f7f90405.js
2563 ms
rcj-99d43ead6bdf30da8ed5ffcb4f17100c.html
2108 ms
adsct
2609 ms
collect
1566 ms
visitWebPage
3173 ms
adsct
2381 ms
beacon.gif
1866 ms
index-prod.html
155 ms
normalize.min.css
969 ms
widget-11b381e65844bdf0a6068382d9c4eb42-prod.css
970 ms
vendor-ad476993dd129d35c050-prod.js
2120 ms
widget-576e937a4e93d3ab096f-prod.js
1967 ms
beacon.gif
0 ms
visit-data
19718 ms
15 ms
merchantwarehouse.com accessibility score
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
Links do not have a discernible name
merchantwarehouse.com 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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
merchantwarehouse.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Merchantwarehouse.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 Merchantwarehouse.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.
merchantwarehouse.com
Open Graph description is not detected on the main page of Merchantwarehouse. 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: