UXFixUXFix
Language
Audit my store
Toms logo

Toms

toms.com

We found 36 issues in Toms's cart, a modelled 15.8–47.8% of conversions.

Audit run by UXFix on 8 September 2026 against 115 rules. Every finding below is shown with the screen we captured, in the order they cost conversions. Nothing here was sponsored or reviewed by the store.

Audit by Abdulhameid Grandoka

Audit date
8 September 2026
Issues found
36
Est. conversion loss
15.8–47.8%
Rules run
115
AI Shoppers score
67/100
Overall checkout score
52/100
FDCBA

Grade D, at risk. Most points are lost on transparency and confidence.

Score breakdown by category

Each category is scored 0–100 from the rules that apply to it.

transparency
0

Cart shows full cost breakdown: items, shipping estimate, tax estimate. Shipping estimator (ZIP/country) available in cart. And 2 more.

confidence
21

Reviews present with summary rating visible above fold. Returns/exchange policy visible on PDP (not buried in footer). And 5 more.

forms
32

Total form fields 8 or fewer (industry average is 11.3). Address autocomplete (Google/Loqate) present. And 8 more.

trust
35

Delivery expectation shown before final purchase. Return policy summary or link visible in cart. And 3 more.

decision
58

Add-to-cart CTA above the fold on mobile. Sticky add-to-cart on long product pages. And 3 more.

How Toms compares

Across 24 audited stores, as of 8 September 2026. Method and full ranking: the UXFix ecommerce benchmark.

This store
52/100
Benchmark median
58/100
Benchmark mean
58.8/100
Rank
22 of 24

Scores above 9% of audited stores

What we checked

The same rule pass UXFix runs on every store. No store data and no analytics access — everything below was observable from the public storefront.

  1. 1
    A full purchase walk on desktop and mobile

    Product page to payment step, one real product, both viewports.

  2. 2
    Cost transparency at every step

    When shipping, tax and totals first become visible to the shopper.

  3. 3
    Form and field behaviour

    Field count, labels, autofill, error placement, recovery after a failed submit.

  4. 4
    Trust signals where money is entered

    Payment marks, security copy, returns and contact reachability at the pay step.

  5. 5
    Mobile ergonomics

    Tap target sizes, thumb reach, keyboard type, viewport zoom on focus.

  6. 6
    Machine readability

    Whether an AI shopping agent can read price, stock and shipping from the page.

What we could not check: 27 rules could not be judged from the public storefront on the date above. They were dropped from the score, not guessed at.

Results: 41 rules passed, 11 partial, 36 failed

115 rules were run. 27 could not be assessed and were dropped rather than guessed, leaving 88 scored. A further 3 findings are held back from this page because our wording for them was not fit to publish.

41 passing~11 partial36 failing?27 not assessable

What Toms does well

Rules already passing. No action needed on any of these.

  • Complete Product schema.org: price, availability, GTIN/SKU, rating, shipping details
  • Price and availability present in DOM as text (not JS/image only)
  • llms.txt present at root; product URLs not bot-blocked
  • Canonical URLs stable; variant URLs machine-readable and permanent
  • No session trap that breaks agent-driven cart hydration

Where it falls short

The issues, in the order they appear below.

  • Cart shows full cost breakdown: items, shipping estimate, tax estimate2–5.2%
  • Full total including shipping and tax visible before payment entry2–5.2%
  • Add-to-cart CTA above the fold on mobile0.8–2.1%
  • Reviews present with summary rating visible above fold0.8–2.1%
  • Returns/exchange policy visible on PDP (not buried in footer)0.8–2.1%
  • Shipping estimator (ZIP/country) available in cart0.8–2.1%
  • Tax shown or clearly labeled as calculated at checkout0.8–2.1%
  • Primary checkout CTA visually dominant on the page0.8–2.1%
Partial, worth a look

Right idea, wrong placement or timing: error messages specific and actionable ('Enter a valid postcode', not 'Invalid'), product description structured with scannable sections, not one blob and variant picker usable on small screens without accidental taps. And 8 more.

See the dollars leaking from your checkout.
Run a free audit →

Findings: 36 issues, ranked by estimated conversion loss

Each finding shows the screen as we captured it on 8 September 2026, what the problem is, and what it costs in conversions.

01CriticalCRT-001 · transparencyCart

Cart shows full cost breakdown: items, shipping estimate, tax estimate

We judged this on the live page but could not confirm this picture is of the same step, so we are not showing it.

CartCaptured Sep 8, 2026, 10:54 PM

