By industry
Online personal trainer website: the intake form
A stranger wants to get fit and wonders whether an online coach is worth a call. Mimiq sends simulated visitors through your page and shows where each one left, from the homepage to the call booking.
What stops someone from booking a first session with an online personal trainer?
A stranger stops before a first session when the page asks for a full health history before it shows a call time. Many people who want coaching online are unsure a program suits them, and they want a time to talk before they tell a stranger about an old injury or their weight. A simulated test follows a visitor from the homepage to the call booking and shows the screen where they stopped.
What this looks like in a report
“It wants my injuries, my past surgeries and my weight before it shows me a call time. I only wanted to know if the call is free and what happens on it. Not sending that to a stranger.”
The fix. Move the call booking above the intake form, and say on that screen that the first call is free and what happens in it. Ask the health questions after a time is picked, with a line saying the coach reads the answers before the first session.
An illustration. Run a test to see your own.See a real sample report
The intake form asks for a medical history before a call time
A stranger who wants to train is often a little embarrassed. They have been away for years, or they are heavier than they want to be, or a knee still aches. The trainer's page wants all of that before the call, in a long form that starts with injuries and surgeries. The visitor cannot tell whether the call is free, what happens on it, or whether anyone will judge them. So they close the form. The trainer reads the form as the first step of a process. The visitor reads it as a medical questionnaire from a stranger.
- On a phone, can a stranger see a call time without filling in a single field?
- Does the page say whether the first call is free and how long a call lasts?
- Does the intake form ask for injuries or medical history before the call time?
- Does the booking screen show the time zone the call is in?
- After the call is booked, does a confirmation email reach the visitor's inbox?
Homepage, program page and call booking, in the order they are read
A stranger rarely arrives at the call booking first. They land on the homepage from an ad or a search, read the headline and scan for a photo that looks like them. Then they go to the program page, where the difference between online coaching and a gym is either explained or assumed. Only after that do they reach the button that says book a call or apply. On a phone that button may sit under three long paragraphs, which is a lot to read before a stranger knows what a call is. Open the site on your phone and count the screens before the call button is visible.
The intake form asks for health history before a time
Coaching intake forms often borrow from clinical forms, because the trainer wants to be careful. The visitor reads them differently. An intake that asks about past injuries, medication and surgery before a call time looks like a screening, and a stranger may not trust a screening from a business they have never met. The fix is mostly order, not removal. If the answers would change what the trainer does, keep the questions and move them after the call is booked. If they would not, cut them. Tell the visitor in plain words who reads the answers and what changes because of them.
Calendars, time zones and the booking widget
The call booking is often a widget loaded from another company's site, and it can fail on a phone, show a blank box or list times with no time zone. Coaching clients are often in other cities or countries, so a call shown at seven in the morning with no zone can be booked for the wrong hour. Open the booking on a phone, read the first available time aloud and ask which zone it is in. Then check that the confirmation email shows the time and the zone too, because that email is the one the visitor will look for.
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 program page can bury the call button under the intake again
The first run shows where the call button gets buried or where the form starts asking about health. The fix moves a button or a question, and the next program page, a new calendar tool or a new coaching offer can move it back. Send the same visitor through after each change, then through the call booking from a phone set to another time zone. Repeat it before you spend on a new ad.
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
Does this tell me how many visitors will book a first call?
No. It does not predict how many visitors will book, and it cannot say how many of them will sign up for coaching. It shows where a simulated visitor stopped and what the screen asked for at that point. Booking rates come from your calendar tool and your site analytics.
Can a visitor book a real call through a test?
A visitor can reach the booking screen and go up to the last step they can finish. Visitors have an email inbox, so a confirmation email reaches them. They cannot receive a text reminder or verify a phone number, and a payment for a paid program stops the run at the payment step.
Should I put a real client's health history into a test?
No. Make up the health answers and use a test calendar slot if you have one. Screenshots in the report show what the visitor typed, so keep real client records out of the run. The test needs only the choices a visitor would make.
Does the test check the coaching itself?
No. It checks whether a stranger can understand the offer, find the call, and reach the booking. It does not judge the training plan or whether the program gets results. Those belong to your own process with clients.
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.