This is a case study of Foot Locker’s e-commerce user experience (UX) performance. It’s based on an exhaustive performance review of 837 design elements. 213 other sites have also been benchmarked for a complete picture of the e-commerce UX landscape.
Foot Locker’s overall e-commerce UX performance is mediocre. Notably, Foot Locker’s UX performance is impeded by broken On-Site Search, poor Customer Accounts, and mediocre Product Page.
First benchmarked in April 7, 2012, and reviewed 23 times since then, most recently December 18, 2022.
Overall UX Performance
866 Guidelines · Performance:
Desktop Web
482 Guidelines · Performance:
Homepage & Category
54 Guidelines · Performance:
On-Site Search
47 Guidelines · Performance:
Product Lists & Filtering
90 Guidelines · Performance:
Product Page
96 Guidelines · Performance:
Cart & Checkout
130 Guidelines · Performance:
Customer Accounts
38 Guidelines · Performance:
Order Tracking & Returns
27 Guidelines · Performance:
Mobile Web
384 Guidelines · Performance:
To learn how we calculate our performance scores and read up on our evaluation criteria and scoring algorithm head over to our Methodology page.
The scatterplot you see above is the free version we make public to all our users. If you wish to dive deeper and learn about each guideline and even review your own site you’ll need to get premium access.
21 pages of Foot Locker’s e-commerce site, marked up with 299 best practice examples:
15 pages of Foot Locker’s e-commerce site, marked up with 262 best practice examples:
Explore similar case studies of Apparel & Accessories sites:
45 page designs: desktop, mobile
79 page designs: desktop, app, mobile
38 page designs: mobile, desktop
68 page designs: app, mobile, desktop
64 page designs: app, mobile, desktop
47 page designs: desktop, mobile
77 page designs: desktop, app, mobile
44 page designs: desktop, mobile
Every 2nd week, we publish a new article on how to build “state of the art” e-commerce experiences — here’s 5 popular ones:
See all 363 articles in the full public archive.