Before you launch or pay for traffic

Home page checklist: the first screen, checked

A home page gets read as a stack of blocks, and a stranger needs one clear next step. This checklist covers the blocks in the order a visitor scrolls past them, and simulated visitors show where each one stops.

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

What should a small business home page show before it goes live?

It should say what the business does and where it is in the first screen, then give one next step that suits most visitors, such as calling, booking or asking a question. The hours, address and phone number need to be easy to find without a second scroll, and a slider should not hide the main offer behind a second slide. A simulated test walks the home page the way a stranger scrolls and shows the block where each visitor stops and what they were choosing between.

What this looks like in a report

Who
Dario, who needs a dog groomer before a trip on Friday
How they arrived
Searched for dog groomers in his town and opened the first result on his phone
Where they stopped
Home page, after the banner rotated to slide two

“The button under the banner goes to a booking page for nail trims, and I need a bath before Friday. The phone number must be at the bottom, under six blocks I have already skipped.”

The fix. Point the banner's button at the bath booking, and put the phone number and the hours above the services list on a phone. Then open the home page on a phone, wait through one full banner cycle, and confirm each slide's button leads to its own offer.

An illustration. Run a test to see your own.See a real sample report

Seven blocks that each ask for a different action

A small business builds its home page one section at a time: a banner, a list of services, a booking button, a gallery, a map, a newsletter box and a footer with the hours. Each block was added for a reason, and the owner reads each one as a separate job to finish. A stranger does not read it that way. They see the blocks as competing choices, and when every block asks for a different action, the visitor picks none of them and leaves to find a site that asks for one.

  • Business name, what it does and the town, all visible before the first scroll
  • One main button, and no more than two secondary links in the first screen
  • Opening hours and phone number on the first screen, or one tap away on a phone
  • Slider: can a visitor who never touches the arrows still see the main offer?
  • Map, chat bubble or booking widget: does it cover the phone number or the address?

Count what the first screen asks a visitor to do

Start with the first screen on a phone and count the actions in it: the banner button, the booking link, the call button, the newsletter field, the chat bubble and the menu. A visitor does not count them. They feel a crowd, and the one that looks like a shortcut gets the tap. For a small business the shortcut is usually the phone number, so the number belongs on the first screen next to the name and the town. If the list has more than one main button, decide which one a stranger should press first, and turn the others into plain text links.

Rotating banners put the main offer on a timer

A slider does not show all its slides at once. The first one fills the frame when the page loads, and later slides appear on a timer or when a visitor presses an arrow. A visitor who reads slide one and then scrolls never sees slide two, and a slide three with a link to a different service may never get a look. Check two things. The first slide should carry the offer you most want seen, and the button on every slide should lead to the page that slide describes. Then open the page on a phone, do nothing, and wait through one full cycle.

Hours and address that only appear in the footer

Small business sites often put the opening hours and the address in the footer, under the gallery, the reviews and the newsletter box. A stranger who wants to know whether the shop is open on Saturday has to scroll through every block to find them. On a phone the footer can also sit behind a fixed bottom bar, so the hours are in the page source but never on the screen. Open the home page on a phone and count how many screens it takes to find the hours without opening the menu. If the answer is more than one, move the hours up.

A chat bubble that sits over the phone number

Floating chat buttons, booking widgets and map embeds are added by other tools, and each one places itself by its own rules. A chat bubble is usually fixed to a lower corner, so it stays on top of whatever scrolls beneath it. On a phone that means the call button or the phone number in the footer can pass under the bubble as the visitor scrolls down. A map embed can fill the whole screen and take over the scroll for a visitor who touches it. Check each widget on a phone in portrait, scroll to the footer with the widget open, and confirm the number can still be tapped.

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.

A seasonal banner can cover the phone number on the next holiday

Small business home pages change with the season: a banner for a sale, a closure notice for a holiday, a booking widget a supplier adds. Each change can push the hours or the call button out of the first screen. Walk the home page on a phone after each change, and compare where the visitors stop with the last run. A closure notice should be checked with the regular opening hours beside it.

Starter

Try it on one launch

$9 once
120 credits, never expire

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
Buy 120 credits

Builder

Test every build

$19 a month
500 credits every month

About 20 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Builder

Pro

Test every release, as a team

$49 a month
1,500 credits every month

About 60 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Pro

Scale

Test at scale, every day

$149 a month
6,000 credits every month

About 240 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Priority support
  • Cancel anytime
Choose Scale
$0for your first test, with a free account (Google sign-in, 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 many blocks should a small business home page have?

Few enough that a stranger can name the first action after one look. A banner, a short list of services, the hours and one contact route usually do the job. Add more blocks only when visitors already ask for them, such as a gallery for a salon or a menu for a cafe.

Can the test tell me whether my services are right for the business?

No. It shows whether a visitor can see what you do, find the next step and reach the phone number or the form. It does not judge your prices or your market, and it does not predict how many visitors will call.

Should the home page have a booking button or a contact form?

Put the route that matches the first question the visitor brings. A booking button fits a business where people reserve a time. A contact form fits a service that quotes each job. Test the route on a phone before you decide, because a form that asks for too much loses the visitor the button was meant to win.

Do I need to test the home page after every change?

Test it after any change to the first screen, the banner, the menu or a widget. A short walk on a phone is enough to catch a new widget that covers the number.

What does a simulated visitor see that I cannot?

The home page the way a stranger first meets it, without your login, your cookies or your memory of where the button sits. It reports the step where each visitor stopped, with a screenshot of that step.

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.

5 visitors try to .