By industry

Optometrist website design: exam or glasses?

A man whose glasses no longer sit right wants an eye exam next week, but the first big button sends him to the frames. Mimiq sends a simulated visitor along the same route and shows where the exam path broke off.

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

Why do people leave an optometrist website without booking an eye exam?

Often the site offers two things at once, an eye exam and a shop for frames, and the visitor takes whichever the homepage shows first. The booking then asks for a reason for the visit and for details they may not have, such as the numbers on their prescription, before it shows any time. A simulated test starts at the homepage, asks for an exam next week, and shows the step where the visitor could not continue.

What this looks like in a report

Who
Walt, 62, whose glasses have felt wrong for a month and who wants an exam next week
How they arrived
Opened the practice's homepage from a map listing on his phone
Where they stopped
Reason for visit list, after tapping book an appointment

“I need an exam for new glasses, but this list says contact lens fitting, eye concern and eyewear adjustment. I cannot tell which one is the exam, and I do not know my numbers. I will try another practice.”

The fix. Rename the reasons in plain words, such as eye exam for new glasses, and say what each one includes. Let a visitor choose I do not know my prescription and still see exam times, with the numbers taken at the visit.

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

The frame shop and the eye exam compete for the same first screen

A visitor whose glasses have stopped working has one goal: an exam. The homepage often gives the frame shop the most room, with bright photos of frames, a Shop now button and an eyewear banner. The exam button is smaller, and sometimes it sits in the menu. A visitor who taps Shop now finds frames with prices but no appointments, and has to search again for the way to book. Some decide the practice does not do exams. Others find the exam link and meet a reason-for-visit list that does not say which option they need.

  • Is booking an eye exam one of the first two buttons on the homepage, on a phone?
  • Is the frame shop link set apart from the exam link, with different words?
  • Does each reason for visit say what it covers, such as a new prescription or a contact lens check?
  • Does a reason change the times shown, and does the page say so?
  • Can a visitor say they do not know their prescription and still see an exam time?

Two products on one homepage

A practice that sells frames and runs exams gets two kinds of visitor on one page. One is browsing frame styles and may book nothing. The other has a deadline, often because their glasses broke or stopped working, and needs an exam within a week or two. Their paths split at the first click. When the frame shop takes the top of the page and the exam link is a small word in the menu, the second group is the one that leaves.

Check the split on a phone. Count the taps from the homepage to a page that lets you book an exam, and write down which button you pressed first. If that button led to frames, the homepage is sending exam visitors into the shop. The test does the same walk from the homepage, so you can see the route a visitor took and the screen that turned them around.

A reason for visit that changes the calendar

Exam booking pages often ask why the visit is needed, and the answer often decides which calendar the visitor sees. A contact lens fitting may need a longer slot, a different room or a particular optometrist, so the times for that reason are different from the times for a routine exam. A visitor who picks a reason that is not theirs can find no times at all, and reads that as the practice being full.

Pick each reason on the list in turn, for the same week, and write down the times each one shows. If one reason shows nothing for next week and the others show plenty, the cause is the reason's calendar, not the week. Then read what each reason says on the page. A reason with no description forces a visitor to guess which slot they will be booked into, and many will not guess.

Prescription numbers a visitor cannot read off

Some forms ask for the numbers on a current prescription, along with the date of the last exam. Many people do not know what those numbers mean, and some do not have the paper in front of them when they book. A field that must be filled before a time is shown will stop a visitor who is unsure, and a visitor who is unsure is usually the person who needs the exam most.

Test this on purpose. Start a booking, pick a reason, and stop at the first prescription field. If the next button stays grey, the field is required and the page has no way out for someone who does not know the numbers. The fix is not to remove the question. Make it optional for a first exam, say that the numbers are measured at the visit, and show the next free time straight away.

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 new frame range can push the exam link off the homepage

A new frame collection, a seasonal sale or a new banner can move the exam button below the first screen or rename it. A new reason for visit can also change which times show for everyone. Run the exam path on a phone after each homepage or booking change, for each reason on the list, and again before a sale starts.

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

Does the test show how many exams I will fill?

No. Mimiq does not predict bookings, and a simulated visitor is not a patient. It shows whether the exam path is easy to find, which reason gives which times, and the step where the visitor stopped. Booking counts come from your scheduling system and your practice records.

Can a simulated visitor book an exam all the way through?

Up to the step that needs a text code or a real card. A visitor cannot receive a text, so a booking that sends a code stops there. A deposit ends the run at the payment step. The report shows the last screen the visitor reached, so you know which step to change first.

Will the test tell me whether a vision plan covers the exam?

No. The test can show whether the page says which plans you accept, and whether a visitor can find that line. It cannot check your plan contracts or what any plan covers for a patient. Confirm those with each plan and with your front desk, not with a simulated visitor.

Should I put a real patient's prescription into a test?

No. Use invented prescription values, or leave those fields empty if the form allows it. Never type a real patient's record into a test, and do not upload patient lists. A test does not check your forms against health privacy rules.

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 .