Guide
How to test a landing page before launch
Before launch you cannot measure a conversion rate, but you can find most of what will hurt it. This guide covers the checks that need no traffic: a technical pass, a message pass, and outside eyes on the page, including where simulated visitors help and where they do not.
How do you test a landing page before launch?
In three passes. First a technical pass: open it on a phone, click every link, submit the form and check that tracking fires. Then a message pass: can a stranger say what you sell, who it is for, why to believe it and what the button does? Then outside eyes: people from your audience, or simulated visitors that try to use the page, to find the breaks and objections you cannot see yourself. Measure conversion only once real traffic arrives.
Why testing before launch gets skipped
The usual plan is to launch, buy some traffic and watch the numbers. That costs money, takes weeks to reach a clear answer, and still does not say why people left. Most of the problems that sink a landing page are visible before launch, if someone who has never seen it looks at it with a reason to leave.
- A technical pass you can do in an hour, with nobody else involved.
- Five questions every stranger should be able to answer from the first screen.
- Ways to get outside eyes on the page, from free to paid, and what each one misses.
- How to retest after a fix, so you know the fix worked.
How it works
- 01
Name the one job
Write down who the page is for and the one action it asks for, such as starting a trial or joining a waitlist. Every check below is measured against that action.
- 02
Do the technical pass
Open the page on a phone over mobile data, click every link and button, submit the form with an address you can read, and check that the confirmation arrives and your analytics record it.
- 03
Do the message pass
Read only the first screen and answer the five questions below as a stranger would. Anything you cannot answer from the page itself is a gap.
- 04
Get outside eyes
Show it to people who match your audience, or send simulated visitors through it, and collect what stops them. In a Mimiq run, 5 simulated visitors land on the live page and try to sign up, in about 5 to 15 minutes.
- 05
Fix one thing and retest
Fix the problem most people hit, then show the new version to the same people or visitors, so the only thing that changed is the page.
What you can learn before launch, and what you cannot
A conversion rate needs real visitors arriving from real channels, so no test before launch can give you one. A tool that quotes a predicted rate for a page nobody has visited is claiming more than it can know.
What you can learn is whether the page does its basic job: a stranger understands the offer, believes it enough to keep reading, and knows what the button will do. Those failures are common, they are visible on the page itself, and they are cheap to fix before money is spent sending people to it.
The technical pass
Open the page on a phone, on mobile data rather than office wifi. Note how long the first screen takes to appear and whether anything jumps around as it loads. Lighthouse, built into Chrome's developer tools, gives a quick read on speed and basic accessibility.
Click every link and button. Submit the form with an address you can check, and confirm that the thank you page and any confirmation email arrive. Then check that your analytics or ad platform recorded the signup, because a page that converts without tracking looks exactly like a page that does not convert.
Check the share preview too. Paste the address into a chat app or a social post draft and see which title, description and image appear. Plenty of launch posts go out with a blank or placeholder preview.
The message pass: five questions
What is it? From the main heading and the line under it, a stranger should be able to name the kind of product. If your main heading could sit on a competitor's page unchanged, it is not doing this job.
Who is it for? Visitors decide fast whether a page is meant for someone like them. Name the audience or the situation, not "teams" or "everyone".
Why believe it? Every claim needs something behind it: a screenshot of the real product, a specific example, a customer you actually have, or a number you can defend.
What does it cost, and what is the catch? Missing pricing reads as expensive, or as a sales call. If you cannot show a price, say how pricing works and what the first step costs.
What happens when I click? "Get started" says nothing. Say what the button does and whether a card is required.
Getting outside eyes on the page
You already know what the product does, so you cannot see the page cold. Colleagues and friends cannot either, and they are polite. The useful reader matches your audience and owes you nothing.
Watching a few people from your audience try to make sense of the page, while you stay quiet, catches the rest. It uses real people and takes some organizing.
Simulated visitors are the fastest option. In a Mimiq run, visitors matched to your audience land on the live page in real browsers on laptops and phones, try to do what it asks, such as signing up, and say where and why they left. Tell Mimiq which ad or search keyword they came from, and the report compares it with the page. The problems come back ranked by how many visitors hit them, each with the steps, a screenshot and a fix to copy into a coding agent. They find what breaks and what confuses. They do not predict how many real people will convert. Treat what they report as a list of likely problems to check.
Retest so you know the fix worked
After a change, show the new version to the same readers. If different people see each version, you cannot tell whether the page improved or the readers changed. In Mimiq, send the same visitors through the new version with the same task, and read the two reports together: who got further, and which problems went away.
Read the reasons more than the counts. A handful of simulated visitors are not a traffic sample, so the useful part of a rerun is which problems went away. It says nothing about which version converts better.
Change one thing at a time where you can. If the main heading, the hero image and the pricing all change at once, a better result does not tell you which change helped.
After launch: measure
Once traffic arrives, real behavior beats any test before launch. Watch where visitors drop off in your analytics, look at recordings of sessions that ended early, and, with enough traffic, run a live experiment on the questions the pre-launch checks could not settle.
Keep testing each new version before it goes live. It clears what is broken first, since each live test costs weeks of traffic. A GitHub Action can run the same check on every preview deploy.
Ways to test a landing page before launch
| Method | Who looks at it | Good for | Misses |
|---|---|---|---|
| Self review with a checklist | You | Broken links, missing pricing, vague buttons | Anything you cannot see because you know the product |
| Friends and colleagues | People who know you | Typos and obvious confusion | Honest objections; they are rarely your audience |
| Five second test | Real people, often from a panel | Whether the first screen says what it should | Trust, pricing and anything below the first screen |
| Watching a few people | Real people from your audience | Where real people get confused, in their own words | Speed: it takes days to recruit and schedule |
| Simulated visitors | Simulated people matched to your audience | What breaks and where visitors leave when they try the page, and why, repeatable after each fix | Real behavior and exact numbers; weaker for niche experts |
| Live experiment | Your real visitors | Which version actually converts better | Needs traffic and time, and says what, not why |
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.
Questions
How many people do I need to test a landing page?
For finding problems, not many. A handful of people from your audience usually surfaces the biggest issues, because the same problems keep coming up. Measuring a conversion rate is a different job, and it needs real traffic.
Can I test a landing page that is not live yet?
A real browser has to open it, so a public preview or staging address works for a Mimiq run, and with paid credits a protected preview does too. If it is still a design, go through the five questions yourself first.
Should I run a live experiment before launch?
You cannot, in the usual sense: a live experiment needs real visitors. Before launch, check versions with outside readers, real or simulated, and save the live experiment for the questions they cannot settle once traffic arrives.
What is the most common landing page problem?
A main heading that does not say what the product is. When strangers cannot tell what is being sold in the first seconds, most other fixes do not matter. After that come a missing price, a button that says nothing, and a form that fails.
How long does a test with simulated visitors take?
A Mimiq run with 5 visitors takes about 5 to 15 minutes. Your first test is free: sign in with Google or email and it starts right away. A free account includes 50 credits, no card.
Keep reading
Send visitors and see what breaks first.
Your first test is free: sign in with Google or email and it starts right away. Last checked 2026-11-01.