The problem

The cart does not show a full cost breakdown. Some of subtotal, shipping, tax, or total is missing before checkout.

Why it matters

Baymard research: 48% of shoppers abandon at checkout because of surprise costs. If the cart hides shipping or tax until the final step, you are training buyers to bail.

Impact
2–5.2%
of checkouts, estimated
Fix effort
2h front-end
estimated
02CriticalCHK-031 · paymentCheckout

Full total including shipping and tax visible before payment entry

Desktop view. This is where the fix belongs.
Desktop view. This is where the fix belongs.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 10:54 PM

The problem

The full order total (including shipping and tax) isn't visible before the buyer starts entering payment details.

Why it matters

Surprise costs at the payment step are the #1 abandonment trigger in every study. Buyers want the final number before their card leaves the wallet.

Impact
2–5.2%
of checkouts, estimated
Fix effort
4h front-end
estimated
03HighPDP-002 · decisionProduct page

Add-to-cart CTA above the fold on mobile

Mobile view, zoomed to the issue location. Click to open the full screenshot.
Mobile view, zoomed to the issue location. Click to open the full screenshot.Product pagePhone view, 390pxCaptured Sep 8, 2026, 10:51 PM

The problem

The Add-to-Cart button is not visible above the fold on mobile. Shoppers have to scroll to find how to buy.

Why it matters

On mobile especially, buyers scan the top of the page and decide within seconds. If the primary purchase button isn't in that first view, many will leave before scrolling.

What to do

Add a sticky 'Ajouter au panier' button pinned to the bottom of the viewport (similar dark navy style as the 'Profiter de la remise' tab) so it's visible without scrolling past the size selector.

Impact
0.8–2.1%
of checkouts, estimated
Fix effort
2h front-end
estimated
04HighPDP-018 · confidenceProduct page

Reviews present with summary rating visible above fold

Desktop view. The pin marks where this belongs. Click to open the full screenshot.
Desktop view. The pin marks where this belongs. Click to open the full screenshot.Product pageDesktop view, 1440pxCaptured Sep 8, 2026, 10:51 PM

The problem

The product page shows no star rating or review summary above the fold. Shoppers have to scroll to find social proof.

Why it matters

Ratings are the fastest trust signal on a product page. A shopper who lands and doesn't see any social proof in the first view assumes it's a low-quality product or a new store.

What to do

Add a star rating with review count (e.g. '★★★★☆ 4.5 (238 avis)') directly beneath the 'Bottines à talon Elia' title and above the €135,00 price, matching TOMS' typical review widget placement so shoppers see social proof before scrolling.

Impact
0.8–2.1%
of checkouts, estimated
Fix effort
1h content
estimated
05HighPDP-022 · confidenceProduct page

Returns/exchange policy visible on PDP (not buried in footer)

Desktop view, zoomed to the issue location. Click to open the full screenshot.
Desktop view, zoomed to the issue location. Click to open the full screenshot.Product pageDesktop view, 1440pxCaptured Sep 8, 2026, 10:51 PM

The problem

There's no returns or exchange policy communicated on the product page itself. Shoppers have to hunt the footer or FAQ to find it.

Why it matters

"What if I don't like it?" is the last question in every purchase. If the answer isn't obvious, hesitation kills conversion, especially for higher-price items and apparel.

What to do

Add a short returns line (e.g. 'Free 30-day returns & exchanges') directly under the Klarna payment info box near the €135,00 price and size selector, similar to how the Klarna financing note is displayed, so shoppers see the policy before adding to cart.

Impact
0.8–2.1%
of checkouts, estimated
Fix effort
1h content
estimated
06HighCRT-002 · transparencyCart

Shipping estimator (ZIP/country) available in cart

We judged this on the live page but could not confirm this picture is of the same step, so we are not showing it.

CartCaptured Sep 8, 2026, 10:54 PM

The problem

The cart has no shipping estimator; shoppers can't preview shipping costs without starting checkout.

Why it matters

Unknown shipping costs are the single biggest cause of cart abandonment. An estimator answers the question before it becomes a reason to leave.

Impact
0.8–2.1%
of checkouts, estimated
Fix effort
2h front-end
estimated
07HighCRT-003 · transparencyCart

Tax shown or clearly labeled as calculated at checkout

We judged this on the live page but could not confirm this picture is of the same step, so we are not showing it.

CartCaptured Sep 8, 2026, 10:54 PM

The problem

The cart does not clearly show tax, either as an amount or as a note that tax will be calculated at checkout.

