By industry
Summer school website: the grade mismatch
A parent needs a program for a child who finishes fourth grade in June, and wants the dates before anything else. Find where the site makes them stop reading, and see what a simulated visitor does first.
Why do parents leave a summer school website without enrolling a child?
Parents leave when they cannot confirm three things quickly: that the program runs on the dates they need, that their child's grade is allowed, and that enrollment is open now. Some sites list dates in a paragraph, show a grade range that stops a year short of the child's grade, or send the parent to a form that does not work on a phone. Check each one on a phone before you change anything else. A simulated test sends a visitor through the dates and the enrollment form, and shows the step where they stopped and why.
What this looks like in a report
“The page says kindergarten to eighth, so he should fit. This form starts its grade list at ninth, so I cannot pick his year. I will ask a friend instead.”
The fix. Make the grade list in the enrollment form match the grades on the page, with the same words and the same first and last grade. Put the start and end dates on the first screen as calendar dates, then send a simulated visitor through the form on a phone to confirm a fourth grader can be selected.
An illustration. Run a test to see your own.See a real sample report
The grade on the page and the grade in the form disagree
A parent scans a summer program the way they scan a menu: they look for their child's grade first. If the page says kindergarten through eighth and the child has just finished fourth grade, the page has answered the question. If the grades appear only inside a PDF, the parent has to read a document on a small screen to find out. Then the enrollment form asks for the grade again, from a drop-down that starts at a different level. The parent now has two answers and assumes the program has not sorted out who it is for.
- Does the page name the grades or ages on the first screen, in the same words the form uses?
- Do the start and end dates appear as calendar dates, not as the words early summer?
- Is the enrollment button visible on a phone without opening a PDF?
- Does the registration form offer the same grade list as the page above it?
- Does the page say whether a spot is open, a waitlist exists, or enrollment is closed?
Dates a parent can check against a school calendar
A parent checks the dates first, against the school calendar, the work calendar and the childcare plan. A paragraph saying the program runs in early summer, with the exact weeks in a PDF, makes that check hard on a phone. Put the first day, the last day and the daily hours on the first screen as plain dates. If there is more than one session, list each one with its seats left or a waitlist note beside it.
Test the dates from the parent's side. Send a simulated visitor to the page with this task: Find the dates for a fourth grader and start an enrollment. The visitor reads the first screen and the session list, then reports where it stopped. If it stops before a date appears, the page hides the dates. If it reaches a date but cannot tell which session fits its grade, the sessions need grade labels.
A grade list that changes between the page and the form
The enrollment form is where a grade mismatch turns into a dead end. Some schools reuse a form from another program, and the drop-down keeps an old list: high school grades on an elementary program, or a birth year range that starts too late for the child. The parent has already decided the child fits. The form then says otherwise, and the parent cannot tell whether the program is closed to them or the form is broken.
Check the two lists side by side. Copy every grade the page names and every option in the grade drop-down into one note. If a grade on the page is missing from the form, the form is wrong. If the form offers a grade the page never mentions, the page is incomplete. If the grades match and the form still refuses the child, a rule on the server is the cause, and the error message is the place to start.
PDF forms, desktop-only pages and the enrollment step
Some summer school sites send enrollment to a PDF whose fields do not fill in on a phone. The parent opens the file, cannot type into the boxes, and gives up. Others have a real online form that works on a laptop, but the submit button sits under a sticky banner on a phone, so the form looks finished and nothing happens. From the parent's side both failures look the same: they tried to enroll and could not.
Tell them apart with one phone test in a private window. Open the enrollment link, try to fill in the name and the child's grade, and tap submit. If the link opens a file rather than a form, the enrollment is a PDF. If the fields accept text but submit does nothing, look under the banner. If submit leads to a medical form before any payment step, note that step as the place a parent stops.
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 session or a reused form can split the grades again
The first run finds the grade or date that stops the parent. The fix makes the page and the form agree, and puts the dates on the first screen. Run the same visitor again to see whether a fourth grader can be selected and the enrollment starts. Run it again when you open a session, add a grade or reuse last year's form, since a form copied from another program is exactly how the lists drift apart.
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
Will this tell me how many children will enroll?
No. The test does not predict enrollment numbers or how many parents will finish the form. It shows the step where a simulated parent stopped, and what the page or form showed them there. Count enrollments in your registration system, before and after each change.
Can a simulated parent pay the fee?
No. The test goes up to the payment step and cannot pay with a real card. A fee paid by check or bank transfer also stops it, since a visitor cannot send money. The report shows whether the fee and the payment step were reached.
Does the test check my program's safety or staffing?
No. It checks the words on the page, the dates, the form and whether a visitor can get through them. It does not check background checks, supervision ratios, insurance or the rules for children's programs in your area. Those need your own records and a review by people who know those rules.
Should I use a real child's details in a test?
No. Use made-up names, birth dates and grades, and do not upload a list of families or type a real child's details into a test. A test does not check your forms for privacy rules, so keep real family records out of it.
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.