By industry
Climbing gym website: day passes and waivers
A first-time visitor wants a day pass on their phone before they drive over. Mimiq sends simulated visitors through the purchase and the waiver, then shows where each one stops and what they were told.
What should a climbing gym website show a first-time visitor before they buy a day pass?
It should show the day pass and the membership as separate choices, name the waiver before the payment step, and say what a visitor gets after paying, such as a confirmation, a wristband or a name at the desk. Many gyms use different waivers for adults and for children, so the page should say which one applies. A simulated test walks the pass path up to the payment step and shows where a visitor stopped.
What this looks like in a report
“The waiver is a PDF. I can't see where to sign it on my phone, and I don't want to pay before I know what I'm agreeing to. I'll check their Instagram and try again later.”
The fix. Move the waiver onto the pass page as a form the visitor can sign on a phone, placed before the payment button. After payment, show a page that says the waiver is on file and what to bring, and email the same text.
An illustration. Run a test to see your own.See a real sample report
The waiver opens as a PDF after payment, so the pass sits unsigned
A visitor who has never climbed indoors wants to know what they are signing and whether they can go today. Climbing gyms usually ask for a signed waiver before a first climb. That can be a PDF link on the pass page, or a form that appears only after the card is charged. On a phone the PDF opens in a viewer with no obvious way to sign it, so the visitor goes back without a waiver on file. The confirmation says to bring the pass to the desk, and the desk asks for the waiver. The visitor has paid for a pass they cannot use yet.
- Is the waiver on the pass page before the payment step, with a clear next step after it?
- On a phone, does the waiver open as a page you can sign, or as a file with no way back?
- Does the confirmation say what to bring, and whether the waiver is done before the visit?
- For a child's pass, does the page say who signs, and ask for a parent's email?
Day pass and membership on one screen, and which one a visitor wants
A first-time visitor wants one visit, and a day pass is the only thing that gets them climbing today. A membership is a commitment, usually with a monthly fee. If the page leads with membership tiers and puts the day pass in a small link, the visitor may think they must join before they can climb once, and the waiver never comes up. Open the site on your phone, from the homepage, and count the taps to a one day pass. If it takes more than a couple of taps, or the link goes to a membership form, the first screen is the problem.
The waiver, a child's pass, and what happens after paying
The waiver is where most first visits stall, and the stall is quiet. A visitor who reaches a PDF on a phone may not find the sign button, may not realize the form needs a typed name, or may close the viewer and forget. For a child's pass, the form usually needs a parent or guardian to sign, and the page should say so before the payment step. Check the path from a child's pass: who is asked to sign, which email is needed, and whether the waiver can be done before arrival. A waiver left until the desk is a second place a visitor can turn back.
Testing the pass path up to the card step
Give the simulated visitor a task: choose a one day pass for one adult on Thursday and sign the waiver. If the pass can be booked without a card, the confirmation email reaches the visitor's inbox, and you can read what it says about the waiver and the desk. A payment that needs a real card ends the run at the payment step, and the report marks it there. A waiver that asks for an in-person signature stops the visitor at that step. Run the same visit again after each change, from the first screen on a phone, and check that the waiver is still reached before the card.
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 pass type or a new waiver tool can put the PDF back on the page
A new pass type, a new waiver tool or a new booking page can send the waiver back to a PDF link. Rerun the same simulated visitor after each change, once for an adult day pass and once for a child's pass. Test the pass page on a phone before you post a summer offer or a link in a climbing group, since those visitors often arrive with no idea what the waiver involves.
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 a simulated visitor buy a day pass?
Only up to the payment step. Visitors cannot pay with a real card, so the run ends there and the report marks it. The test shows what the visitor saw before paying, including the waiver and the pass details, which is where first-time problems show up.
Does this tell me how many visitors will buy a pass?
No. Mimiq does not predict sales, and it cannot tell you how many visitors will buy a pass this month. It shows where a simulated visitor stopped and what the page said there. Your payment reports and your site analytics give the numbers, and a change measured against the same traffic gives the cause.
Can the test check my waiver wording?
No. The test checks whether the waiver is reachable, signable and shown before payment, on the path a visitor takes. It does not judge whether the wording protects you or meets the rules where you operate. Have someone qualified review the waiver itself.
Should I test with a real member's or a child's details?
No. Use made-up names, emails and birth dates, and keep real members' records and children's details out of any test. A waiver test checks the path to the form, so it does not need a real signature or a real child's information.
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.