Why it isn't converting
Why do customers abandon carts: where they quit
Shoppers fill the cart, get as far as the total or the account form, then close the tab. Mimiq sends simulated shoppers through the same cart and shows the screen where each one stops, with a screenshot.
Why do customers abandon carts before they order?
Most abandoned carts end on one of four screens: the cart total, the account or sign-in step, the delivery choice or the payment form. A shopper leaves when the price changes, a step asks for more than they expected, or the cart fails to hold what they added. A cart report only counts the abandoned cart, so these causes look identical there. A simulated shopper walks the same cart and shows the screen where each one stopped, with a screenshot.
What this looks like in a report
“The total went up by a lot once I typed the address, and now there's a password box before I can pick a delivery day. I just wanted to send a gift. I'm leaving.”
The fix. Show shipping and tax on the cart page, next to the item price, and offer guest checkout above the sign-in form. Keep the delivery date choice visible before the payment step.
An illustration. Run a test to see your own.See a real sample report
The total changes after the shopper has already decided
A shopper decides to buy when the price looks final, so a change at the end feels like a trick. Shipping, tax, a handling fee or a discount that disappears can show up after the address is typed, which is the point where the shopper compares the total with what they expected. A required account is the next common cause. A shopper who wanted a one-time purchase sees a password field and closes the tab rather than invent a login. Some carts also empty on return, so the shopper finds nothing left to finish.
- The cart total at each step, with shipping and tax shown beside the item price
- A required password on the checkout form, and whether guest checkout is offered at all
- The coupon box: does it send a shopper to a search for codes or to another site?
- Close the browser, reopen the store in the same browser, and check every item is still there
- Delivery choices for a date or speed, with the extra cost of each one shown
The shipping line is where most shoppers decide
Shoppers compare the cart total with the price on the product page and with the price the ad showed. A product listed at one price that shows a higher total after shipping is a surprise, and a surprise at the cart is the cheapest place for a shopper to quit. Check the cart with a delivery address in each country your traffic comes from, and compare the total with the listed price. If the real total appears only after the address form, the shopper has already spent effort on something they may not buy. Show the likely total early, and keep it the same on every screen after.
A forced account ends the visit for a one-time buyer
A shopper who wants to buy once, as a gift, does not want an account. When the checkout asks for a password before the address, many close the tab. Check whether guest checkout is offered, where the account option sits, and whether the sign-in step can be skipped. Some stores offer a guest path but bury it under a large sign-in button. Try the checkout as a first-time buyer in a private window, and note whether you were asked to create anything before you could enter a delivery address. A reminder email cannot fix a screen the shopper never got past.
A cart that empties on return looks like a lost sale
Some carts are not abandoned at all. The shopper adds items on a phone, switches apps and comes back later to an empty cart or one missing an item. This happens when the cart is tied to a browser cookie that expires, when cookies are blocked, or when the shopper returns in a different browser. The shopper cannot see which, so they assume the store failed and leave. Test it by adding two items, closing the browser completely, and opening the store again in the same browser, then in a fresh private window. Count the items each time.
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 new shipping app or cart theme can empty the cart again
Cart apps, shipping calculators and themes change the cart page, and each update can move the total or reset the cart on return. Run the same cart after each change, on a phone and in a fresh browser. Test the checkout behind a login with a test account, so the account screens are checked as well. Send each new country or delivery option through its own run before it goes live.
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
How do I know which screen is losing the carts?
Start with your own counts for the same dates: carts created, checkouts started and orders placed. A large drop between two of them points at the screen after the drop. Then walk that path as a shopper, because the counts cannot show what was on the screen. A simulated shopper does that walk and shows the screen with a screenshot.
Can a simulated shopper finish the purchase?
No. The test goes through the cart, the account step and the delivery choice, then stops at the payment step. It cannot pay with a real card or sign in with Google. Use your payment provider's test mode for the final step, and check the confirmation email yourself.
Will a reminder email bring these shoppers back?
The test cannot tell you that, and no simulated run can show it. Use it to check that the cart a reminder points to still holds every item. Fix the screen the carts stop on first, then measure the reminder against your own abandoned carts over the same weeks.
Should I remove the coupon field?
Not automatically. A field that sends shoppers to a search for codes often ends the visit, so check where the shopper goes after they click it. If the field leads away from the store, change it before you remove code entry altogether.
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.