By platform

Weebly checkout not working for some shoppers

A shopper adds an item, enters an address, and reaches a step that shows no shipping options or drops the cart. Mimiq sends simulated shoppers through the store and shows where each one stopped, with a screenshot.

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

Why does my Weebly checkout stop for some shoppers but not for me?

Checkout usually stops for some shoppers because of the country they ship to, or because their browser does not keep the cart from one page to the next. A test order from your own browser often passes, since your country, your browser and your saved cart are the ones you already set up. A simulated test runs the same path as a shopper from outside, and shows the step where each run stopped, with the message the page displayed.

What this looks like in a report

Who
Yusuf, buying a ceramic mug as a birthday gift for his sister in Canada
How they arrived
Clicked a shared product link in a group chat
Where they stopped
Shipping step, after entering his address

“The page says no shipping options are available for my address. I added the mug and I was about to pay. Is the shop closed to Canada, or is something broken on my side?”

The fix. Show a clear message at the address step that names the countries you ship to, and list them in the shipping settings so an empty option list is explained. Test the checkout with an address in a country you do not ship to, and confirm the message appears.

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

The shipping step that offers nothing for one country

A store can ship to some countries and not others, and a shopper outside that list reaches the shipping step with no options to pick. The page may show an empty list, a generic message, or a rate that does not add up. Nothing in the cart is wrong, so the shopper blames the store and leaves. The owner who tests from home enters a home address that is on the list, so the step looks fine every time. Only the address the shopper types changes the path.

  • Does the shipping step show at least one option for each country you sell to?
  • Does an address outside your shipping list show a clear message, not an empty step?
  • Does the cart still hold the item after you move from the cart page to the address step?
  • Does the payment step load once the address and the shipping choice are saved?

The shipping list that ends at the address step

Most store setups keep a list of places you ship to, with a rate or a free option for each. If a shopper's country is not on that list, the store has no option to offer, and checkout can stop at the step where shipping is chosen. The shopper sees a blank choice, a warning in small text, or a button that stays gray. Because the list lives in the shipping settings and not in the cart, the cart looks fine right up to that point.

If your rates depend on weight, the same thing happens with a single product. An item with no weight set can fail the rate calculation, and the shopper sees no option at all, even from a country you ship to. Check each product that has no weight or size, because one missing field can stop checkout for everyone who buys that item.

A cart that empties between the cart page and payment

The second failure happens between pages. The cart keeps its items in the shopper's browser, usually through a cookie or a session that the store sets when the first item goes in. If the browser blocks that cookie, or the shopper opens the store inside another app's built-in browser, the cart can be empty when the next page loads. The shopper sees an empty cart at the step where they expected a total, and assumes the order vanished. You do not see this from home, because your browser keeps everything you put in.

Tell the two failures apart by the step and the country

Run one order from a private window with an address in a country you do not ship to, and note the step. An empty shipping list means the shipping settings are the cause. A cart that loses its items before the address step means the browser or the cookie setting is the cause. A payment step that does not load, with the address and shipping saved, points at the payment setup, which a test cannot finish. The screenshot for each run shows which of these the shopper met.

Then repeat the run from a phone and from a laptop, with the same product. If the phone fails and the laptop passes, look at the phone layout and at any app browser a shopper might use. If both fail on the same step, the shipping rules or the product data is the cause, and no layout change will fix it.

Mimiq is independent and not affiliated with the platforms it names. Names belong to their owners.

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 country or theme update can empty the cart again

Checkout breaks again after a change that looks small: a new country added to the shipping list, a product with no weight, or a theme update that changes how the cart is stored. Rerun the same shopper path after each change, from an address outside your shipping list and from a phone. You catch the step that moved before the next shopper leaves at it.

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 the test pay for the order?

No. Visitors cannot pay with a real card, so the test goes up to the payment step and stops there. It cannot tell you whether the payment provider accepts a card, or whether an order record reaches your system after payment.

Does the test use my real products and prices?

Yes. It uses the store the way it is published, so the products, prices and shipping rules are the real ones. Pick a product you actually sell, because that is the one a real shopper reaches at the same step.

Will it test a discount code?

It can, if the code field is on the page and the visitor can type a code. The report shows whether the code was accepted and what the page displayed next. It cannot tell you whether the discount is calculated correctly, so check the total on a real order before you trust it.

Do shoppers need an account to check out?

Only if the store asks for one. A guest checkout needs an email address, which visitors have. Visitors cannot sign in with Google or single sign on, so if your store forces a login, use a test account you give the visitors with paid credits.

Does a clean run mean real shoppers will buy?

No. A clean run shows that a simulated shopper can reach the payment step along a given path. It does not predict how many real shoppers will buy, or how many leave at shipping because the cost is too high for them.

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 .