Why it matters

Buyers in the US and Canada expect a tax line before they commit. Silence at the cart step means a jump in the total at checkout, and that jump is what makes them abandon.

Impact
0.8–2.1%
of checkouts, estimated
Fix effort
2h front-end
estimated
08HighCRT-010 · momentumCart

Primary checkout CTA visually dominant on the page

We judged this on the live page but could not confirm this picture is of the same step, so we are not showing it.

CartCaptured Sep 8, 2026, 10:54 PM

The problem

The primary checkout button doesn't visually dominate the cart page. It competes for attention with promo-apply, save-for-later, or continue-shopping controls.

Why it matters

Cart is a decision moment. If the buyer's eye doesn't land on "Checkout" instantly, they scroll around, get distracted by promo hunting, and leave. Making the checkout CTA the biggest, brightest thing on the page measurably lifts completion.

What to do

Enlarge the 'Continuer' button and fill it with a solid, high-contrast color (e.g. TOMS navy or black) instead of the current thin outline, and add more padding so it clearly outweighs the 'Appliquer' promo code button and payment icons above it.

Impact
0.8–2.1%
of checkouts, estimated
Fix effort
4h front-end
estimated
09HighCHK-009 · formsCheckout

Total form fields 8 or fewer (industry average is 11.3)

Desktop view. The pin marks where this belongs. Click to open the full screenshot.
Desktop view. The pin marks where this belongs. Click to open the full screenshot.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 10:54 PM

The problem

The checkout has more than 8 form fields. Industry-best checkouts collect 6-8 fields; industry-average is 11.3.

Why it matters

Every extra field drops conversion by roughly 2%. Fields cost you money in a direct, measurable way. A checkout with 13 fields loses ~10% of buyers compared to one with 8.

Impact
0.8–2.1%
of checkouts, estimated
Fix effort
4h front-end
estimated
10HighCHK-012 · formsCheckout

Address autocomplete (Google/Loqate) present

Desktop view, zoomed to the issue location. Click to open the full screenshot.
Desktop view, zoomed to the issue location. Click to open the full screenshot.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 10:54 PM

The problem

The checkout has no address autocomplete (Google Places, Loqate, SmartyStreets, or similar). Shoppers type every line of their address manually.

Why it matters

Address autocomplete cuts address-entry time roughly in half on mobile and drops delivery-failure rates from typos. It also feels premium, buyers notice.

Impact
0.8–2.1%
of checkouts, estimated
Fix effort
4h front-end
estimated
11HighCHK-038 · trustCheckout

Delivery expectation shown before final purchase

Desktop view, zoomed to the issue location. Click to open the full screenshot.
Desktop view, zoomed to the issue location. Click to open the full screenshot.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 10:54 PM

The problem

The checkout page does not show when the order will arrive. Buyers commit to buying without knowing the delivery date.

Why it matters

Delivery timing is often the deciding factor between two stores. If your competitor tells the buyer "arrives Tuesday" and you say nothing, you lose. Especially for gifts.

Impact
0.8–2.1%
of checkouts, estimated
Fix effort
1h content
estimated
12HighCHK-A01 · agentAI Shoppers

Machine checkout readiness signals (ACP/UCP endpoints declared)

Desktop view. This is where the fix belongs.
Desktop view. This is where the fix belongs.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 10:54 PM

The problem

The checkout has no signals declaring it can be driven by AI agents. No ACP or UCP meta tags, no /.well-known/agentic-commerce endpoint, no Stripe ACP integration.

Why it matters

OpenAI's Agentic Commerce Protocol (ACP) and Google's Universal Commerce Protocol (UCP) are the emerging standards for agent-driven checkout. Stores that declare readiness get preferential routing from ChatGPT and Google AI. This is 2026's biggest new distribution channel.

Impact
0–2.1%
of checkouts, estimated
Fix effort
2h back-end
estimated
13HighCHK-015 · formsCheckout

Error messages specific and actionable ('Enter a valid postcode', not 'Invalid')

Desktop view. Highlighted area shows what we found.
Desktop view. Highlighted area shows what we found.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 10:54 PM

The problem

Error messages are generic ('Invalid', 'Error') instead of telling the buyer exactly what to fix.

Why it matters

A buyer who doesn't understand the error can't fix it. Specific messages ('Enter a valid postcode, e.g. 11937') turn dead-ends into quick corrections.

Impact
0.4–0.9%
of checkouts, estimated
Fix effort
4h front-end
estimated
14MediumPDP-003 · decisionProduct page

