Why it isn't converting

Checkout page conversion rate: orders per start

Shoppers reach the checkout and some never order, and the store admin does not say which field or option lost them. Mimiq walks a simulated shopper through the checkout to the payment step and shows the screen where a shopper like them stops.

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

How do I work out my checkout page conversion rate?

Divide the orders placed in a period by the checkouts started in the same period, using counts from the same store and dates. The result shows how many shoppers who reached checkout finished it, but not why the others left. Late shipping costs, a required account, a missing payment method and a field that rejects a valid address all lower it, and each one needs a different fix. A simulated shopper walks the same checkout up to the payment step and shows the field or option where they stopped.

What this looks like in a report

Who
Nikhil, buying a gift for his brother in another state
How they arrived
Clicked a shopping ad for a leather wallet on his phone
Where they stopped
Address form, after typing the zip code

“The form says my zip code is not valid, but it is the one I always use. There is no hint about which format it wants. The total is still changing, so I have no idea what I'll pay.”

The fix. Accept a postal code in the format of each country you ship to, and show the expected format under the field. Show the shipping and tax total before the payment step, and keep it unchanged after the address is saved.

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

Checkout starts and orders are counted in different places

The rate divides two counts that often come from different places. The checkout start may be recorded when the address page loads, which includes a shopper who clicked by mistake. The order may be recorded on a confirmation page that some shoppers never reach, such as one who closed the tab after paying. A shopper counted at the start who never orders is a lost sale. A shopper who paid but never saw the thank-you page is a counting gap, and it moves the rate just as much. Compare both counts against the same orders in your store admin before you read the rate.

  • Checkout starts and placed orders for the same dates, pulled from the store admin
  • The address form: does it accept a valid address from your main ad country without an error?
  • Shipping and tax: do they appear before the payment step, and does the total stay the same?
  • Payment options: is the method most of your shoppers expect shown on a phone?
  • The step after payment: does the confirmation page load and record the order?

Count the starts and the orders from the same source

Before the checkout rate means anything, the two numbers need one origin. Take the orders from the store admin, and take the checkout starts from the same system for the same date range. If the checkout start is counted in an analytics tool, check how often it fires for one shopper who moves between the cart and the address page. Two counts from two tools will never match exactly, so decide which one is the denominator, write it down, and compare the same pair each month. A rate that changes because the counting changed is not a result.

Losses cluster at one address field or one payment choice

Most checkout losses sit in a short list of places. The address form may reject a postal code format from another country, or require a line that is not needed. The total may change after the address is typed, because tax or shipping appears late. The payment page may show no option the shopper uses, or show one in a way that looks unfamiliar on a phone. Each one looks like the same drop in the rate. Walk the checkout yourself on a phone, in a private window, with a real address from your largest ad market, and write down the first moment you hesitate.

The test stops at payment, so the last step still needs a real check

A simulated shopper can reach the payment step and stop there, which covers the address, the delivery choice and the total. It cannot pay with a real card, sign in with Google or complete a payment that a bank has to approve. Test the payment step yourself with your payment provider's test mode, and check the confirmation page. A shopper who paid and then saw an error is a lost order, and the rate records it as a loss.

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 shipping rule or payment option can move the drop to the last step

Shipping rules, tax settings and payment options change without a page redesign, and any one of them can add a field, move a total or hide a method. Run the checkout again after each change, from the same address, on a phone. When shoppers must sign in, check the checkout behind a login with a test account. Give each shipping country its own run, since a checkout that works for one country can stop at the address for another.

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

What checkout conversion rate should I expect?

The number depends on your checkout. A store with one product at one price and a store with delivery choices and a required account will not match. Compare your rate with your own earlier periods, and split it by device and by shipping country. Mimiq does not give a target rate and does not predict the rate of any checkout.

Can a simulated shopper complete an order?

No. The test goes up to the payment step. It cannot pay with a real card or use a payment method that needs bank approval. Complete one order yourself in your provider's test mode to check the confirmation page and the order record.

Should I remove the account step?

Test it first. A required account can help repeat buyers, but many first-time shoppers leave when asked to create one before they reach the address form. Run the checkout with a guest path, and compare where the shoppers stop. Keep the account option, but move it after the order when the purchase does not need it.

What can the test not tell me about the rate?

It cannot tell you whether a shopper who would have bought was put off by the price, the delivery time or a competitor. It shows where a visitor who follows the checkout stops, with a screenshot. The rate itself still needs the store's own counts.

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 .