By industry
Videographer portfolio website: lost inquiries
A brand planner needs a launch film shot in two months and wants to see past work before writing to anyone. Mimiq sends simulated visitors through your reels and inquiry form, and shows the step where each one stopped.
Why do potential clients leave a videographer portfolio website without sending an inquiry?
They leave when the work loads slowly or does not play on a phone, when an embedded film shows a private-video message, or when the inquiry form asks for a budget range and a shoot date before the visitor has described the project. A planner comparing several videographers moves on to the next portfolio. A simulated test opens the reels on a phone, plays a film, fills in the inquiry as a client would, and shows the step where each visitor stopped.
What this looks like in a report
“The second film wouldn't play on my phone and showed a private video message. The form wants my budget range and a shoot date, and I don't know either yet. I'll try the next videographer.”
The fix. Replace any embed that shows a private message with a film your team controls, or with a still and a link that opens in a new tab. Move the budget field to the end as optional, and ask what is being shot and when before anything else.
An illustration. Run a test to see your own.See a real sample report
The first film decides whether the visitor stays to inquire
A stranger on a portfolio site usually arrives with a specific shoot in mind: a product launch, a wedding, a training film for staff. They open a grid of thumbnails and tap the first one. On a phone, the film may load so slowly that the visitor leaves before it plays, or the page may show a blank frame with no sense of progress. Some pages embed films from a video host that was set to private, so the visitor sees an error where the work should be. Then the inquiry form asks for a budget range and a date before anything about the project has been described.
- Does the first reel start within a few seconds on a phone, with a still image while it loads?
- Does each embedded film play for a visitor who is not logged in to the video host?
- Can the inquiry be sent with the budget left blank, and a rough range offered as an option?
- Does the form ask what is being shot before it asks for a date?
Reels that stall before the first frame
A film is the portfolio. Everything else on the page exists to get a visitor to press play and stay for the length of a cut. On a phone, that takes a fast connection and a page that shows something useful while the file loads. Many portfolio sites load a grid of large video files at once, so the first film waits behind the rest and the visitor sees a blank frame. Check the grid on a phone on a weak connection, which is how a planner between meetings will see it.
Show a still frame from each film at the same size, and load a single film only when its tile is tapped. Put the film a planner is most likely to want first, such as a launch or a corporate piece, in the first tile. Keep the tile layout fixed so the page does not jump while the images arrive. The run records slow requests on the step where they happen, so a heavy film file shows up under the reel it belongs to.
An embed that tells the visitor the film is private
Many portfolio sites host films on a video service and embed them in the page. An embed works only if the film's privacy setting lets a stranger play it. A film left as private, or set in a way the embed does not allow, shows the visitor a message about access rather than the work. A visitor with no account sees a locked box, and that is the moment a planner decides the videographer is not organized enough for a launch. Open each embed in a private browser window, with no account, and see what plays. Where a film has to stay private, add a line above the locked item that says the reel is shared on request.
An inquiry form that asks for a budget before a project
A planner with a launch in two months often has a date and a rough idea of the film, but no budget they can defend yet. A form that opens with a budget range, a shoot date and a production type asks for all three before the project has been described. Some visitors pick the lowest range to keep the conversation open, and others leave because no range fits. Read the form once as someone with a spring launch and no confirmed dates, then count the fields they cannot answer honestly.
Ask what is being shot, where and for whom first, in a single sentence. Make the budget and the date optional, with a line that says a rough range helps the videographer suggest a crew size. A simulated visitor can reach the inquiry and report which field it stopped on, and the report names both the field and the step.
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 reel at the top can push the inquiry button below the first screen
Each new reel added to the top can push the inquiry button down, change the grid order or bring back a private embed. Run a planner through the portfolio and the inquiry after every addition, on a phone, and check that the film still plays for a visitor with no account. A client gallery behind a password needs a test password you give the run, so it reaches the reels inside.
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
Does the test tell me how many inquiries the site will bring in?
No. The test cannot tell you how many inquiries the site will bring in, and it does not predict how many would become paid shoots. It shows whether a planner can play a film, read the work and reach the inquiry form. Inquiry counts come from your contact inbox and form records.
Can the test judge whether my films are good?
No. It cannot judge the cutting, the color, the sound or the story in a film. It reports whether a film plays, where a slow request held up the page, and where a visitor stopped. The quality of the work is a matter for you, your clients and your own review.
Can the test send an inquiry with a real client's details?
No. Use invented names, a made-up company and a test address. A client's name, schedule or unreleased project should not sit in a test form, and the report should not carry them either.
Will the run play a film on a password-protected client page?
Yes, if you give the run a site password for a protected preview. Without that password the run stops at the lock, and the report says so. Use a password that exists only for the test.
Does the test confirm that a client receives the inquiry reply?
It confirms that the form shows a success state, and that a visitor's inbox receives any confirmation the form sends. It does not check how your team replies to the client.
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.