Why it isn't converting

Low conversion rate Shopify: find the step

Shoppers look at products and leave without adding anything, or they add to cart and disappear. Mimiq sends simulated shoppers through your store and shows the exact step where each one stops.

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

Why is my Shopify store's conversion rate low?

Shoppers who browse and do not buy usually stop in one of three places: the product page, the cart or the checkout. On a Shopify product page, the size or color picker is a common cause: the option a shopper wants is sold out or hidden, or the page opens on one they cannot buy. Find which of the three places loses the most shoppers, then fix that one first. Mimiq sends simulated shoppers through the same product-to-checkout path and shows the step where each one stopped, with a screenshot.

What this looks like in a report

Who
Joaquin, looking for a waxed jacket in a large for his brother
How they arrived
Opened a product link from a search for waxed jacket large
Where they stopped
Product page, after choosing size large

“I picked large and the price did not change. The button says Add to cart but nothing happens, and the photo still shows the small one. Is this even in stock? I give up.”

The fix. Preselect the first size that has stock, and mark each sold-out size on the picker. Gray out Add to cart only with a line that names the unavailable size, and keep the photo and price in step with the selection.

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

The product page asks a choice the shopper cannot finish

A shopper on a product page has one question before the add to cart button means anything: can I get this in the version I want? They pick a size, and the page either confirms it or quietly fails. If the option they picked is sold out, the button may still say Add to cart and then do nothing, or it may be grayed out with no line saying why. If the preselected option is sold out, the photo and price shown first belong to something nobody can buy, so the shopper assumes the whole product is gone. They leave without trying the other sizes.

  • Preselected option: is the size or color chosen when the page loads something you can actually sell today?
  • Sold-out options: are they hidden, marked Sold out, or left clickable with nothing happening?
  • Photo and price: do they change when the variant changes, or do they stay on the first option?
  • Add to cart on a phone: is the button in the first screen, or pushed under a sticky header or an app banner?
  • Feedback after the click: does the cart count or a small drawer confirm that the item went in?

The option the page opens on decides the first impression

Open the product in a private window and do not touch the options. Look at which size or color is already selected, what the price says, and what the photo shows. Then check whether that option has stock. Some stores open on the first item in the list, and that item is often the first to sell out. A shopper then sees a price and a photo for something they cannot buy, while the button still looks active. The wrong version is a default that is sold out with no label. The right version opens on the first option that can be bought, marks the sold-out ones beside the picker, and changes the photo and price when the selection changes.

A cart that hides the next step loses the shopper it just won

A shopper who clicks Add to cart has made a decision, and the cart is where that decision is kept or dropped. The cart drawer or cart page has to show the item, the quantity, the subtotal and one clear button that goes to checkout. On a small screen a drawer can push that button below the fold, and a discount field can look like the place to pay. Shoppers also stop when shipping is missing, since the cost often appears only at checkout. Compare the number of visits that added to cart with the number that started checkout in your store analytics. A large gap there points to the cart, not to the product page.

Apps and sticky bars cover the button on a phone

Review widgets, popups, countdown bars and newsletter sign-ups get added one at a time, and each takes space. On a phone, a sticky header or a bottom bar can sit over the Add to cart button, so the button is in the page but not where a thumb can reach it. A popup that opens on scroll can also hold the page until it is closed. Check this at phone width: open the product, scroll to the button, and see whether anything covers it or moves it. Remove or move the block that does it. A new app or a theme update can bring the same problem back, so check the product page again after every change.

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 new app or theme update can hide Add to cart again

Stores change after the first fix. A new review app, a popup, a theme update or a sold-out size can each move the button or empty the default option again, usually without anyone on your team seeing it. Run the same shoppers through the same product after each change, and check whether they reached the cart. Paid runs can open a protected staging copy behind a site password, so a change can be checked before it goes 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

Can a simulated test tell me my conversion rate?

No. It does not predict how many real shoppers will buy, and it does not forecast a rate. It shows where simulated shoppers stop on your store, what they were thinking at that step, and which fix to try first. Your real rate comes from your store analytics, so compare the two before you change prices or ads.

Does the test log in to my admin or read my orders?

No. A plain test uses your public store address, the same pages a shopper sees. It does not read your admin, your orders or your analytics. If a page sits behind a site password, a paid run can open it with a password you give, and nothing else in the store is touched.

Will a simulated shopper pay with a card?

No. A simulated shopper can fill in the address and reach the payment step, and the run stops there. The final card entry and the order confirmation still need a person on your team to place a test order and watch it through.

What if my shoppers leave for reasons the test cannot see?

They will. The test cannot see what your returning shoppers already think of the brand, or how much a particular size matters to a real buyer. Use the test to find the sold-out option, the hidden button or the cart step that fails, then check price with real traffic before you change it.

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 .