Test a page or flow
Test checkout Squarespace: where buyers stop
Your store works when you open it on your own laptop with your own address. A stranger on a phone may see a different shipping price, or no shipping option at all.
How do I test checkout on a Squarespace store?
Go through a purchase as a guest, starting from a product page and stopping at the payment step, using an address in a region you ship to and one you do not. Check that the shipping rate, tax and total on the last step match what you set in your store settings for that region. What a buyer pays depends on where the order goes, so each region needs its own pass. A simulated test adds visitors who do this from their own browsers and report the step where each one stopped.
What this looks like in a report
“The bowl looked fine on the product page, and now the total is higher and I cannot see why. I will just buy it somewhere else, where the price is what I saw.”
The fix. Open the shipping settings for Canada and check that a rate covers that region, and add one if it is missing. Run the same guest through again and compare the total on the last step with the price on the product page.
An illustration. Run a test to see your own.See a real sample report
The shipping rate changes with the address, and the buyer sees it last
The shipping rate is decided after the buyer types an address, from the regions and rules you set. An address in a region with no rate, or a cart that misses a free shipping minimum, gets a different price or no option at all. Tax can add a line at the same point. The product page shows the price you wrote, but the total is the one the buyer pays, and on a small screen that total is easy to miss. The owner rarely notices, because their own address already matches a rate they chose.
- Enter an address in a region with no shipping rate and see what the step offers.
- Compare the price on the product page with the total on the last step before payment.
- Check that a tax line appears for every region where you charge tax.
- Try a cart just under and just over any free shipping minimum.
Walk one purchase from the product page to payment
Start where a stranger starts, on the product page with no cart and no saved details. Pick the options the page offers, add the item and open the cart. Then go through checkout as a guest, filling in the email, the address and the shipping choice in the order the form asks for them. Write down the total at each step. A total that changes between the cart and the last step is the first thing to investigate, because the buyer saw the first number and pays the last one. You set up the path, so you know which option to pick. The walk shows a stranger's version only if you pick the way they would.
Regions and free shipping decide the line the buyer sees
The shipping line depends on the region the address falls in. A region with a rate shows that rate, and a region without one shows nothing, or a rate you did not expect. Free shipping rules add a second condition: many shops offer free shipping only above a minimum amount, so the same product can cost more in a small cart than in a large one. Tax works the same way, with rules that apply to some regions and not others. Test one address per region you sell to, and one cart on each side of every minimum, because the line only changes at those edges.
Variants that look available and an add to cart button that does nothing
Products with sizes or colors add a second place a shopper can get stuck. The page may show a sold out option as if it were available, or keep the add to cart button inactive until a choice is made. A shopper who picks the first size in the list can press the button, see nothing happen and decide the store is broken. Pick each variant in turn, add each one to the cart, and check that the cart shows the size and color you chose. Your own habit is to pick the size you know is in stock, which is the one path that never fails for you.
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 region or tax rule can change the total for buyers there
Regions, tax rules and free shipping minimums change without touching the product pages, so the shop looks the same while the total moves. Rerun the same guest visitors after each change, and compare the total they reached with the total the product page showed. Keep one visitor for each region you sell to, and one for a cart on each side of each free shipping minimum. The comparison tells you whether the change reached the buyer.
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
Can I test payment on Squarespace without a real card?
Stop the test at the payment step and do not enter a real card, and do not ask a visitor to. Payment setup is a separate check from this one, so run a payment test yourself, using the test details your payment provider publishes. The simulated test covers the contact details, address, shipping and totals up to the point where money would move.
Should I test every product?
No. Pick the product your ads point to, one with variants, and one that costs much more or much less than the rest. Most checkout faults sit in shipping and tax rules, which apply to whole groups of products. One product from each group catches most of them, and you can add more when a buyer reports something you did not see.
What can the test not tell me?
It does not tell you how many buyers will finish checkout. A simulated test shows the step where a visitor gave up and what they said at that step. A completion rate needs real traffic, which means your store data or a live experiment, not a set of simulated visitors.
Why does checkout work for me but not for a stranger?
You have your own address saved in the browser, and you already know which size or option to pick. A stranger chooses from the list, types an address your store may never have shipped to, and may do it on a phone. Test as a new visitor in a private window, with an address from a region your buyers live in.
What if my store is still behind a password?
Visitors need the site password to get past the first page. With paid credits, you can give Mimiq the password for a protected preview, and the visitors enter it as a stranger would. Without the password, the test stops at the lock screen and reports that, so you know nothing else was checked.
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.