By industry
Campground website design: site choice stalls
A camper with a trailer and a dog picks dates, taps a site on the map, and cannot tell which sites have electric. Mimiq sends simulated visitors through the booking and shows where each one stopped.
Why do campground visitors stop before they reserve a site online?
Campers usually arrive with three facts they need matched exactly: the dates, the kind of site they need, and the rules for their vehicle or pet. A map with colors that have no visible key, a site type named differently from the way a camper would search, or a rule that appears only in the final summary can stop the booking. A simulated test books a site for a stated party, vehicle and pet, and shows the screen where the visitor could no longer match their needs to the page.
What this looks like in a report
“The map has three colors and I cannot see a key. I need electric for the trailer, and I cannot tell which numbers have it. I tapped one and nothing changed. Is site 14 free or not?”
The fix. Put a key above the map that uses words, such as open with electric and taken, and highlight the chosen site on the map itself. Show the site type and the dog rule on the same card as the price, so a visitor does not find them only at the end.
An illustration. Run a test to see your own.See a real sample report
The map shows a site the camper cannot use
A couple with a small trailer wants a weekend with electric hookup. The campground page shows a map with green, yellow and grey sites and a number on each. They pick the dates first, and the page keeps every site on the map. The green sites include tent-only spots, and nothing on the map says which are which. The camper taps a green site, the summary shows a price with no hookup line, and the vehicle length limit appears only at the end. They leave, not knowing whether the site they wanted was ever free.
- Read the map key aloud. Does it use words a camper would use, such as electric or tent?
- Pick a site that needs hookups. Does the summary repeat the hookup on the same card?
- Enter a vehicle length. Is the limit shown before a site is picked?
- Add a dog. Is the pet rule shown before the dates are confirmed?
- On a phone, tap a site number. Does the chosen site light up on the map?
Site types that do not match the words campers search for
A camper searches for a campsite with electric, a tent pad or a space for a trailer. The campground's own site types are usually named after the loop or the grade of the pitch, such as Loop B, Premium or Standard, and the visitor cannot guess which one has the hookup they need. Before any dates are chosen, the page should list each site type with one line that says what it includes: tent only, electric, water and sewer, or cabin. Read each site type name aloud and ask whether a camper could match it to a search. If not, add the words a camper would type next to it.
The map colors that nobody explains
The map is the one place where a camper picks a number, and nothing on the page explains it unless someone wrote a key. Green, yellow and grey can mean open, limited and closed, but a visitor who arrives cold does not know which is which unless a key sits near the map. On a phone, the map is small, so the numbers are hard to tap, and a tap on a site that is actually taken may do nothing at all. Look at the map in both views and tap three sites in a row. If the chosen site does not highlight, the visitor cannot confirm that the number they picked is the one they will get.
Vehicle and pet rules that appear only in the summary
Length limits and pet rules can end a stay that looked fine. A visitor with a long trailer needs to know whether the site takes it, and a visitor with a dog needs to know whether the loop allows one. When those rules appear only in the summary, the visitor has spent several steps picking dates and a site, and now has to start over. The fix is to show each rule on the site choice card, before the dates, and to make the length field refuse a site that cannot take the vehicle. Test with a vehicle at the limit, and with one just over it.
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 map or a seasonal site change can make a free site look taken
The first run finds the screen where a camper with a trailer and a dog gave up. A fix changes the map key, the site type names or the rule card, and a new season, a renumbered loop or a changed map can bring the same stop back. Run the trailer visitor after each change, then a tent visitor who needs no hookup, so both kinds of site get checked.
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 this tell me how many campers will book a site?
No. It does not predict how many campers will book, and it cannot tell you how many chose another campground. It shows the screen where a simulated camper stopped, what the map or summary said, and what they could not match. Bookings come from your reservation records and analytics.
Will a test hold a site or take a deposit?
The test goes up to the payment step and stops, because visitors cannot pay with a real card. If your booking holds a site before payment, check whether the hold appears on your live calendar, and remove it. Run the test on a staging copy where you can.
Does the test check local fire rules or site condition?
No. The test checks what the page says and whether a visitor can reach payment. It does not check fire restrictions, insurance, or whether a site is clean or open on a given day. Those belong to your park staff and the rules for your area.
Should I test the map on a phone and a laptop?
Yes. A map that works on a laptop can have targets too small for a thumb. Run the same visitor on each, and compare which site number they chose. Keep the visitor's goal the same across both runs, so the difference comes from the layout.
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.