By industry

Senior living website design: tour requests

An adult child searching late at night wants to know whether a community can help a parent bathe and dress. Mimiq sends simulated visitors through your care pages and tour form, and shows the step where each one stopped.

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

Why do families leave a senior living website before they request a tour?

They leave when the care levels are named in terms a family does not use, when the tour form asks for medical details before a visit is offered, or when the page gives no sense of cost and only asks them to get in touch. Families often compare several communities in one sitting, so one hard step sends them to the next result. A simulated test takes the path a family member would, reads the care pages, starts a tour request and shows the step where each visitor stopped.

What this looks like in a report

Who
Ngaio, lives two hours away and is looking at places for her father
How they arrived
Opened a senior living community website from a search she ran late at night
Where they stopped
Tour request form, after reading the care levels

“I need to know if they help with bathing and whether he can keep his cat. The form wants his diagnosis before it gives me a tour time. I'm not typing that into a website at midnight.”

The fix. Describe each care level with the daily tasks it covers, and put the tour dates above the form rather than after it. Ask only for the family member's name, a way to reach them and a preferred visit day, and move health details to a step after the visit.

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

Care levels named in terms only the staff use

A family member searching for senior living does not start with assisted living or skilled nursing. They start with a parent who needs help getting in the shower, or who keeps forgetting the stove. Many community websites sort their care into named levels, each with a clinical label, and the difference between them lives in a paragraph the visitor has to read on a phone. The visitor cannot tell which level fits their parent, and may not know the level names exist. Next comes the tour form, which asks for a diagnosis and a list of medications before it offers any date, so the visitor stops.

  • Does the care page describe each level in daily tasks, such as bathing or meals, before the label?
  • Can a visitor see a tour date or a weekday window before the form asks for health details?
  • Is the cost described in words, with what it includes, rather than a line saying to ask?
  • Is the text large enough to read on a phone without zooming, with buttons a thumb can reach?

Care levels described in labels instead of days

Senior living sites have a vocabulary of their own, and a family outside the industry has to translate it. A care level may be named for the setting, the staff training or the type of support, and the names do not always tell a reader how much help a resident gets. A father who needs help with bathing and dressing every morning may fit a different level than one who only needs meals and reminders, and the page does not always say so. Read the care section as an adult child holding a list of daily tasks written on the back of an envelope. Check whether each level answers the question of which tasks it covers.

Rewrite each level as a short list of the daily tasks it includes, then add the label in brackets for the staff who use it. A visitor who sees 'Help with bathing, dressing and medication reminders' can match it to their parent in seconds. Keep the medical terms, because a discharge planner will expect them, but let the plain description come first.

A tour form that asks for a diagnosis before any visit

A tour is the next step a family can take, and the form for it should be easy to finish on a phone in a parking lot. Many forms ask for a diagnosis, a list of medications, a mobility score and insurance details before they offer a visit date. Those fields belong to an assessment, and an assessment is a reasonable conversation for the community to have. It is an unreasonable first question on a website. A visitor who cannot give those details yet has no way to request a tour, so they request one from the next community on the list.

Ask for the family member's name, a way to reach them and the day they would like to visit. Let the visit happen first, then send a short health form by email for the staff to review before any move-in. A simulated visitor reaches the form and reports which field it could not answer, so you can see the stop without any real family's details being entered.

Base rent and care fees the page never explains

Families compare communities by monthly cost early. Some communities bill in two parts, a base rent for the apartment and a care fee that depends on the care level, and a page that names only the base rent makes the total impossible to estimate. The visitor cannot tell whether a community is within reach, so they cannot tell whether a tour is worth the time. Explain both parts in words, with what each one covers, then look at how the cost section reads after a visitor has already read the care levels.

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 care level or a rewritten tour form can reset the first screen

Communities add care levels, rename units and rewrite tour forms each year, and one change can push the tour button below the fold or bring a health question back to the first screen. Run the same family visitor through the care pages and the form after every change, and check the phone view. A page behind a resident portal or login needs a test account you give the run, so it reaches the tour form.

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 tell me how many families will request a tour?

No. The test cannot tell you how many families will request a tour, and it does not predict how many of those tours would lead to a move-in. It shows whether a family member can understand the care levels, find a visit date and reach the request form. Tour counts come from your inquiry records.

Can the test enter a real resident's health details?

No, and it should never be given them. Use invented answers, such as a made-up parent's name and a fictional need for help with dressing. Real health information belongs in a secure intake process, not in a test.

Does the test check whether the community is licensed or meets care standards?

No. The test reads the words on your site and follows the steps a family takes. It does not check licenses, inspections or care standards, and nothing a simulated visitor reports replaces your own records or any inspection.

Will the test show whether older readers can use the site?

It shows whether the text and buttons are reachable at phone width, and where a visitor stops. It is not a full accessibility audit. A review by people who use assistive tools will find more.

Can the test follow a tour confirmation email?

Yes, when the form sends one. A visitor has a working inbox, so the run can open the confirmation and follow any link in it. The test does not judge the wording of the message.

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 .