2.9 sec in total
165 ms
1.3 sec
1.4 sec
Welcome to zappo.com homepage info - get ready to check Zappo best content right away, or after learning these important things about zappo.com
GET FREE SHIPPING & RETURNS! We have 1000s of styles of shoes & Zappos legendary 365-day return policy + 24/7 friendly customer service. Call 1-800-92
Visit zappo.comWe analyzed Zappo.com page load time and found that the first response time was 165 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
zappo.com performance score
name
value
score
weighting
Value2.8 s
58/100
10%
Value11.6 s
0/100
25%
Value5.0 s
63/100
10%
Value6,720 ms
0/100
30%
Value0.048
99/100
15%
Value20.6 s
2/100
10%
165 ms
241 ms
60 ms
89 ms
30 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Zappo.com, 48% (50 requests) were made to M.media-amazon.com and 39% (41 requests) were made to Zappos.com. The less responsive or slowest element that took the longest time to load (498 ms) relates to the external source Zappos.com.
Page size can be reduced by 1.5 MB (31%)
5.0 MB
3.5 MB
In fact, the total size of Zappo.com main page is 5.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. Only a small number of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 509.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 509.2 kB or 84% 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. Zappo images are well optimized though.
Potential reduce by 840.6 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 840.6 kB or 51% of the original size.
Potential reduce by 197.9 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. Zappo.com needs all CSS files to be minified and compressed as it can save up to 197.9 kB or 79% of the original size.
Number of requests can be reduced by 44 (43%)
103
59
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zappo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
zappo.com
165 ms
www.zappos.com
241 ms
gtm.js
60 ms
marty-zappos.app.da92a0ef151c4a6dba08.css
89 ms
marty-zappos.5465.84b132dd0813e758e548.css
30 ms
marty-zappos.8809.84b132dd0813e758e548.css
101 ms
marty-zappos.5201.84b132dd0813e758e548.css
31 ms
marty-zappos.2786.84b132dd0813e758e548.css
40 ms
marty-zappos.5520.84b132dd0813e758e548.css
28 ms
marty-zappos.9800.84b132dd0813e758e548.css
56 ms
marty-zappos.Landing.84b132dd0813e758e548.css
51 ms
marty-zappos.vendor.84b132dd0813e758e548.js
442 ms
marty-zappos.app.84b132dd0813e758e548.js
85 ms
marty-zappos.1523.84b132dd0813e758e548.js
86 ms
marty-zappos.7762.84b132dd0813e758e548.js
86 ms
marty-zappos.40.84b132dd0813e758e548.js
497 ms
marty-zappos.1467.84b132dd0813e758e548.js
441 ms
marty-zappos.377.84b132dd0813e758e548.js
442 ms
marty-zappos.8809.84b132dd0813e758e548.js
439 ms
marty-zappos.5201.84b132dd0813e758e548.js
498 ms
marty-zappos.2786.84b132dd0813e758e548.js
441 ms
marty-zappos.5520.84b132dd0813e758e548.js
496 ms
marty-zappos.Landing.84b132dd0813e758e548.js
498 ms
cs-container.js
497 ms
main.7d31c52.js
352 ms
Zappos-25-Years-Logo-Site.svg
450 ms
melody-sprite.2021.09.16._TTH_.svg
195 ms
APP-DOWNLOAD-CODE-INCENTIVE-HERO-1440x175_1._FMwebp_.jpg
195 ms
OUTDOOR-CAMPAIGN-HERO-STANDARD-1440x700-NEW._FMwebp_.jpg
329 ms
71zOJU8TvLL._AC_SR768,1024_.jpg
326 ms
61EdoR-GJWL._AC_SR768,1024_.jpg
327 ms
71E2mkgbmNL._AC_SR768,1024_.jpg
326 ms
91da9HAWUaL._AC_SR768,1024_.jpg
336 ms
71Aybcy4bdL._AC_SR768,1024_.jpg
326 ms
81jrOaWKy-L._AC_SR768,1024_.jpg
341 ms
61vWCvBVOML._AC_SR768,1024_.jpg
338 ms
61zTvRK7oEL._AC_SR768,1024_.jpg
336 ms
71KJ6fGHCZL._AC_SR768,1024_.jpg
337 ms
715txnQRm2L._AC_SR768,1024_.jpg
338 ms
71CsP5xfTxL._AC_SR768,1024_.jpg
346 ms
71bvmmRB6jL._AC_SR768,1024_.jpg
345 ms
71WJ2TFkJ4L._AC_SR768,1024_.jpg
348 ms
71PRXtS2JGL._AC_SR768,1024_.jpg
346 ms
810E-Vsxn8L._AC_SR768,1024_.jpg
346 ms
81DmCCYpfKL._AC_SR768,1024_.jpg
353 ms
714ClJ7tomL._AC_SR768,1024_.jpg
362 ms
71gZgubXBAL._AC_SR768,1024_.jpg
349 ms
81FQ8MiljUL._AC_SR768,1024_.jpg
351 ms
81MHImKna2L._AC_SR768,1024_.jpg
362 ms
710WfV6HQfL._AC_SR768,1024_.jpg
389 ms
71X011RCLSL._AC_SR768,1024_.jpg
361 ms
71U78BE2JHL._AC_SR768,1024_.jpg
363 ms
71E+L49jCYL._AC_SR768,1024_.jpg
364 ms
71Cgr2-ZocL._AC_SR768,1024_.jpg
366 ms
71UaR7n1KSL._AC_SR768,1024_.jpg
365 ms
71ccJC+D0mL._AC_SR768,1024_.jpg
368 ms
714425Rr2uL._AC_SR768,1024_.jpg
369 ms
81bUNyBcKqL._AC_SR768,1024_.jpg
369 ms
71l5ZqrT8YL._AC_SR768,1024_.jpg
374 ms
613T5BZZL1L._AC_SR768,1024_.jpg
371 ms
61-HWonqZvL._AC_SR768,1024_.jpg
375 ms
heart.17f367bcdf3bb773b332fa8a0f378cf0.svg
182 ms
star-sprite.69d5b63df89443e8c54a59419ff25a96.svg
181 ms
v7.js
327 ms
js
162 ms
data
386 ms
err.cgi
197 ms
err.cgi
197 ms
err.cgi
197 ms
err.cgi
196 ms
track.cgi
195 ms
err.cgi
192 ms
err.cgi
245 ms
err.cgi
277 ms
err.cgi
281 ms
err.cgi
258 ms
err.cgi
268 ms
err.cgi
262 ms
err.cgi
251 ms
err.cgi
283 ms
611xkNYsWFL._AC_SR768,1024_.jpg
194 ms
61nZFZ4AKuL._AC_SR768,1024_.jpg
162 ms
collect
55 ms
71uQOuaFW7L._AC_SR768,1024_.jpg
71 ms
619F96IXgOL._AC_SR768,1024_.jpg
61 ms
81UtU2x8smL._AC_SR768,1024_.jpg
61 ms
719A9LL7GHL._AC_SR768,1024_.jpg
63 ms
81JroUF2HgL._AC_SR768,1024_.jpg
60 ms
71lnx3QIcEL._AC_SR768,1024_.jpg
72 ms
sync
7 ms
713Ud6h-gGL._AC_SR768,1024_.jpg
58 ms
711+sP4SO2L._AC_SR768,1024_.jpg
58 ms
61Sj2w4nxXL._AC_SR768,1024_.jpg
60 ms
61mCONcNT9L._AC_SR768,1024_.jpg
60 ms
61Cau6EbDZL._AC_SR768,1024_.jpg
65 ms
61lweVWivUL._AC_SR768,1024_.jpg
61 ms
data
62 ms
data
39 ms
data
105 ms
pixel.js
37 ms
collect
19 ms
onload.cgi
48 ms
rp.gif
15 ms
a2_dyjidl91fbt8_telemetry
7 ms
err.cgi
50 ms
zappo.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 progressbar elements do not have accessible names.
zappo.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Page has valid source maps
zappo.com SEO score
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
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zappo.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Zappo.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.
zappo.com
Open Graph description is not detected on the main page of Zappo. 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: