E-commerce UX Audit Checklist: What to Check, Score and Fix

How does the audit test site search and navigation?

The audit runs the same five query types on every store, and each one passes only when the first results, or a helpful zero-result page, answer it.

Start from the zero-result queries in the search log, because they show shoppers' words the catalog misses. The sheet uses made-up apparel queries; swap in your own.

Autocomplete should suggest products within a few letters, a zero-result page should offer a spelling fix or popular categories, and results need the same filters as category pages. For navigation, check labels in shoppers' words, a clickable parent category, breadcrumbs, and a search field visible on mobile without opening the menu. Screenshot every failure; that log is your first page of findings.

Which listing and product page checks find the leaks?

On listing pages, check filters and product cards against what shoppers compare; on product pages, check the variant selector, delivery cost and date, size guide and returns line.

On the product listing page (PLP):

• Filters match the attributes each category is bought on, such as size, color and price, because generic filters hide the one that matters.
• Applied filters stay visible and removable one by one, so undoing one does not reset the rest.
• Product cards show price, rating and swatches, so shoppers compare without opening each product.
• Sort order offers the sorts shoppers use, such as best-selling and price, and stays applied after filtering, so results do not reshuffle.
• The back button keeps the scroll position, so shoppers do not restart a long list.

A product page UX audit reads the product detail page (PDP) next to your return reasons, since a sizing question left open can come back as a "wrong size" return:

• The variant selector marks out-of-stock sizes and flags a missing size, so add to cart never fails silently.
• Delivery cost and date sit next to the add-to-cart button, so cost is settled before the cart.
• The size guide and return policy sit one tap away, because they answer the questions behind your return tags.
• The rating and review count sit near the price, and reviews filter by the size or fit they mention, because fit comments answer the question behind "wrong size" returns.
• Images zoom to fabric and labels, because the photo stands in for handling the product.

The Federal Trade Commission (FTC) Rule on the Use of Consumer Reviews and Testimonials (16 CFR Part 465) bans fake reviews and review suppression, one of the payment, accessibility and review rules for online stores. Start both lists with your three best-sellers.

Which 12 checkout checks belong in an e-commerce UX audit?

The 12 checks fall into four groups (cost, account, form and trust), and the first asks whether shoppers see the total cost before the payment step.

Baymard's US survey of abandonment reasons sets aside the 42% who were only browsing. Among the rest, extra costs such as shipping, tax and fees led at 40%; distrust with card details reached 19%, a required account 18% and a long or complicated checkout 17%. Each group in the card answers one of those reasons.

Check 5 is a count: the same Baymard page puts the average US checkout at 14.88 form fields by default, against 7–8 in an ideal flow. Mark each check on a phone first, where mobile checkout typing hurts most. A checkout UX audit alone misses everyone who never reaches the cart, so the checklist covers search, listing and product pages as well.

The order confirmation page closes the checklist: it repeats the order number, delivery date and items, and offers the account from check 4 with a password field only. Support tickets tagged "where is my order" can point to a confirmation page or order email that leaves out the delivery date, so pull their count from your help desk before the audit.

How does an e-commerce UX audit cover mobile, speed and WCAG 2.2?

Mobile gets its own pass with its own GA4 numbers, speed is judged on Core Web Vitals field data, and every audited template is checked against WCAG 2.2 level AA.

Start from the device split: when the mobile conversion rate trails desktop, the mobile pass gets more hours for thumb reach, sticky bars over the size selector and field keyboards.

Google's web.dev guidance sets the Core Web Vitals thresholds for a good experience at a Largest Contentful Paint (LCP) of 2.5 seconds or less, an Interaction to Next Paint (INP) of 200 milliseconds or less and a Cumulative Layout Shift (CLS) of 0.1 or less, at the 75th percentile of page loads. In a store, INP is the lag after tapping a filter, a swatch or add to cart, so use PageSpeed Insights field data, not one lab run.

WCAG 2.2 level AA is the conformance level the audit uses. Of the criteria new in WCAG 2.2, Redundant Entry fails a billing form that asks again for the shipping address, and Accessible Authentication (Minimum) fails a login that depends on memorizing or retyping a code. The table maps five criteria to a store.

For the Americans with Disabilities Act (ADA), the Department of Justice says ADA Title III covers what businesses open to the public offer online, but it has no regulation setting detailed web standards, so WCAG 2.2 AA is the working benchmark. The European Accessibility Act has applied to e-commerce services for European Union (EU) consumers since 28 June 2025 under Directive (EU) 2019/882.

The audit checks templates, not every page, and fixes go into templates, never an overlay widget; a full-site accessibility audit is quoted separately. Tab through your checkout with a keyboard before the audit starts.

How do you score and rank e-commerce UX audit findings?

Multiply each finding's severity rating (1 to 4) by the share of affected sessions, divide by the effort estimate in development days, and fix the highest scores first.

Each issue gets a screenshot, a severity rating, a recommended fix and an effort estimate in design and development days. On our audits, two senior UX designers review independently, then merge findings. Affected sessions come from the funnel exploration: the share of all sessions that reach the page with the issue.

Illustrative, with invented inputs: a severity 3 shipping-cost surprise on a cart page reached by 12% of sessions scores 3 × 12 = 36, or 18 at 2 development days. A severity 4 gift-wrap bug met in 0.5% of sessions scores 4 × 0.5 = 2, or 2 at 1 day, so it waits. The 2×2 below turns scores into actions.

Each "fix this sprint" item becomes an A/B testing hypothesis. That ranked fix roadmap, with reach and effort in days, is what an expert audit hands over, and what a team scoring its own store struggles to calibrate. No reach column in your backlog yet? Add one before the next sprint.

What does a self-audit of your own store miss?

You can run this checklist yourselves, but a self-audit misses what your team stopped noticing: menu names, saved addresses, fast connections and catalog search terms.

• Category names: staff know where everything lives, so "Essentials" reads as clear to them and vague to shoppers.
• Logged-in sessions: saved addresses and cards hide the guest checkout path and its errors.
• Fast devices: a laptop on office Wi-Fi hides the INP and LCP delays of a mid-range phone on mobile data.
• Catalog vocabulary: staff search with product names and SKUs, so synonyms and misspellings never fail for them.
• No shared scale: two colleagues rate one issue 2 and 4, and the louder voice wins.

Independent evaluators close those gaps, because they bring neither your vocabulary nor your habits. Bring them in when findings will decide a redesign budget, or when cart abandonment rises while traffic and prices hold. Without funnel evidence, audit first, then redesign only the weakest templates.

What should you send to get an e-commerce UX audit quote?

Send your store URL with six scope inputs, from the store platform to any accessibility deadline, and an e-commerce UX audit can be priced at a fixed scope.

These six inputs set the audit scope:

• Store platform (Shopify, BigCommerce, Adobe Commerce or custom), because on a Shopify UX audit a recommended fix can then name the theme section, app or checkout setting it touches.
• Templates in scope (home, listing, product, cart, checkout, account), so the audit reviews templates, not every page.
• Devices, markets and languages, so the scope names which versions of the store get reviewed.
• GA4 access or a funnel export, so reach is scored from week one.
• Top 50 search queries and the zero-result list, so the search test uses your shoppers' words.
• Any accessibility deadline, such as EU sales under the European Accessibility Act, because it sets the depth of the WCAG check.

Our audit price is $5,000–$15,000 for an audit duration of 2–3 weeks, as published in the hub's comparison of a UX audit with e-commerce UX design. Redesigning the weakest templates afterwards is an e-commerce UX design engagement of $25,000–$60,000 over 4–8 weeks.

Every project begins with a free consultation and a fixed-scope proposal. For a smaller first look, a 45-minute UX audit session reviews your store and identifies the top three friction points. Either way, the scope starts from your own drop-off numbers: send us your store URL and platform and attach the funnel exploration.

After the first sprint of fixes, repeat the 60-second phone test on mobile data. Any stall it still finds goes to the top of the next audit scope.

FAQs