Before you launch or pay for traffic

Website product page checklist: what stops buyers

The page looks finished to you, because you already know the size you want. A shopper has to reach Add to cart without help, and a simulated visitor can show where they stall.

5 visitors try to .
First test free with an accountRun it from your coding agent

What should a website product page checklist cover?

A product page should show the price and the chosen variant together, change the photo and the stock message when the variant changes, and keep Add to cart active only for a variant that can be bought. The shipping cost or delivery estimate should appear before the cart, and the page should read the same on a phone. A simulated test picks the variant its task names, presses Add to cart, and reports the step where a shopper stopped, with a screenshot.

What this looks like in a report

Who
Teodor, looking for a waterproof jacket for a wet spring trip
How they arrived
Clicked a shopping ad for rain jackets on his phone
Where they stopped
Product page, after choosing a size

“I picked a medium, but the photo still shows the black one. Is the medium in stock, or is the price for another size? I will not guess.”

The fix. When the size or color changes, update the photo, the price and the stock message in the same render. Disable Add to cart for any size and color with no stock, and show 'Out of stock' beside that size.

An illustration. Run a test to see your own.See a real sample report

The photo, the price and the button disagree after a size change

A shopper chooses a size from a drop-down, then looks at the photo to check the color and at the price to check the total. On many product pages one of those three lags behind. The photo stays on the first color, the price keeps the base amount until the page reloads, or Add to cart stays active for a size that is sold out. The shopper cannot tell which number is right, so they assume the worst and go back to the results. The owner rarely sees this, because the owner already knows the size they want and clicks the one that works.

  • Pick each size and color in turn. Do the photo, the price and the stock message change each time?
  • Is a sold out size marked unavailable before the shopper presses Add to cart?
  • On a phone, can the size chart open without leaving the product page?
  • Does a shipping cost or delivery estimate appear before the cart?
  • Does the product title match the ad or search that brought the shopper here?

Where the checklist items break: the second variant, not the first

A checklist item passes or fails on the variant the page loads with. Most owners check that one, because it is the variant they sell best or the one they set up. The break comes when a shopper picks the second size or the second color. Wrong: a single photo for every color, and a price in the header that updates only after a reload. Right: a photo for each color, the price placed beside Add to cart, and both updated by the same selection. Check each item against the last variant in each list too, since that is the one nobody opens while they build the page.

A wrong item in the cart, or a stock error after the add

Two faults both end with a shopper who wanted a size and got an error or the wrong item, and they sit in different places. If the cart line shows a different size or color from the one the shopper picked, the fault is in the display or in the variant the button sends. If the cart line matches but the shopper is then told the item is out of stock, the stock check ran late, after the button had already been active. Read the cart line in the screenshot after each test add, so the variant and the message tell you which of the two you are looking at.

Test the page as a shopper who already has a size in mind

Give the test one task on the product address: add a medium blue jacket to the cart. Each visitor picks the variant the task names, presses Add to cart and reaches the cart. The report then shows where each visitor stopped, which step the failure sat on, and a screenshot of that step. A visitor who picks a sold out variant sees whatever the page shows, so a button that stays active shows up in the report. What the test cannot check is your stock count. It sees the page, not your warehouse system, so a size the page shows as in stock while your shelves are empty will pass the test.

What you get with Mimiq

  1. 01

    Run it by hand, or on every pull request

    Paste a link and a task in the app and watch the visitors work. Or run them on every preview deploy: the GitHub Action comments on the pull request, any other CI can call the MCP endpoint, and your coding agent can run it too.

  2. 02

    Bugs and usability problems in one report

    The browser records errors and failed or slow requests on the step they happened. The visitors say where the wording or the steps confused them, and where they left.

  3. 03

    Visitors that behave like your audience

    Each visitor is a different profile with a reason to be there, matched to who the page is for, described by you, or built from your own customers.

  4. 04

    A prompt to fix each problem

    Every problem comes with a fix to paste into Cursor, Claude Code, Lovable or any coding agent, and one prompt hands over the top problems at once. Then send the same visitors through again.

  5. 05

    Follow every visitor

    See each visitor's whole path, step by step with screenshots, and what it was thinking at every step. Ask any visitor a question.

The browser records relevant JavaScript errors and failed or slow app requests encountered during the run, attached to the step where they occurred. The visitors are simulated: they find problems, they do not predict how many real people will convert.

A restock or a new color can bring the mismatch back

A catalog changes after launch: a color is added, a size sells out, a supplier swaps the photo set. Each change can leave one variant with the wrong photo or a button that stays active. Rerun the same shoppers after every catalog change, on a laptop and on a phone, and check the last variant in each list. Do it on the preview address before the new products go live.

Starter

Try it on one launch

$9 once
120 credits, never expire

About 4 tests of 5 visitors

  • Visitors on your landing page, signup and checkout
  • Where they left and why, with a fix to copy for each problem
  • Run it in the app or on every pull request
  • Ask any visitor a question, included
  • Test accounts and protected previews
Buy 120 credits

Builder

Test every build

$19 a month
500 credits every month

About 20 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Builder

Pro

Test every release, as a team

$49 a month
1,500 credits every month

About 60 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Pro

Scale

Test at scale, every day

$149 a month
6,000 credits every month

About 240 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Priority support
  • Cancel anytime
Choose Scale
$0for your first test, with a free account (Google sign-in, no card). It includes 50 credits, enough for 10 visitors. After that a visitor uses 5 credits, and packs start at $9 for 120 credits.
See a sample report

Questions

Does the test check every variant on my product page?

No. One task names one variant, so a test covers only the size and color in that task. If a product has many sizes and colors, one test does not walk through them all. Check the variants you sell most by hand, then write a second task for each one you are unsure about.

Can the test tell me which product photo sells more?

No. It does not predict how many shoppers buy, and it does not rank one photo against another. It shows whether the photo changes with the color a shopper picked, and where a shopper stopped. A photo comparison needs real traffic and a live experiment.

Do I need to show shipping on the product page?

Show an estimate there if you can, because a shopper who first meets the cost at checkout may leave at that step. The test shows whether a cost appears before the payment step, and which step a visitor first saw one. It does not tell you whether the cost matches what your carrier charges.

Does Mimiq read my store's inventory or catalog?

No. It does not read your store, inventory or catalog. It sees the page a shopper sees, at the public address you give it. If the page shows a size as in stock and your shelves are empty, the test cannot catch that, because it has no connection to your stock count.

Should I test the product page on a phone?

Yes. The test runs in phone browsers at a public address. On a phone the size drop-down can sit behind the keyboard, or the photo can stack under the price, so Add to cart ends up as the last thing on screen. Run the laptop and phone tests separately, so you can see which one fails.

Keep reading

Send visitors and see what breaks first.

Your first test is free: sign in with Google and it starts right away. Last checked 2026-11-02.

5 visitors try to .