By industry
EV charger landing page: the quote form
A homeowner with a driveway wants a charger fitted before the car arrives. Mimiq sends simulated visitors through your quote form and shows where each one stops, and the question they could not answer.
What should an EV charger landing page ask for in a quote request?
Ask for the postcode first, then the parking spot, in that order, because a homeowner can answer both without opening anything. Say plainly whether a survey comes before a fixed quote, so a visitor knows what the next step costs them in time. A simulated test sends a visitor through the quote form and shows which question they could not answer and where the page went quiet.
What this looks like in a report
“I have no idea what my fuse board can take, and I won't open it in the hallway. If you need to see it, say so and I'll book a visit. The form wants a number.”
The fix. Add a line before the fuse question that says a visit can check the supply, so the homeowner does not need to know it. Make the fuse board and supply size optional, and route a visitor who answers not sure to a survey request.
An illustration. Run a test to see your own.See a real sample report
The quote form asks about a fuse board the homeowner has never opened
A homeowner with an electric car is usually asking one question: can you fit a charger at my house, and what happens next. They do not know the rating of their electricity supply, how far the cable run from the fuse board would be, or whether a landlord has to agree. A quote form that asks for all of that before it shows a next step asks for knowledge the visitor does not have. The visitor either guesses and receives a quote built on a wrong answer, or closes the tab. If the page never says a survey can answer those questions, the guess is the only way forward.
- Can a homeowner reach the quote form without typing a fuse rating or a supply size?
- When the postcode is outside your area, does the message say why, before the rest of the form?
- Does the form offer on-street parking as an option, and what does it say next?
- If a landlord must agree, does the page say so before a visitor asks for a survey?
The postcode check, and what a visitor outside the area sees
The first gate is the postcode. A homeowner types it, and the form either moves on or stops. A form that stops with a message reading 'not in your area' and nothing else leaves a visitor just outside the line guessing whether a town next door is covered. Check the message with a postcode you do not serve. If it does not name the rule, a visitor who lives a few streets outside the line will assume they cannot have a charger and never send a quote. A short list of covered towns on the page answers that before the form does.
The questions a homeowner can only answer after a survey
Some quote forms treat every field as required. A visitor who has never opened the fuse board cannot pick a supply size, so they pick the first option or guess. A quote built on a guess is wrong from the start, and the homeowner finds out on survey day. The honest path is a field that accepts not sure and a line explaining that a visit can check it. Ask about the parking spot in plain words, such as driveway, garage or the road, and say what a road spot means for the charger before the visitor chooses it.
Testing the quote form from inside and outside the area
Test the quote form twice. First from a covered postcode, with a task to request a quote for a driveway charger and to answer not sure wherever the form asks for a fuse rating or a supply size. Then from a postcode just outside your area, to see whether the message names the rule that stopped it. The visitor has an email inbox, so a quote confirmation reaches it. A phone code stops the run at that step, since a visitor cannot receive a text. The report shows the field, the postcode it typed and a screenshot for each run. Run both again after each change.
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 covered area or a new charger brand can reopen the postcode gate
Adding a town, a charger brand or a new quote tool changes the fields a homeowner sees. Rerun the same simulated visitor after each change, once from a covered postcode and once from one just outside the line. Check the form on a phone before a new campaign or a new listing sends homeowners to it, since each source brings a different kind of household.
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
Should the quote form ask for the car model?
Not first. A visitor who has not bought a car yet, or is choosing between two, will stop at a question they cannot answer. Ask for the car later, in the reply, when you are talking about the cable length. If it stays on the form, make it optional so a homeowner without the model can still reach the quote.
Do I need a survey before I quote a fixed price?
That depends on your process, and the page should say which one you use. If you need to see the fuse board or the cable route first, say so before the visitor asks for a fixed quote. A visitor who learns about a survey after paying a deposit feels tricked. The test shows whether the page explains the survey. It does not tell you whether the survey will change the price.
Can a test show whether more homeowners will request a quote?
No. Mimiq shows where a simulated visitor stopped, which field they could not answer and what the page said when they were turned away. It cannot tell you how many real homeowners will request a quote, and it does not give a rate. Your inquiry form reports and your analytics give those numbers, and a live change against the same traffic gives the cause.
Can the test check the charger and the wiring?
No. The test checks what a visitor can do on your page: the postcode, the fields, the messages and the confirmation. It does not inspect a charger, a home's wiring or the electrical rules that apply to the job. Those belong to your installer's process and to whoever signs off the work.
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.