By industry
Restaurant website design: the reserve button
A couple deciding where to eat tonight wants the hours and a table for six before they open the menu. Mimiq sends simulated diners through your site on a phone and shows the step where each one gave up.
Why do people look at a restaurant's website and then book somewhere else?
Diners book somewhere else when a restaurant's site cannot show the hours, the menu and a table for their party within a few taps on a phone. People searching for tonight are choosing with other tabs open, so the first place the page fails is the place they stop. Check the hours, the menu and the booking step for the largest party you seat. A simulated test sends a diner through the same path and shows the step where they stopped.
What this looks like in a report
“Six is the number I have, and the widget jumps from four to eight. I do not want to phone a restaurant in the afternoon just to ask about a table.”
The fix. Add a party size of five and six to the widget, or show a line above the form that says larger parties should call, with the number. Put the hours in the header next to the reserve button, and move the cookie notice so it does not cover that button.
An illustration. Run a test to see your own.See a real sample report
The reserve button sits under a cookie banner on a phone
A restaurant website is often built on a laptop by someone who knows the room. On a phone, the first screen stacks a photo, a welcome line, a cookie notice and the header. The notice can sit across the bottom of the screen, and the reserve or order button sits under it, so the diner sees the label and cannot tap it. Hours often sit in the footer, which may still show last month's schedule. A menu saved as a PDF is hard to scan for prices on a phone. Each one sends a hungry visitor to the next restaurant in the list.
- On a phone at lunch, can you read the hours without scrolling to the footer?
- Does a cookie or consent banner cover the reserve or order button?
- Is the menu text on the page, or a PDF that is hard to read on a phone?
- Does the reservation form offer a party of six, or stop at four?
- If ordering goes to another site, does its name and logo match yours?
Hours and the cookie notice on the first screen
The first screen of a restaurant site has a short job: tell a hungry person that the place is open, where it is and what they can do next. The photo usually takes most of it. A cookie or consent banner, if you have one, arrives at the same moment. On a phone the banner can cover the bottom of the screen, which is where the reserve button often sits. Look at the hours and the button on a phone with a fresh browser, so the banner shows. If you cannot read the hours or tap the button with the banner open, a diner cannot either.
A menu in a PDF, and the party size the widget skips
Two details lose the diner after they have already decided to come. A menu saved as a PDF makes the diner open a separate file, which is harder to scan for prices than text on the page. A menu typed into the page can be read, searched and shared. The reservation widget is the second place. Some widgets list party sizes in fixed steps, such as one to four and then eight. A group of six sees no option that matches and assumes the restaurant does not take them. Select the largest group you seat and check that the widget offers it.
Ordering on another site and the name it shows
Many restaurants send online orders to a third-party ordering page. That page may carry a different name, a logo the diner does not recognize and its own hours. A diner who taps Order and lands on an unfamiliar name may stop, unsure whether they are still in the right place. The same is true of a reservation tool that opens in a pop-up window. Tap your own order link from a phone and check the name, the hours and the menu on the other side. Note the step where the page changes, because that handoff is where a diner decides whether to trust it.
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 PDF or holiday notice can cover the reserve button again
Restaurant sites change with the seasons, the holidays and the staffing. A new menu file, a holiday hours notice or a new ordering link can move the reserve button, the hours or the party sizes. Run the same diner after each change, and check the first screen with the banner open. A changed menu file is enough to bring back a problem you had already fixed.
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
Will this tell me how many diners will book a table?
No. It does not predict how many diners will book, and it cannot tell you covers or revenue. It shows the step where a simulated diner stopped, the hours or party size they could not find and the handoff where they left. For rates, use your reservation tool's reports and your own count of covers for the week.
Can a simulated diner place an order or pay?
No, not with a real card. An order that asks for payment ends at the payment step, because visitors cannot pay with a real card. The run can add items, choose options and reach that step, which shows where the pickup flow stops for a diner who wants to collect their food.
Should I put a real guest's name or phone number into a booking test?
No. Use a made-up name and a test phone number, and do not enter a real guest's details into a booking. A test does not check your reservation tool against privacy rules, and a shared report should not carry anyone's contact details.
Does this judge the food or the photos?
No. It checks whether a hungry diner can find the hours, the menu and the booking step on a phone, and whether the page handles the party they came with. It does not judge how the food tastes or whether the photos look appealing. Ask a few regulars what they remember about the site.
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.