Sticky add-to-cart on long product pages

Desktop view. This is where the fix belongs.
Desktop view. This is where the fix belongs.Product pageDesktop view, 1440pxCaptured Sep 8, 2026, 10:51 PM

The problem

On this long product page, the Add-to-Cart button disappears once the shopper scrolls down. There is no sticky bar that keeps it reachable.

Why it matters

Shoppers scroll deep into reviews and details, decide to buy, and then have to scroll all the way back up. Every extra scroll is a chance to get distracted and leave.

Impact
0.2–0.7%
of checkouts, estimated
Fix effort
2h front-end
estimated
15MediumPDP-009 · decisionProduct page

Selected variant state unambiguous (visual + text confirmation)

Mobile view. This is where the fix belongs.
Mobile view. This is where the fix belongs.Product pagePhone view, 390pxCaptured Sep 8, 2026, 10:51 PMWe could not point at the exact spot on this page.

The problem

When a shopper selects a variant (size, color, style, or edition), the selected state isn't clearly indicated with both a visual highlight AND a text label.

Why it matters

Ambiguity here causes wrong-variant orders. The shopper thought they picked Large, actually picked Medium, and it costs you a return plus a lost repeat customer.

What to do

Add a visible selected-state ring or border around the chosen color swatch (currently both circles look identical with no highlight) and display the color name as text near 'Couleur:' (e.g. 'Couleur: Cuir Imperméable Noir' already exists but doesn't map to a highlighted swatch); also add a filled/bordered state to the size grid buttons to show which size, if any, is actively selected.

Impact
0.2–0.7%
of checkouts, estimated
Fix effort
2h front-end
estimated
16MediumPDP-015 · confidenceProduct page

Image zoom available on desktop and mobile

Desktop view. This is where the fix belongs.
Desktop view. This is where the fix belongs.Product pageDesktop view, 1440pxCaptured Sep 8, 2026, 10:51 PM

The problem

Clicking the product image doesn't open a zoom view. Shoppers can't inspect details, fabric, or quality up close.

Why it matters

Zoom is how online shoppers replace touching the product. Baymard finds inadequate image inspection among the top reasons for product-page abandonment.

Impact
0.2–0.7%
of checkouts, estimated
Fix effort
1h content
estimated
17MediumPDP-016 · confidenceProduct page

In-scale/lifestyle image included (product in real context)

Desktop view, zoomed to the issue location. Click to open the full screenshot.
Desktop view, zoomed to the issue location. Click to open the full screenshot.Product pageDesktop view, 1440pxCaptured Sep 8, 2026, 10:51 PM

The problem

The product gallery only shows the product isolated on a white background. No lifestyle, in-use, or scale reference images.

Why it matters

White-background photos are neutral but not persuasive. Lifestyle images (worn, used, in a real setting) lift conversion 30-50% and cut returns because buyers understand the product better.

What to do

Add at least one lifestyle photo showing the Elia boots worn on a model's feet/legs in a real setting (e.g. walking outdoors or styled with an outfit) to give scale and context, similar to how competitor shoe PDPs mix flat-lay and on-foot shots.

Impact
0.2–0.7%
of checkouts, estimated
Fix effort
1h content
estimated
18MediumPDP-021 · confidenceProduct page

Q&A section or complete specifications for considered purchases

Desktop view. The pin marks where this belongs. Click to open the full screenshot.
Desktop view. The pin marks where this belongs. Click to open the full screenshot.Product pageDesktop view, 1440pxCaptured Sep 8, 2026, 10:51 PM

The problem

The product page does not have a Q&A section or a real specifications table. Shoppers cannot answer their own questions before buying.

Why it matters

Considered purchases (electronics, appliances, tools, tech gear) live and die on the details page. When shoppers cannot find dimensions, materials, compatibility, or answers to obvious questions, they leave to research on Amazon or a competitor and often buy there instead.

Impact
0.2–0.7%
of checkouts, estimated
Fix effort
1h content
estimated
19MediumPDP-031 · mobileProduct page

Tap targets at least 44x44 px on all interactive elements

Mobile view. This is where the fix belongs.
Mobile view. This is where the fix belongs.Product pagePhone view, 390pxCaptured Sep 8, 2026, 10:51 PM

The problem

Some interactive elements on the mobile page are smaller than 44x44 pixels. Fingers struggle to hit them accurately.

Why it matters

44x44 pixels is the minimum touch target Apple and the WCAG 2.2 guidelines recommend. Below that, mis-taps happen: buyers hit the wrong swatch, wrong quantity, wrong link, and abandon in frustration.

Impact
0.2–0.7%
of checkouts, estimated
Fix effort
3h front-end
estimated
20MediumCRT-005 · transparencyCart

Delivery estimate for each item visible in cart

We judged this on the live page but could not confirm this picture is of the same step, so we are not showing it.

CartCaptured Sep 8, 2026, 10:54 PM

The problem

The cart does not show a delivery estimate for each item. Buyers cannot see when their order will arrive.

Why it matters

Delivery timing is the second-biggest factor after price, especially for gifts and urgent purchases. Uncertain arrival dates push buyers to competitors who are clear.

Impact
0.2–0.7%
of checkouts, estimated
Fix effort
2h front-end
estimated
21MediumCRT-012 · momentumCart

Express wallets do not visually compete with primary checkout CTA

We judged this on the live page but could not confirm this picture is of the same step, so we are not showing it.

CartCaptured Sep 8, 2026, 10:54 PM

The problem

Express wallet buttons (Apple Pay, Google Pay, Shop Pay, PayPal) are competing with the main Checkout button for the shopper's eye.

Why it matters

When every button looks equally important, the shopper hesitates. A clear primary CTA carries momentum through the cart into checkout.

What to do

Enlarge and color the 'Continuer' button (currently a plain dark rectangle similar in size to the wallet icon row) to be visually dominant—e.g. use TOMS' signature dark navy with more padding—and add a clear 'ou payez avec' divider text above the row of Apple Pay/Maestro/Mastercard/PayPal/Shop/Visa icons so they read as secondary alternatives rather than equal options.

Impact
0.2–0.7%
of checkouts, estimated
Fix effort
4h front-end
estimated
22MediumCRT-015 · momentumCart

Save-for-later distinct from Remove (recovery preserved)

We judged this on the live page but could not confirm this picture is of the same step, so we are not showing it.

CartCaptured Sep 8, 2026, 10:54 PM

The problem

The cart only offers a "Remove" action. There is no "Save for later" or "Move to wishlist" option to hold the item without buying today.

Why it matters

A shopper who is not ready to buy today but likes an item will either remove it (and forget) or leave the tab open (and forget). Either way you lose the sale. A save-for-later button captures that intent.

Impact
0.2–0.7%
of checkouts, estimated
Fix effort
4h front-end
estimated
23MediumCRT-019 · trustCart

Return policy summary or link visible in cart

We judged this on the live page but could not confirm this picture is of the same step, so we are not showing it.

CartCaptured Sep 8, 2026, 10:54 PM

The problem

The cart doesn't mention or link the returns policy. Shoppers who care about returns have to hunt in the footer or checkout.

Why it matters

Returns confidence is a last-mile confidence signal. A quick "Free 30-day returns" line on the cart removes the last reason to bail.

What to do

Add a small 'Retours gratuits sous 30 jours' line with a link to the Retours policy directly under the 'Estimated Total' row in the cart panel, similar to how the Klarna installment line is shown, so shoppers see it before checkout.

Impact
0.2–0.7%
of checkouts, estimated
Fix effort
1h content
estimated
24MediumCHK-003 · structureCheckout

Clear step indicator showing progress through checkout

Desktop view, zoomed to the issue location. Click to open the full screenshot.
Desktop view, zoomed to the issue location. Click to open the full screenshot.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 10:54 PM

The problem

The checkout doesn't show which step the buyer is on or how many steps remain. It feels like an infinite form.

Why it matters

Not knowing how long a task will take is one of the strongest predictors of abandonment. A visible "Step 2 of 3" gives buyers the confidence to push through the next 30 seconds of typing.

What to do

Add a simple breadcrumb bar under the TOMS logo (e.g. 'Informatie > Verzending > Betaling') with the current step in bold navy to match the site's color scheme, so shoppers know they're on step 1 of 3 before payment.

Impact
0.2–0.7%
of checkouts, estimated
Fix effort
4h front-end
estimated
25MediumCHK-007 · structureCheckout

Site logo/name does not link away from checkout (or warns first)

Desktop view. This is where the fix belongs.
Desktop view. This is where the fix belongs.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 10:54 PM

The problem

The store logo in the checkout header links straight back to the homepage.

Why it matters

A stray click on the logo dumps the buyer out of checkout, and on some stores it also loses the form data. Small leak, easy fix.

Impact
0.2–0.7%
of checkouts, estimated
Fix effort
4h front-end
estimated
26MediumCHK-010 · formsCheckout

Single Full Name field (not first + last)

Desktop view, zoomed to the issue location. Click to open the full screenshot.
Desktop view, zoomed to the issue location. Click to open the full screenshot.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 10:54 PM

The problem

The checkout uses separate First Name and Last Name fields instead of a single Full Name field.

Why it matters

Two fields cost two taps and two keyboard focuses on mobile. Baymard research shows a single Full Name field measurably lifts checkout completion, especially on phones.

Impact
0.2–0.7%
of checkouts, estimated
Fix effort
4h front-end
estimated
27MediumCHK-011 · formsCheckout

Optional fields marked as optional (not required by default)

Desktop view. The pin marks where this belongs. Click to open the full screenshot.
Desktop view. The pin marks where this belongs. Click to open the full screenshot.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 10:54 PM

The problem

Optional fields on the checkout are not visibly labeled as optional. Shoppers assume everything is required.

Why it matters

Labeling only the required fields (with a *, say) means every unmarked field looks equally required. Buyers fill in fields they did not need to, or bail because they think they must supply a company name they do not have.

Impact
0.2–0.7%
of checkouts, estimated
Fix effort
4h front-end
estimated
28MediumCHK-019 · formsCheckout

Autocomplete attributes set correctly (given-name, family-name, cc-number, etc.)

Desktop view, zoomed to the issue location. Click to open the full screenshot.
Desktop view, zoomed to the issue location. Click to open the full screenshot.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 10:54 PM

The problem

Personal-info fields are missing correct `autocomplete` attributes, or one is set to `autocomplete="off"`. Password managers and browser autofill do not work smoothly.

Why it matters

WCAG 2.2 requires autocomplete on personal-info fields for accessibility. Beyond compliance, correct autocomplete makes checkout a 2-tap experience for returning buyers, huge for mobile conversion.

Impact
0.2–0.7%
of checkouts, estimated
Fix effort
4h front-end
estimated
29MediumCHK-020 · formsCheckout

Ship-to same as billing offered as default

Desktop view, zoomed to the issue location. Click to open the full screenshot.
Desktop view, zoomed to the issue location. Click to open the full screenshot.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 10:54 PM

The problem

The checkout does not offer a "Same as shipping" checkbox for the billing address, with the box checked by default. Buyers have to type their address twice. (This rule only applies to physical-product stores.)

Why it matters

For most orders, billing and shipping addresses are the same. Making the buyer re-enter their address is duplicate work and a common source of typos.

Impact
0.2–0.7%
of checkouts, estimated
Fix effort
4h front-end
estimated
30MediumCHK-021 · formsCheckout

Phone number field explains why it is needed (or is optional)

Desktop view, zoomed to the issue location. Click to open the full screenshot.
Desktop view, zoomed to the issue location. Click to open the full screenshot.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 10:54 PM

The problem

The phone number field is required with no explanation why. Buyers who value their privacy hesitate or abandon.

Why it matters

"Why does a t-shirt store need my phone number?" is a real objection. Without a rationale, some shoppers will not give it and will leave.

Impact
0.2–0.7%
of checkouts, estimated
Fix effort
4h front-end
estimated
31MediumCHK-024 · formsCheckout

Form labels visible above fields (not placeholder-only)

Desktop view, zoomed to the issue location. Click to open the full screenshot.
Desktop view, zoomed to the issue location. Click to open the full screenshot.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 10:54 PM

The problem

The checkout form uses placeholder-only labels: the field's purpose is shown as grey text inside the input, and disappears the moment the buyer starts typing.

Why it matters

Placeholder-only labels violate WCAG accessibility, but they also just cost sales. A buyer who types a wrong value, then forgets what the field was for, has to erase everything to see the label again. Frustration compounds.

What to do

Add small persistent labels (e.g. 'Voornaam', 'Adres', 'Postcode') above each input field in the Bezorging and Betaling sections, similar to the 'Land/regio' field which already shows a label above the dropdown, so the field purpose remains visible once the buyer starts typing.

Impact
0.2–0.7%
of checkouts, estimated
Fix effort
4h front-end
estimated
32MediumCHK-035 · trustCheckout

Trust/security signals visible near payment step

Desktop view. The pin marks where this belongs. Click to open the full screenshot.
Desktop view. The pin marks where this belongs. Click to open the full screenshot.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 10:54 PM

The problem

The payment step doesn't show any trust or security signals near the payment fields (padlock icon, "Secure checkout", PCI badge, Verified by Visa).

Why it matters

Buyers are at their most anxious when typing card numbers. A visible security signal near the field removes that anxiety and lifts conversion.

What to do

Add a small lock icon with 'Beveiligde checkout' text directly above or beside the 'shop'/PayPal buttons at the top of the form, and consider adding SSL/PCI badges near the order summary total (€140,00) on the right panel to reassure users before they enter address/payment details.

Impact
0.2–0.7%
of checkouts, estimated
Fix effort
1h content
estimated
33MediumCHK-040 · mobileCheckout

Payment form supports mobile browser autofill for card details

Mobile view, zoomed to the issue location. Click to open the full screenshot.
Mobile view, zoomed to the issue location. Click to open the full screenshot.Checkout, first stepPhone view, 390pxCaptured Sep 8, 2026, 10:54 PM

The problem

The card-payment form is missing the `autocomplete` attributes mobile browsers need to autofill saved cards.

Why it matters

iOS and Android can autofill a saved card in one tap when the fields are labeled correctly. Without it, the buyer types 16 digits, expiry, and CVV manually, and many abandon.

Impact
0.2–0.7%
of checkouts, estimated
Fix effort
3h front-end
estimated
34MediumCHK-A04 · agentAI Shoppers

Delegated-payment compatibility signals present (tokenization endpoints)

Desktop view. This is where the fix belongs.
Desktop view. This is where the fix belongs.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 10:54 PM

The problem

The checkout does not declare support for delegated-payment (ACP tokenization). Agents cannot pass a tokenized payment method on the buyer's behalf.

Why it matters

Delegated-payment is the piece that actually lets agents complete a purchase without asking the buyer to type their card. Stripe and PayPal both support this via their ACP modes. Without it, agents can prep the order but hand it back to the buyer to finalize.

Impact
0–0.7%
of checkouts, estimated
Fix effort
2h back-end
estimated
35LowPDP-013 · decisionProduct page

Quantity selector present and easy to use (tap-friendly on mobile)

Mobile view. This is where the fix belongs.
Mobile view. This is where the fix belongs.Product pagePhone view, 390pxCaptured Sep 8, 2026, 10:51 PMWe could not point at the exact spot on this page.

The problem

The quantity selector on this product page is either missing on mobile, or too small to tap comfortably.

Why it matters

Fat-finger errors turn quick purchases into frustrating ones. Apple's tap-target guideline is 44px minimum; anything smaller mistaps often on real thumbs.

What to do

Add a quantity stepper (- / input / +) with buttons at least 44x44px, placed directly above or beside the 'Sélectionnez une taille' button so shoppers can select multiple pairs before adding to cart.

Impact
0.1–0.4%
of checkouts, estimated
Fix effort
2h front-end
estimated
36LowCHK-042 · mobileCheckout

No layout jumps when form errors appear

Mobile view. This is where the fix belongs.
Mobile view. This is where the fix belongs.Checkout, first stepPhone view, 390pxCaptured Sep 8, 2026, 10:54 PM

The problem

When an error message appears, the form visibly jumps, moving fields under the buyer's cursor or thumb.

Why it matters

Layout jumps cause mis-clicks and lose the buyer's place in the form. On mobile they routinely cause wrong-field input.

Impact
0.1–0.4%
of checkouts, estimated
Fix effort
3h front-end
estimated
AI ShoppersHow the store performs for AI shopping agents and AI search

An AI assistant can find Toms. It cannot complete a purchase there.

UXFix scores every store twice: once for human shoppers, once for the agents now doing the browsing on their behalf. Toms scores 52 for humans and 67 for agents. 4 of the 12 agent rules are not fully met.

AI Shoppers score
67/100
AI search visibility
4of 8

Derived from this store's own captured product-page content. Coverage judges whether that content answers each query — it is not a measurement of search volume or of what any AI currently recommends.

What an agent could read
Complete Product schema.org: price, availability, GTIN/SKU, rating, shipping detailsPDP-A01
Price and availability present in DOM as text (not JS/image only)PDP-A02
llms.txt present at root; product URLs not bot-blockedPDP-A03
Canonical URLs stable; variant URLs machine-readable and permanentPDP-A04
No session trap that breaks agent-driven cart hydrationCRT-A02
Cart line items include machine-readable product IDs/GTINsCRT-A03
No CAPTCHA-only gate without accessible agent pathCHK-A02
What it could not
Machine checkout readiness signals (ACP/UCP endpoints declared)CHK-A01
Delegated-payment compatibility signals present (tokenization endpoints)CHK-A04
Structured errors returned in machine-readable format for agent flowsCHK-A05
~Cart state reachable via stable URL or API endpointCRT-A01
AI search results we ran
What are good waterproof ankle boots for women to wear in rain and snow?
Covered"conçue pour affronter la pluie et la neige"
Does TOMS offer vegan shoe options?
PartialNav lists "Végan" category but this product page describes leather uppers only
What are good gift ideas for her from TOMS?
PartialNav has "Cadeaux pour elle" link but product page has no gifting language
How does buying TOMS shoes support social causes?
Covered"Chaque achat TOMS soutient l’éducation, la santé et le bien-être des enfants"
How do I find my correct EU shoe size when buying TOMS boots?
CoveredSize guide table with US/CA, UK, EU, JP and foot length conversions
Are TOMS boots sustainably or ethically made?
Covered"Leather Working Group" and "fièrement certifiés B Corp™"
How do TOMS Elia ankle boots compare to other waterproof boots on the market?
MissingNo competitor or comparative material/performance data present
What are comfortable heeled boots for everyday winter wear?
Partial"Semelle CloudBound™... ultra confort" but no mention of everyday styling or outfit versatility

Questions this audit answers

What is Toms's UX audit score?

Toms (toms.com) scored 52/100 on 8 September 2026 in UXFix's independent audit of its product page, cart and checkout, judged on 88 of the 115 rules run.

What are the biggest UX issues on toms.com?

The audit found 36 failing checks. The costliest: cart shows full cost breakdown: items, shipping estimate, tax estimate, full total including shipping and tax visible before payment entry and add-to-cart CTA above the fold on mobile.

Can AI shopping agents read Toms's store?

Toms scores 67/100 on UXFix's AI Shoppers rules, which test whether an AI agent can read price, stock and shipping from the store and complete a purchase there.

How was this audit conducted?

UXFix ran the same 115 deterministic rules it runs on every store: a full purchase walk on desktop and mobile, from product page to payment step, using only the public storefront. No store data or analytics access was used, and every finding is shown with the captured screen.

How does Toms compare with other audited stores?

Against 24 scored stores in the UXFix benchmark, Toms ranks 22 with 52/100. The benchmark median is 58. As of 8 September 2026.

Conclusion

Toms is not a badly built store. It passes 41 of 88 assessable rules. What it has is a band of friction between the product page and the payment step, and every part of it is named above.

The 36 findings above come to roughly 99 developer hours of estimated effort in total. Most are settings or template changes rather than rebuilds. A further 11 rules are only partly met and worth a look after these.

The pattern repeats across the stores we audit: the score is rarely lost on visual design, and it is rarely lost in one place. It is lost on when the cost appears, how many decisions stand between a shopper and paying, and whether a machine can read any of it.

If they fix three things
  1. Cart shows full cost breakdown: items, shipping estimate, tax estimate 2h front-end
  2. Full total including shipping and tax visible before payment entry 4h front-end
  3. Add-to-cart CTA above the fold on mobile 2h front-end
Now
52
Projected
61

Modelled, not measured. We re-audit for free to check.

Get your store audited

The same rules, the same evidence, the same estimates, on your product page, cart and checkout. Free, no card, about two minutes.

Cite or embed this audit

Quote the score with its date, or embed the live badge. The badge links back to this page and stays current if we re-audit.

Citation
UXFix (2026). Toms UX and conversion audit: 52/100. Audited 8 September 2026. https://uxfix.ai/audits/toms-com
Embed snippet
<a href="https://uxfix.ai/audits/toms-com"><img src="https://uxfix.ai/audits/toms-com/badge.svg" alt="UXFix score: Toms 52/100" width="220" height="48" /></a>

More case studies

Recent audits from the same benchmark corpus.

Wpfactory
wpfactory.com
70/100
Citstores
citstores.com
65/100
Ladoun
ladoun.com
41/100

Disclaimer

This is an independent audit. It was not sponsored, commissioned, paid for or reviewed by Toms, and UXFix has no commercial relationship with the store. Findings were produced from the public storefront on 8 September 2026 and may no longer reflect the live site. Conversion figures are estimates modelled from published abandonment research, not from the store's own analytics. Store name and screens are used for commentary and comparison. If you work at Toms and would like this page corrected or removed, email [email protected].

Findings reflect toms.com as captured on 8 September 2026. Stores change; if something here no longer matches the live site, email [email protected] and we will re-check and republish.

All case studiesArticlesPricingRead the full methodology