By platform
High converting Shopify product page: sizes
You checked the page with every size in stock, so the sold-out state never showed on your screen. Simulated buyers tap each option on a phone and report where the page stopped making sense.
How do you make a Shopify product page easier to buy from?
A Shopify product page works when the choice tells the truth: the price, the photo, the stock message and the add-to-cart button all change with the size or color the buyer picks. Put the size guide and the shipping line directly under the picker, not after the reviews. A simulated test taps each option the way a buyer would and reports the step where a buyer stopped.
What this looks like in a report
“Medium says sold out but the button is gray, so I cannot tell if the jacket is gone or if I picked wrong. Large has a price that did not change, and I cannot see a size guide.”
The fix. Show a line beside the size picker that names each size that is sold out, and tie the button label to the size the buyer picked. Move the size guide and the shipping line directly under the picker, then tap every size on a phone before you publish.
An illustration. Run a test to see your own.See a real sample report
The button tells a buyer nothing when the size they want is gone
A buyer opens the product, taps the size they wear, and the button reads sold out or simply stays gray. Nothing beside the picker says which sizes are gone or whether the others are in stock. So the buyer assumes the whole jacket is unavailable and leaves, or they tap another size, see the price stay the same, and start to wonder whether the page works at all. You looked at the page with every size in stock, so the sold-out state never appeared on your screen.
- On a phone, tap each size in turn. Do the price, the photo and the button change each time?
- Pick a sold-out size. Does the page say which sizes are still available?
- Find the size guide and the shipping line without scrolling back up. Are they near the picker?
- Add the item to the cart, then open the cart. Does it show the size and color you picked?
The first option a buyer taps sets the tone
Buyers often tap the size they usually wear, and that size is often the first to sell out. If the first tap lands on a sold-out option, the page has to recover the buyer. Some themes let a sold-out option stay selectable, then gray out the button after the tap, with no note about why. Test the page with your fastest-selling size out of stock, because that is the state a buyer meets on a day you did not check.
A disabled button with no reason reads as a broken page
Wrong: a gray Add to cart button and nothing else. Right: a line beside the picker that reads Medium is sold out, with Large still selectable. A disabled button without a reason makes the buyer doubt the rest of the page, including the price. Read the label text, not only the color, because the label should name the size so a buyer who tapped the wrong option knows at once.
Check what happens after the tap when a size is in stock too. The photo should change to the color the buyer picked, the price should keep its format, and the cart should repeat the same choices. A page that changes one part and not the others feels unfinished, even when the stock count is right. A buyer who sees that mismatch rarely reports it. They just leave.
Shipping and the size guide sit below the buyer's question
A buyer unsure about fit wants the size guide at the picker, not after the description and the reviews. A buyer unsure about delivery wants the shipping line before the button, not on the checkout page. When both answers sit far below the fold on a phone, the buyer scrolls, loses the picker and picks again. Place the two lines directly under the picker, and check that they stay visible when the buyer changes size.
Mimiq is independent and not affiliated with the platforms it names. Names belong to their owners.
What you get with Mimiq
- 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.
- 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.
- 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.
- 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.
- 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 hide a sold-out size again
A restock or a new color changes which options the picker shows and which ones can be selected. After each stock change, tap every size and color on a phone and read the button label and the photo each time. Keep a note of the sold-out state you tested, so the next update does not bring back the silent button.
Starter
Try it on one launch
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
Builder
Test every build
About 20 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Pro
Test every release, as a team
About 60 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Scale
Test at scale, every day
About 240 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Priority support
- Cancel anytime
Questions
Does a product page test show whether I will sell more?
No. It does not predict sales or a conversion rate. It shows whether each size and color changes the page the way a buyer expects, and where a simulated buyer stopped. Take the real rate from your store's sales data.
Can a simulated buyer add the jacket to the cart?
Yes. A run can pick the options, press add to cart and open the cart to check the choices it made. If the buyer goes on to checkout, the run stops at the payment step, because a simulated buyer cannot pay with a real card.
Should I hide sold-out sizes or show them?
It depends on the buyer. Hiding a size can make the range look smaller than it is, while showing it as sold out can frustrate someone who wanted that size. Whichever you choose, the page should say plainly what the buyer will see, and a run shows you what that looks like on a phone.
How many options should I test?
Test every size and color a buyer can pick, and pay most attention to the one that sold out first and the one that is sold out now. A page with many options has more states than you can check by eye, so each one needs a tap.
Will a test find problems in the product description?
Only the ones a buyer reports by stopping. A simulated buyer can say it could not find the fit information, but it cannot judge whether your description is accurate for the product.
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.