Guide

How to test a website before launch: a checklist

A website launch fails in boring ways: a form that emails nobody, a staging setting that hides the site from search, a signup nobody outside the team can finish. This checklist covers what to test before launch day, which kind of tool fits each check, and which checks need people or simulated visitors.

5 visitors try to .
First test free with an accountRun it from your coding agent

How do I test a website before launch?

Work through six areas: links and forms, speed on a phone, accessibility basics, search and sharing settings, analytics, and whether a newcomer can do the main task. You or automated tools can run the first five. The last needs someone who has never seen the site, a real person or a simulated visitor, trying to use it.

Why launch day bugs are always the boring ones

Teams test the features they built and skip the plumbing around them, because it worked last time. The contact form still sends to an old address, the staging block on search engines ships to production, the analytics tag fires twice. None of it is hard to catch. It just needs a list and an afternoon.

  • A checklist grouped by area, with the kind of tool for each check.
  • The settings that most often ship by mistake from staging.
  • Which checks a tool can do, and which need a person.
  • Where simulated visitors acting as newcomers fit, and where they are the wrong tool.

How it works

  1. 01

    List the key pages and one core task

    Usually the homepage, pricing, the signup or contact page, and the main thing a new visitor should be able to finish, such as signing up or booking a demo.

  2. 02

    Run the technical checks

    Crawl for broken links, submit every form, and load the key pages on a phone over mobile data.

  3. 03

    Check accessibility basics

    Run an automated checker, then go through the core task with the keyboard alone and check that images and form fields are labeled.

  4. 04

    Check search, sharing and tracking

    Remove any staging block on search engines, check titles and share previews, and confirm that your analytics record a visit and a signup exactly once each.

  5. 05

    Watch newcomers try the core task

    Have people who have never seen the site try it, or send simulated visitors through it, and fix the step where they leave or what breaks.

  6. 06

    Watch the first days

    After launch, check error logs, form submissions and analytics daily for a while. That is when the problems nobody predicted show up.

Links, forms and email

Crawl the site with a link checker and fix every broken link and redirect loop. Then do by hand what a crawler cannot: submit every form with an address you can read, and check that the thank you page appears and the confirmation email arrives, outside the spam folder.

Check where form submissions go. A contact form wired to a test inbox or a colleague who has left is one of the most common launch day failures, and nobody notices until a customer asks why you never replied.

Try the error cases too: an invalid email, an empty required field, a password that breaks the rules. Each message should say what is wrong and how to fix it.

Speed and devices

Load the key pages on a real phone over mobile data. Lighthouse, built into Chrome's developer tools, reports speed, layout shifts and basic accessibility in one run, and points at the heaviest images and scripts.

Check the pages in at least one browser nobody on the team uses every day. Layout bugs like to hide there.

Accessibility basics

Automated checkers catch a useful share of problems, such as missing alt text, unlabeled form fields and low contrast. They cannot tell you whether the site is usable with assistive technology.

So also do a manual pass: complete the core task with the keyboard alone, check that the focus is always visible, and check that headings describe the page in order. For a real answer on screen readers, test with people who use them every day. Simulated visitors, including Mimiq's, cannot stand in for that.

Search, sharing and tracking

Staging settings ship by accident. Check that no page carries a noindex tag or a robots.txt rule left over from staging, that each key page has its own title and description, and that a sitemap exists. Then paste a link into a chat app to see the share preview.

Open your analytics in its debug or real time view, visit the site, and complete the core task once. Each step you care about should record exactly once. Double-counted signups make a launch look better than it is, and missing ones make it look worse.

Check the legal basics that apply to you, such as a privacy policy and, in some countries, consent before analytics cookies are set.

Can a newcomer do the main task?

Every check above can pass and the site can still lose people, because the team cannot see it fresh. The only test for this is someone who has never seen the site trying the main task, with nobody explaining anything.

A few real people from your audience are the gold standard. Simulated visitors are the fast version. In a Mimiq run, each visitor opens your site in its own real browser, on a laptop or a phone, and tries a task such as 'Sign up and start using it', clicking, typing and filling in forms, with an email inbox of its own for verification links. The report shows how far each one got, what was broken, and where and why it left.

Start a run on each key page, such as the homepage or the pricing page, to see whether newcomers can get from there to the main task. A GitHub Action can repeat the check on every preview deploy. It does not replace the technical checks above: simulated visitors find breaks and confusion on screen. They do not find broken tracking.

What simulated visitors cannot check

They cannot use Google or other social sign in providers, or pay, so a run ends before payment. A CAPTCHA can stop them. Any visitor stopped by one is marked as blocked by the site, and if it stops every visitor, the run fails and nothing is charged. A staging or preview address without bot protection works, as long as it is public or you give access. With paid credits, visitors can sign in with a test account you give them and open protected previews (a Vercel bypass secret or a site password). The secrets are filled in only in the browser and deleted when the run ends. Test accounts and protected previews come with paid credits: the $9 Starter or a plan from $19 a month.

They flag slow steps and requests encountered during the run, but do not replace a dedicated performance audit, accessibility testing, SEO checks or analytics validation. And they are simulated: a run shows where visitors like yours can get stuck. It does not predict how many real visitors will convert.

Pre-launch checks by area

AreaWhat to checkWho or what checks it
Links and formsEvery link resolves; every form submits and reaches the right inbox; errors say how to fix themA link checker, then you by hand
SpeedThe first screen on a phone over mobile data; heavy images and scriptsA speed report such as Lighthouse, and a real phone
AccessibilityKeyboard-only use, labels, contrast, alt textAn automated checker, a manual pass, and people who use assistive technology
Search and sharingNo leftover noindex; titles, descriptions and a sitemap; share previewsThe page source, and a link pasted into a chat app
TrackingEach key step records exactly onceYour analytics debug or real time view
Newcomer usabilityA stranger can finish the main task and understands each key pageReal people from your audience, and simulated visitors for a fast first pass

What you get with Mimiq

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

$0for your first test, with a free account (Google or email, no card). It includes 50 credits, enough for 10 visitors. After that a visitor uses 5 credits, and packs start at $9 for 120 credits.
See a sample report

Questions

How long before launch should I test?

Run the full list a few days before launch, so there is time to fix what it finds, and the quick checks again on launch day after the final deploy. Settings change between staging and production.

What do teams forget most often?

A staging block on search engines left in place, and forms that send to the wrong inbox. Both are invisible from inside the team, and both cost real traffic and real leads.

Can I test a website before it is public?

The technical checks, yes, on a staging site. Mimiq needs an address it can reach, because a real browser opens it on Mimiq's side; a staging or preview address works as long as it is public and has no bot check in front of it. With paid credits you can also give the visitors a bypass secret, a site password or a test account.

Is a usability test the same as QA?

Mimiq combines exploratory bug finding with a newcomer's path through the page. Pair it with deterministic QA, performance tooling and real user research for coverage beyond the visitors' run.

What does a check with simulated visitors cost?

Your first test is free: sign in with Google or email and it starts right away. A free account includes 50 credits, no card. After that, a run uses 5 credits a visitor, so 5 visitors use 25, and it is a $9 Starter (120 credits that never expire) or monthly plans from $19.

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.

5 visitors try to .