We found 41 issues in Gymshark's checkout, a modelled 16.7–52.9% of conversions.

The problem

When the checkout form has an error, the store clears out information the shopper already typed correctly.

Why it matters

A shopper who typed their address once and lost it to a form error frequently will not type it twice. This is a critical-severity leak at the very end of the funnel, where every lost buyer was seconds from paying.

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.

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.

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.

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

Dismiss or resolve the 'Cookies' modal and the 'ARE YOU IN THE RIGHT PLACE?' region popup before the product content and 'Add to Bag' button can be reached; consider combining these into a single lightweight consent bar so shoppers can see the product and purchase CTA immediately.

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.

The problem

When a size or color is unavailable, the option still looks selectable. Shoppers only find out it cannot be bought when the add-to-cart step rejects them.

Why it matters

Letting someone pick an option and then failing them is one of the most frustrating patterns in variant selection. It reads as a broken store, and many shoppers leave rather than retry.

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 FR/US country popup to a small dismissible corner banner or auto-detect locale silently, and ensure the size grid and black 'Add to Bag' button remain fully visible and clickable without requiring the shopper to close an overlay first.

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.

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

Dismiss or reposition the 'ARE YOU IN THE RIGHT PLACE?' modal so it doesn't cover the primary checkout button, and ensure the checkout button uses a bold, high-contrast color (e.g. Gymshark's black/blue) larger than the FR/US selector buttons so it remains the clear focal point once the modal closes.

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.

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.

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.

The problem

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.

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.

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.

The problem

Cart items can't be edited in place: quantity changes or removals are missing or require leaving the cart.

Why it matters

Shoppers adjust quantities at the last moment. If editing is hard, they either abandon or check out with the wrong items and return them later.

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 clear selected-state to the size grid (e.g. filled black background with white text for the chosen size like 'M (8-8)') and display confirming text such as 'Size: M' near the 'Select a size' label so users can verify their choice before checkout.

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.

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.

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.

The problem

The variant picker on mobile has options that are too small or too close together. Fingers hit the wrong option.

Why it matters

Every mistap on a variant is either an abandoned cart or a wrong-order return. On mobile, this is one of the top sources of hidden lost revenue.

What to do

Increase each of the 7 crop-top thumbnail swatches to at least 48x48px and add 8-10px spacing between them, or reduce the number shown per row to 5 with horizontal scroll to prevent accidental taps between similar dark-colored variants.

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.

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.

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 progress bar above the 'Express checkout' section (e.g. 'Information → Shipping → Payment') with the current step bolded/highlighted in black to match the Gymshark logo styling, so users know how many steps remain before payment.

The problem

There's no way to edit the cart from inside the checkout; fixing a quantity means abandoning the checkout flow.

Why it matters

Buyers often spot a mistake at the order summary. If fixing it costs their progress, some just quit.

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.

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.

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.

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.

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.

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.

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. 'Email', 'First name', 'Address Line 1', 'City', 'State', 'ZIP code', 'Card number', 'Expiry', 'CVV') above or beside each input box similar to the Shopify checkout pattern, instead of relying solely on the gray placeholder text that disappears on typing.

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 or beside the CONTACT/Email field (near the 'Sign in' link at y~0.27) so shoppers see trust cues before entering personal data, and repeat a PCI/SSL badge near the future payment fields once they load.

The problem

There's no visible way to reach help from the checkout page: no phone number, no chat widget, no "Need help?" link.

Why it matters

When something goes wrong mid-checkout (a declined card, a missing address field), a visible help option is the difference between recovery and abandonment.

What to do

Add a persistent 'Need help?' link or chat bubble in the top header next to the GYMSHARK logo, or place a small 'Questions? Contact us' link beneath the 'Express checkout' heading so shoppers stuck on address or payment fields (like the empty Address Line 1 or Credit/Debit Card fields shown) can get support without leaving the page.

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.

The problem

The cart URL contains a session token, so opening it in a different browser or by an agent yields an empty cart. Cart state is not portable.

Why it matters

Agentic commerce workflows hand off the cart between the buyer, the agent, and payment providers. If the cart URL is session-bound, that handoff breaks and the buyer has to start over.

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.

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 (- / number / +) below the 'Learn more' link and above the color swatches, using at least 44x44px tap targets in the same dark/black style as the 'New' badge for consistency.

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.

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.