We found 40 issues in Reebok's product page, a modelled 15.3–47.9% 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.
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
A full purchase walk on desktop and mobile
Product page to payment step, one real product, both viewports.
2
Cost transparency at every step
When shipping, tax and totals first become visible to the shopper.
3
Form and field behaviour
Field count, labels, autofill, error placement, recovery after a failed submit.
4
Trust signals where money is entered
Payment marks, security copy, returns and contact reachability at the pay step.
5
Mobile ergonomics
Tap target sizes, thumb reach, keyboard type, viewport zoom on focus.
6
Machine readability
Whether an AI shopping agent can read price, stock and shipping from the page.
What we could not check: 21 rules could not be judged from the public storefront on the date above. They were dropped from the score, not guessed at.
Results: 44 rules passed, 15 partial, 35 failed
115 rules were run. 21 could not be assessed and were dropped rather than guessed, leaving 94 scored. A further 3 findings are held back from this page because our wording for them was not fit to publish.
✓44 passing~15 partial✗35 failing?21 not assessable
What Reebok does well
Rules already passing. No action needed on any of these.
✓
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
✓
Guest checkout offered as first-class option (no account wall)
Where it falls short
The issues, in the order they appear below.
✕Price visible without scroll or interaction on desktop and mobile0.9–2.3%
✕Cart shows full cost breakdown: items, shipping estimate, tax estimate0.9–2.3%
✕Full total including shipping and tax visible before payment entry0.9–2.3%
✕Add-to-cart CTA above the fold on mobile0.8–2.1%
✕Delivery/arrival date estimate shown0.8–2.1%
✕No aggressive popup covering PDP within first 10 seconds0.8–2.1%
✕Largest Contentful Paint under 2.5s on mobile0.8–2.1%
✕Shipping estimator (ZIP/country) available in cart0.8–2.1%
Partial, worth a look
Right idea, wrong placement or timing: price visible without scroll or interaction on desktop and mobile, cart shows full cost breakdown: items, shipping estimate, tax estimate and full total including shipping and tax visible before payment entry. And 12 more.
AI Shoppers
AI shopping agents already visit your store. Can they buy?
Findings: 40 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.
01CriticalPDP-001 · decisionProduct page
Price visible without scroll or interaction on desktop and mobile
Mobile view (only what shoppers see before scrolling). Highlighted area shows what we found.Product pagePhone view, 390pxCaptured Sep 8, 2026, 9:46 PMWe could not point at the exact spot on this page.
The problem
The product price is not visible above the fold on desktop or on mobile. Shoppers have to scroll to find out what the product costs.
Why it matters
Price is the single strongest predictor of whether a shopper stays or bounces. If they can't see it in the first second, they're gone. This is the highest-impact fix on any product page.
Impact
0.9–2.3%
of checkouts, estimated
Fix effort
2h front-end
estimated
02CriticalCRT-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, 9:51 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
0.9–2.3%
of checkouts, estimated
Fix effort
2h front-end
estimated
03CriticalCHK-031 · paymentCheckout
Full total including shipping and tax visible before payment entry
Desktop view. Highlighted area shows what we found.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 9:52 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
0.9–2.3%
of checkouts, estimated
Fix effort
4h front-end
estimated
04HighPDP-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.Product pagePhone view, 390pxCaptured Sep 8, 2026, 9:46 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
Remove or minimize the country-redirect modal ('Looks like you are visiting from France...') so it doesn't block content, and ensure the 'Add to Cart'/'Add to Bag' button is placed directly below the size selector (currently cut off at the bottom near the cookie banner) so it's visible without scrolling.
Impact
0.8–2.1%
of checkouts, estimated
Fix effort
2h front-end
estimated
05HighPDP-005 · decisionProduct page
Delivery/arrival date estimate shown
Desktop view. The pin marks where this belongs. Click to open the full screenshot.Product pageDesktop view, 1440pxCaptured Sep 8, 2026, 9:46 PM
The problem
The product page doesn't tell shoppers when their order will arrive. There is no delivery date or lead-time estimate.
Why it matters
Buyers often decide between two stores based on delivery timing, especially for gifts and urgent purchases. Uncertain timing pushes them to competitors who are clear.
Impact
0.8–2.1%
of checkouts, estimated
Fix effort
2h front-end
estimated
06HighPDP-029 · frictionProduct page
No aggressive popup covering PDP within first 10 seconds
Desktop view, zoomed to the issue location. Click to open the full screenshot.Product pageDesktop view, 1440pxCaptured Sep 8, 2026, 9:46 PM
The problem
An aggressive popup (newsletter, discount, chat prompt) covers this product page shortly after it loads. Cookie banners don't count; this is the newsletter-style overlay.
Why it matters
Popups on first visit interrupt intent. First-time shoppers are still evaluating; a modal that blocks the price or ATC is a fast way to lose them.
What to do
Reduce the geo-redirect modal to a small dismissible top banner or corner toast instead of a centered 300px-wide modal with dark overlay, so the DMX Series 3000 product title, price, and Add to Cart button remain visible on load; also add a visible close behavior default (auto-dismiss after selection) rather than requiring the shopper to click the X or a flag button first.
Impact
0.8–2.1%
of checkouts, estimated
Fix effort
4h front-end
estimated
07HighPDP-033 · mobileProduct page
Largest Contentful Paint under 2.5s on mobile
Mobile view. This is where the fix belongs.Product pagePhone view, 390pxCaptured Sep 8, 2026, 9:46 PM
The problem
The main content of the product page takes longer than 2.5 seconds to appear ("Largest Contentful Paint" is slow).
Why it matters
Every extra second of load time drops conversion by ~7% (Google, 2024). 2.5s is Google's threshold for a good experience. Above 4s is considered poor and hurts search rankings too.
Impact
0.8–2.1%
of checkouts, estimated
Fix effort
3h front-end
estimated
08HighCRT-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, 9:51 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
09HighCRT-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, 9:51 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
10HighCRT-011 · momentumCart
Express wallet options (Apple/Google/Shop Pay) present 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, 9:51 PM
The problem
The cart doesn't offer any express wallet button (Apple Pay, Google Pay, Shop Pay, PayPal Express).
Why it matters
Express wallets skip 60-80% of the checkout form. Shop Pay alone lifts checkout completion by ~1.7x. On mobile especially, one tap vs six form fields is the biggest single conversion lever left in ecommerce.
What to do
Add branded express checkout buttons (e.g., Apple Pay black button, PayPal blue/yellow button, Shop Pay purple button) directly above or below the black 'CHECKOUT • $100' button so returning customers can skip manual form entry.
Impact
0.8–2.1%
of checkouts, estimated
Fix effort
4h front-end
estimated
11HighCHK-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.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 9:52 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
12HighCHK-012 · formsCheckout
Address autocomplete (Google/Loqate) present
Desktop view, zoomed to the issue location. Click to open the full screenshot.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 9:52 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
13HighCHK-038 · trustCheckout
Delivery expectation shown before final purchase
Desktop view, zoomed to the issue location. Click to open the full screenshot.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 9:52 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.
Desktop view. This is where the fix belongs.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 9:52 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
15HighPDP-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.Product pageDesktop view, 1440pxCaptured Sep 8, 2026, 9:46 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 inline snippet like 'Free 30-day returns' directly under the Add to Cart button (near the Klarna financing text at y~0.373) so shoppers see the policy without expanding the 'Shipping & Returns' accordion at y~0.427.
Impact
0.4–0.9%
of checkouts, estimated
Fix effort
1h content
estimated
16HighCRT-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, 9:51 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
The black 'CHECKOUT WITH MEMBERSHIP' button and grey 'CHECKOUT • $100' button are nearly identical in size and weight, causing the shopper to pause between two similarly-styled CTAs; make the primary 'CHECKOUT • $100' button solid black or brand red and visually shrink or restyle the membership upsell button as a secondary link so there's one clear dominant action.
The structured product data that AI shopping agents read (ChatGPT, Google, Copilot) is incomplete on this page. Some or all of these are missing: product ID (GTIN), brand, review data, availability, shipping details.
Why it matters
AI-referred traffic converts 42% higher than regular traffic (Adobe, 2026). But agents only recommend stores whose product data they can read. Incomplete data means invisible to AI shoppers.
Impact
0–0.9%
of checkouts, estimated
Fix effort
2h back-end
estimated
18MediumPDP-003 · decisionProduct page
Sticky add-to-cart on long product pages
Desktop view. This is where the fix belongs.Product pageDesktop view, 1440pxCaptured Sep 8, 2026, 9:46 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
19MediumPDP-015 · confidenceProduct page
Image zoom available on desktop and mobile
Desktop view. This is where the fix belongs.Product pageDesktop view, 1440pxCaptured Sep 8, 2026, 9:46 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
20MediumPDP-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.Product pageDesktop view, 1440pxCaptured Sep 8, 2026, 9:46 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 DMX Series 3000 being worn (e.g., on a model's feet in an outdoor or gym setting) among the current six thumbnail views, since all existing shots are studio product-only images against white/gray backdrops.
Impact
0.2–0.7%
of checkouts, estimated
Fix effort
1h content
estimated
21MediumPDP-031 · mobileProduct page
Tap targets at least 44x44 px on all interactive elements
Mobile view. This is where the fix belongs.Product pagePhone view, 390pxCaptured Sep 8, 2026, 9:46 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.
Content on the product page moves around while it loads ("layout shift"). Buyers try to tap a button and it jumps.
Why it matters
Layout shift is one of Google's Core Web Vitals. Beyond the SEO hit, it is deeply frustrating on mobile: you go to tap Add to Cart, an image loads above it, the button jumps down, and you tap something else instead.
Impact
0.2–0.7%
of checkouts, estimated
Fix effort
3h front-end
estimated
23MediumCRT-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, 9:51 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
24MediumCRT-006 · transparencyCart
Discount/promo application shows explicit line item, not silent adjustment
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, 9:51 PM
The problem
A discount has been applied but there is no explicit line showing the discount amount and label. The saving happens silently.
Why it matters
Buyers who applied a code want to see it working. A silent adjustment feels like the code did not work, and they may re-apply, try a different code, or abandon in frustration.
Impact
0.2–0.7%
of checkouts, estimated
Fix effort
2h front-end
estimated
25MediumCRT-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, 9:51 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
26MediumCRT-022 · mobileCart
Cart usable on mobile without horizontal scroll
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, 9:51 PM
The problem
The cart page is broken on mobile: content overflows the viewport, requires horizontal scrolling, or has buttons that fall off the screen.
Why it matters
More than 60% of ecommerce traffic is mobile. A cart that requires horizontal scrolling doesn't lose 60% of buyers, it loses closer to 90% of the mobile ones. This is fatal and easy to check with a phone.
Impact
0.2–0.7%
of checkouts, estimated
Fix effort
3h front-end
estimated
27MediumCHK-003 · structureCheckout
Clear step indicator showing progress through checkout
Desktop view, zoomed to the issue location. Click to open the full screenshot.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 9:52 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 horizontal step indicator at the top of the page (below the Reebok logo) such as 'Contact → Delivery → Payment → Review' with the current step (Delivery) bolded or highlighted in Reebok red, so users know how many steps remain.
Impact
0.2–0.7%
of checkouts, estimated
Fix effort
4h front-end
estimated
28MediumCHK-007 · structureCheckout
Site logo/name does not link away from checkout (or warns first)
Desktop view. This is where the fix belongs.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 9:52 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
29MediumCHK-010 · formsCheckout
Single Full Name field (not first + last)
Desktop view, zoomed to the issue location. Click to open the full screenshot.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 9:52 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
30MediumCHK-018 · formsCheckout
Correct HTML input types (email, tel, number) for mobile keyboards
Mobile view, zoomed to the issue location. Click to open the full screenshot.Checkout, first stepPhone view, 390pxCaptured Sep 8, 2026, 9:52 PM
The problem
Some input fields use `type="text"` when they should use `type="email"`, `type="tel"`, or `inputmode="numeric"`. Mobile keyboards do not adapt.
Why it matters
The wrong keyboard is a small papercut on every entry. Type an email on a phone with a QWERTY (no @ key) or a phone number without the number pad, and completion drops.
Impact
0.2–0.7%
of checkouts, estimated
Fix effort
4h front-end
estimated
31MediumCHK-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.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 9:52 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
32MediumCHK-020 · formsCheckout
Ship-to same as billing offered as default
Desktop view, zoomed to the issue location. Click to open the full screenshot.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 9:52 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
33MediumCHK-024 · formsCheckout
Form labels visible above fields (not placeholder-only)
Desktop view, zoomed to the issue location. Click to open the full screenshot.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 9:52 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. 'First name', 'Last name') above the input boxes at coordinates near y=0.49-0.55, similar to how 'Country/Region' and 'Shipping method' have static labels, so the field purpose stays visible once text like 'John' is typed into the placeholder-only First/Last name boxes.
Impact
0.2–0.7%
of checkouts, estimated
Fix effort
4h front-end
estimated
34MediumCHK-035 · trustCheckout
Trust/security signals visible near payment step
Desktop view. The pin marks where this belongs. Click to open the full screenshot.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 9:52 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 padlock icon with 'Secure Checkout' text directly above the Contact email field (near the Shop Pay button at y~0.37) so users see trust cues before entering personal and payment info, not just in the footer legal text.
Impact
0.2–0.7%
of checkouts, estimated
Fix effort
1h content
estimated
35MediumCHK-040 · mobileCheckout
Payment form supports mobile browser autofill for card details
Mobile view, zoomed to the issue location. Click to open the full screenshot.Checkout, first stepPhone view, 390pxCaptured Sep 8, 2026, 9:52 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
36MediumCHK-A02 · agentAI Shoppers
No CAPTCHA-only gate without accessible agent path
Desktop view. This is where the fix belongs.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 9:52 PM
The problem
The checkout uses a CAPTCHA (reCAPTCHA, hCaptcha, Cloudflare Turnstile) with no agent-bypass path. Automated agents cannot complete checkout.
Why it matters
CAPTCHAs are designed to block bots, but they also block legitimate AI shopping agents that buyers explicitly delegate to. Without an agent-token bypass, you cannot participate in agentic commerce even if you want to.
Desktop view. This is where the fix belongs.Checkout, first stepDesktop view, 1440pxCaptured Sep 8, 2026, 9:52 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
38LowPDP-013 · decisionProduct page
Quantity selector present and easy to use (tap-friendly on mobile)
Mobile view. This is where the fix belongs.Product pagePhone view, 390pxCaptured Sep 8, 2026, 9:46 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 compact quantity stepper (minus/number/plus, each ~44px tall) directly above or beside the black 'Add to Cart - $130' button, similar in style to the size grid so shoppers can order multiple pairs without leaving the page.
Impact
0.1–0.4%
of checkouts, estimated
Fix effort
2h front-end
estimated
39LowCRT-A03 · agentAI Shoppers
Cart line items include machine-readable product IDs/GTINs
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, 9:51 PM
The problem
Cart line items do not include machine-readable product identifiers (SKU, GTIN, product_id). Agents see only display names.
Why it matters
Without a stable identifier per line, agents cannot cross-check items against a catalog, apply price rules, or reconcile the order. Display names change with translation and localization, they are not safe identifiers.
Impact
0–0.4%
of checkouts, estimated
Fix effort
2h back-end
estimated
40LowCHK-042 · mobileCheckout
No layout jumps when form errors appear
Mobile view. This is where the fix belongs.Checkout, first stepPhone view, 390pxCaptured Sep 8, 2026, 9:52 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 Reebok. 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. Reebok scores 57 for humans and 48 for agents. The gap is the part most stores have not looked at yet. 7 of the 12 agent rules are not fully met.
AI Shoppers score
48/100
AI search visibility
3of 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
✓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
“What training shoes does Reebok recommend for F45 workouts?”
PartialF45 Training | Reebok Explore listed in navigation
Questions this audit answers
What is Reebok's UX audit score?
Reebok (reebok.com) scored 57/100 on 8 September 2026 in UXFix's independent audit of its product page, cart and checkout, judged on 94 of the 115 rules run.
What are the biggest UX issues on reebok.com?
The audit found 35 failing checks. The costliest: price visible without scroll or interaction on desktop and mobile, cart shows full cost breakdown: items, shipping estimate, tax estimate and full total including shipping and tax visible before payment entry.
Can AI shopping agents read Reebok's store?
Reebok scores 48/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 Reebok compare with other audited stores?
Against 25 scored stores in the UXFix benchmark, Reebok ranks 15 with 57/100. The benchmark median is 58. As of 8 September 2026.
Conclusion
Reebok is not a badly built store. It passes 44 of 94 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 40 findings above come to roughly 114 developer hours of estimated effort in total. Most are settings or template changes rather than rebuilds. A further 15 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
Price visible without scroll or interaction on desktop and mobile — 2h front-end