By industry
Photography landing page: inquiry form stalls
A parent on a phone likes the portraits, then hits a date field they cannot fill in. Mimiq sends simulated visitors through your inquiry form and shows the field where each one stopped.
Why do photography visitors look at the portfolio and never send an inquiry?
Most visitors to a photography page want to know two things: whether the style fits, and whether the photographer can do their kind of session. The portfolio answers the first question, so visitors keep scrolling, and the inquiry form gives them nothing until they reach it. When the form asks for an exact date, a budget and a shoot type before it says anything about sessions, many visitors leave with the portfolio still open. A simulated test sends a visitor through the same path and shows the field where they stopped.
What this looks like in a report
“I only know it is a September thing and maybe a Saturday. The form wants one exact day before it lets me continue. I will look at the other studios that let me say a month.”
The fix. Let the date field accept a month or a season, with an exact day as optional, and add a line saying the date can be confirmed later. Move the contact link above the gallery so a visitor can send a question before scrolling.
An illustration. Run a test to see your own.See a real sample report
The form asks for a date and a budget before the visitor knows either
A photographer builds the page from the portfolio, because that is the work they are proud of. The visitor scrolls a long gallery on a phone and only then looks for a contact link. Some pages open the gallery in a lightbox that uses the back button to close it, so a visitor who taps Inquire can lose their place. The inquiry form often requires an exact session date, yet a parent planning a family shoot usually knows only the season. A budget menu whose lowest choice sits above what the visitor expects ends the form right there.
- On a phone, can you reach the contact link without scrolling the whole gallery?
- Does the date field accept a month or a season when the day is not fixed?
- Is a budget question required, and does its lowest option fit a small session?
- Does Inquire open the same form, or a second page with a different one?
- After sending, does the page say what happens next and when you will reply?
The gallery is the first screen, and the form is the last
A portrait photographer's page is built to show work, and it does that well. The problem is what sits after the work. A parent who likes the portraits wants to know whether the studio does their kind of session, in their area, before they spend time on a form. If the page offers only the gallery and a footer link, the visitor has to search for the way to ask. Many will not search. Look at your page on a phone and count the screens between the first image and the first contact link. If the number is more than one, the inquiry waits behind the portfolio.
A date the visitor does not have yet
The most common blocker is a required field the visitor cannot honestly answer. A family session is usually planned around a season, a holiday or a relative who is flying in, not around one Saturday in October. When the form insists on an exact date, the visitor must either invent one or stop. Some pick a date and send it, then learn the studio is booked that day. Others close the tab. Test the field with a visitor who has only a month in mind. If the form refuses, the cause is the field, not the portfolio.
Lightboxes, a second form and the Inquire link
Two layout choices make the form harder to reach than the owner expects. Some full screen lightboxes use the back button to close the gallery on a phone, so a visitor who taps Inquire from inside it may land back at the top of the page with their place lost. Another common setup sends the Inquire link to a separate contact page with a different, longer form. The visitor then fills in the same details twice, or decides the page is broken. Check both: tap Inquire from inside the gallery, press back, and see where you land.
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 portfolio section can push the inquire link back below the gallery
Portfolio pages grow. A new session type, a seasonal album or a link to a blog post can add images above the contact link, and the form drops below a screen that a phone visitor does not scroll. Run a visitor after each new album, and again when you add a session type or a location. The run shows whether the contact step is still on the first screen or has moved behind the work again.
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 portfolio visitors will inquire?
No. It does not predict how many visitors will inquire, and it cannot tell you the rate from a page view to an inquiry. It shows the field where a simulated visitor stopped, the link they could not find and the message they saw after sending. For rates, use your site analytics or count the inquiries you receive over a month.
Can a simulated visitor book a session?
No. The run can fill in the inquiry and reach the send step, but a booking is a conversation between you and the client, and the test does not complete it. If your studio takes a deposit by card, the run ends at the payment step, because visitors cannot pay with a real card.
Should I use a real client's name or date in the test?
No. Use made-up names and a test email address. A test does not check your site against privacy rules, and a real client's family details do not belong in a run whose report is saved and shared.
Can a run get past a bot check on the form?
Not always. A bot check or CAPTCHA can stop a visitor, and the report marks that step as blocked by the site rather than as a fault in the form. If one appears on your inquiry form, real clients see it too, so check whether that form needs it at all.
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.