We found 37 issues in Toysrus's checkout, a modelled 15.8–47.7% 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

Add a sticky 'Add to Cart' button pinned to the bottom of the viewport (below the $22.99 price area) so it remains tappable without scrolling, matching the blue Toys R Us brand color used in the header.

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

A region or currency popup blocks the product page before the shopper has shown any intent to buy.

Why it matters

Interrupting a first-time visitor with 'Where are you shipping to?' before they've even seen the product costs real conversions, especially on mobile where these modals go full-screen.

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.

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 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 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

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

Since the star rating shows '(0)' with no actual reviews, consider adding a placeholder like 'Be the first to review this item!' near the stars to encourage engagement, or highlight related products with actual ratings to build trust above the fold.

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

The purple 'Chat' bubble in the bottom-right corner is unobtrusive but slightly overlaps the 'Buy with shop' button area on smaller screens; shrink it to a minimized icon or shift it 20px lower so it doesn't risk overlapping the payment buttons.

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.

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

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.

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

A star rating is shown, but the number of reviews behind that rating is not visible.

Why it matters

"4.5 stars" from 3 reviews is very different from "4.5 stars" from 3,000. Shoppers use the count as a trust signal. Without it, the rating loses meaning.

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 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.

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 step indicator bar above 'Express checkout' (e.g., 'Information → Shipping → Payment') with the current step highlighted in the blue used for the 'shop' button, so buyers know they're on step 1 of 3 and how many steps remain.

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', 'City', 'ZIP code') above each input field in a smaller gray font, similar to how 'Country/Region' currently has a visible label above the dropdown, so the placeholder text like 'Email' or 'First name' isn't the only cue once the user starts 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 lock icon with 'Secure Checkout' text directly above or beside the 'Contact' header (near the Sign in link) and repeat a PCI/SSL badge near the 'CONTINUE WITH CREDIT CARD' divider so shoppers see trust cues before entering payment details.

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 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 (- 1 +) directly above the blue 'Add to cart' button, sized at least 44px tall with generous tap targets, matching the width of the price/shipping block for visual consistency.

The problem

The CVV / security code field has no explanation or tooltip. Shoppers who don't know what CVV is are stuck.

Why it matters

CVV confusion is a top-10 reason for card-form abandonment. A single help icon fixes it for free.

What to do

Once the card fields render, add a small gray '?' icon next to the CVV/security code field (similar to the info icons already used next to Email and Phone fields) that shows a tooltip like '3-digit code on the back of your card (4 digits on Amex, front)'.

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.