Test a page or flow
Check my new website before you share it
You know every page, so you skip the parts that make no sense to someone who has never seen the site. A stranger finds those parts first, usually on the first screen.
How do I check my new website?
Send someone who has never seen it through the site with one job in mind, and watch where they stop, click the wrong thing or ask what the product is. Follow every link in the menu and footer, every form, and the page a shared link opens on. A simulated test adds visitors who read each page from the first load with no context, and report the step where each one lost the thread.
What this looks like in a report
“The headline says streamline everything, which could mean anything. There is a block of lorem ipsum under it, so I am not sure this is finished. I will check back later, or not.”
The fix. Replace the placeholder block under the headline with a short line that says what the product does for a named customer, and remove the lorem ipsum text from the page. Then open the homepage as a new visitor and check that the first screen says what the product is.
An illustration. Run a test to see your own.See a real sample report
The first page a stranger lands on is the one you read last
A new site has a few things an owner stops seeing. The homepage still has a section you meant to replace, the pricing link goes to a page you have not written, and the footer has a hash link that jumps nowhere. The owner reads past all of it, because they know what each piece is for. A visitor arrives from a message with no history, reads the headline, looks for the product, and leaves at the first placeholder they cannot make sense of. You cannot see that from inside, because you already know the answer to every question the page asks.
- Read the homepage headline and say out loud what the product does, without scrolling.
- Follow every link in the menu and footer, and note any that goes to a blank or hash page.
- Look for placeholder text, lorem ipsum, and buttons that go nowhere.
- Share the link in a chat app and check the preview title and image a stranger sees.
Walk the site as someone who arrived from a share
Open the link the way a stranger does, from a message, with no menu or history in front of you. Read the first screen and write down, in one sentence, what you think the company sells and who it is for. Then click the first thing that looks like a next step, and keep going until you reach a form or a dead end. Repeat the walk from the sign-up page and from the menu, because visitors arrive on pages that are not the homepage, and a shared link can open on a blog post or a pricing page. Note every moment you had to guess.
The empty parts a new site leaves behind
A new site collects unfinished pieces: a team page with one photo, a case study that says coming soon, a contact form whose messages go to an inbox nobody has set up yet, and a thank-you message that never appears after submit. The owner skips past each one, because they know the form works once the inbox is connected. A stranger who sends a message and hears nothing back has no way to know that, so they assume the company is not answering. Check each form by submitting it with an address you can read, and check that the confirmation a visitor sees is the one you meant them to see.
Pages you built and never linked
Some pages exist only because you typed their address. A pricing page or a demo page built last week may not be in the menu, the footer or the homepage yet, so a visitor who starts at the homepage never finds it. Test by starting from the homepage and trying to reach each page with the menu alone. A page you can reach only by typing its address is one a stranger will not reach, so either link it or remove it before you share the site.
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 menu link added after launch can point to a page not built yet
New pages and menu links keep arriving after launch, and each one can point at a page that is not built, is empty or is hidden from the menu. Rerun the same visitors on the homepage and the sign-up path after each addition, and check the menu link on the path they took. A run behind a login uses a test account you give it, so the signed-in parts of the site are checked too.
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
Who should look at my new site?
Someone in the group you want as customers, who has not seen the site before. A friend who already knows what you do fills in the gaps without noticing them. Simulated visitors take their profile from a description you write, so the description decides who they are. Write it for the person who would actually pay.
Does a clean check mean the site will get visitors?
No. The check shows whether a visitor who arrives can understand the site and reach a next step. It does not predict how many people will arrive, or how many of them will sign up. Traffic and sign-up rates come from your analytics, once real people are visiting.
Should I check every page or only the homepage?
Check the homepage, every page a link on it leads to, and the page a shared link opens on. Pages you never link do not get found by a stranger, so check them by typing the address and by finding them from the menu. A page only you can reach is a page you have not finished.
What do I do with feedback that feels harsh?
Take the step, not the tone. A visitor who says the headline could mean anything has told you which words to change. Fix the headline where the visitor stopped, then rerun the same visitors and compare the step they reached.
Can I run the check before the site is live?
Only with a public address. Visitors run in a browser at a public address, so a staging or preview link works, and a site that sits behind a private network does not. If the site needs a password, you give the visitors that site password with paid credits, and they enter it the way a stranger would.
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.