By industry
Solar panel landing page design: the quote form
A homeowner clicked your ad for a free quote and landed on a page about clean energy. Mimiq sends simulated homeowners through the form and shows the field where each one gave up.
What makes a solar panel landing page get quote requests?
A solar landing page gets quote requests when the form asks only for what a homeowner knows without going to look it up. A common version puts the roof measurements and the utility bill questions before it says what the quote covers, and a homeowner who has to dig out a bill stops there. A simulated test sends a homeowner from the ad through the form on a phone and shows the field where they stopped.
What this looks like in a report
“I have no idea how big my roof is, and the bill is in a drawer somewhere. Can I guess? If I guess wrong, does the quote fall apart? I will just close this and look later.”
The fix. Split the form into two screens. The first asks for name, email, address and what the homeowner wants, and the second asks for roof and bill details with a line saying a rough guess or an estimate is fine.
An illustration. Run a test to see your own.See a real sample report
The ad promised a quote, and the form asks for homework
The ad says free quote, and the homeowner clicks expecting a price range. The page opens on clean energy language and a photo of a roof, and the form appears further down. Then it asks for the roof square footage, the roof material, the orientation, the annual kilowatt hours and the name of the utility. A homeowner who does not know the roof size is now guessing or leaving. A street address that the map check does not recognize can fail with no message. The owner built the page knowing those answers, so the gap cannot be seen from the desk.
- On a phone, can you see the quote button without scrolling past the photos?
- Count the fields before the first line that says what the quote covers.
- Does any field ask for a number the homeowner has to go and look up?
- Type an address the map does not know. Is there a message, or does the form just stop?
- After submit, does a confirmation email arrive at the address typed on the form?
What the ad promised and what the first screen shows
Start with the ad, because the homeowner does. A search or social ad that says free quote sets an expectation: a number, or at least a rough range, and a short form. Many pages instead lead with the company story, a sun icon and a line about the future of energy. That is not wrong, but the homeowner came for their own roof and their own bill, and a line like that answers neither. Open the page on your own phone from the ad link and read the first screen aloud. If the words quote, savings or your roof are not on it, the first screen is working against the ad.
Fields a homeowner has to go and find
Every field is a small errand. A roof square footage needs a tape measure or a satellite view. The annual kilowatt hours sit on a utility bill, sometimes behind a portal login the homeowner has forgotten. A form that asks for these before it asks for a name makes the homeowner stop and work. Put the questions a homeowner can answer from memory first, such as the address, the type of home and whether they rent or own. Move the measurements to a second screen, and say there that an estimate is fine and the installer measures the roof on the visit.
Promise problems and form problems fail in different places
A solar landing page can lose a homeowner in two places, and both show up as no quote requests. The first is the ad landing: the homeowner clicks for a free quote and leaves before the form is on the screen. The second is inside the form: the homeowner reaches it and stops at one field, or the form submits and no confirmation email arrives. Check the first from the ad link on a phone and note whether the quote form is visible without scrolling. Check the second by filling the form once and confirming the email arrives at the address typed.
Roof size, shading and savings belong to the site visit
A landing page test checks whether a homeowner can get through the request. It does not check whether a roof is worth panels, how much shading the house gets, or what the savings would be. Those depend on the roof, the orientation and local rules, so they belong to the site visit or a design tool. The honest version of the page says so: the quote needs a visit, and the form gathers enough to book one. Use a made-up house and made-up figures in the test. Do not type a real homeowner's utility account number or street address into a test run.
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 field added for financing can move the roof questions back up front
The first run finds the field. The fix changes the screen, and the form can drift back the next time someone adds a question for financing or a utility partner. Send the same homeowner through again after each change to the form, and check whether the confirmation email still arrives after submit. Run it again before you buy traffic for a new campaign, because a new ad can bring a different kind of homeowner in at a different entry point.
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 homeowners will request a quote?
No. It does not predict how many homeowners will request a quote, and it cannot tell you your cost per lead. It shows the field where a simulated homeowner stopped and what that field asked for. For rates, use the numbers from your ad account and your form tool.
Can a simulated homeowner send a real quote request?
Point the test at a staging copy of the form if you can, so a request does not reach your sales team. Visitors have a working email inbox, so a confirmation email reaches them. They cannot receive a text code and cannot pay a deposit with a real card, so a form that needs either stops at that step.
Should I put real roof details into a test?
No. Give the visitor made-up details. A test is not the place for a real homeowner's address, utility account number or bill. Screenshots in the report show what the visitor typed, so keep real customer records out of the run entirely.
What if the address map does not load on a phone?
The visitor types an address and the report shows what happened next, including any message they saw or the lack of one. If the map needs a sign in or a key a visitor does not have, the visitor stops there. Check the map on a phone in a private window before you run a full test.
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.