By platform
Wix form not working: find the failing step
The form looks right in the editor, but a stranger presses send and nothing comes back. Simulated visitors send it from a clean browser and show the step where the send stops.
Why is my Wix form not working for visitors?
A Wix form that works in the editor can still fail on the live site, because the editor shows your draft and visitors see the version you last published. The other usual causes are a form inside a pop-up or hidden section that a visitor cannot reach, a required field the visitor cannot see, or a notification that goes to an address nobody reads. Find out which by pressing send from a clean browser and reading what the form shows afterward. A simulated visitor fills in the form as a stranger would and reports the message or the step where the send stopped.
What this looks like in a report
“The button turned into a spinner, then went back to blank. I typed everything in. Either they did not get it or the form is broken, so I will email the studio directly.”
The fix. Publish the site after moving the form, then open the public page in a private window and press send from a phone. If the send fails, open the form's settings, confirm the notification goes to an address you read, and check that no required field is hidden.
An illustration. Run a test to see your own.See a real sample report
The editor shows a working form and the live page shows the old one
A website builder keeps two copies of your page. The editor holds the draft you are changing, and the public address serves the version you last published. If you moved, resized or rebuilt the form without publishing, a visitor meets the old layout, or a form that you have since removed. Forms also sit inside sections that hide them on a phone, behind a pop-up that closes too early, or beside a field the visitor cannot reach. Your send from the editor can succeed while the same form on the public page never reaches its notification.
- Open the public address in a private window, signed out, and check that the form is on the page.
- Compare the public page with the editor. If the form differs, publish the site and test again.
- Fill in every field, including the ones at the bottom, then press send and read what appears.
- Check the form's notification settings and send one test to an address you can read.
- On a phone, scroll to the form and check that no banner or pop-up covers the send button.
Draft and live are different pages
The editor and the public site are two views of one project. When you change a form in the editor, the change stays in the draft until you publish, and a visitor keeps seeing the last published version. A form moved to a new section, a field added, or a pop-up set up since the last publish can all be missing from the public page. An owner who tests in the editor is testing the draft, which is the one version a stranger never sees.
The gap is easy to miss, because the editor preview often looks right. Check the public address after every publish, in a private window, and open the page the way a visitor would arrive, from the home page or a link rather than from the editor's preview button. That gap is the first thing to rule out before you look anywhere else.
Where a visitor's send can stop
A send stops at the first thing that blocks it. A pop-up can open over the form and close before a visitor finds the fields. A banner or a chat bubble can sit on top of the send button on a phone. A required field placed below the fold can stop the send with a message the visitor cannot see. A field the visitor cannot reach, such as one inside a collapsed section, can do the same. The visitor sees a button that does nothing, and the owner sees no enquiry.
A send that works for you proves less than it seems
A send from your own browser, signed in, shows that the form works for you. It does not show that a stranger's send reaches the notification you read, and it does not show that the visitor's own confirmation, if one is set up, arrives. A simulated visitor can check the second part, because its inbox is real and a confirmation sent to the address it typed will reach it. It cannot open your notification inbox, so the owner still checks that part.
Mimiq is independent and not affiliated with the platforms it names. Names belong to their owners.
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 moved or resized form can go blank on the live site again
Forms get moved, resized and rebuilt during design work, and each change can leave the live page behind the editor. After each edit and publish, run the same simulated visitors through the enquiry form on a phone and a laptop, and compare the step where each one stopped. Protected previews need a site password in the run, which is part of paid credits. A saved run shows whether the live form still sends.
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
Why does the form work in the editor but not on my site?
The editor shows the draft, and visitors see the last published version. A form you moved, edited or hid after your last publish can look different on the public page. Publish, then check the public address in a private window, opening it from a link rather than the editor's preview.
Can a simulated visitor see the submissions in my dashboard?
No. It cannot open your site's dashboard or your notifications. It shows what the form displayed to the visitor, the step where the send stopped and any failed request on that step. Read the submissions yourself, in the place where your form sends them.
Why do some visitors say the form did nothing?
A pop-up, a banner or the phone keyboard can cover the send button, so the visitor taps where nothing happens. A required field can also block the send with a message placed out of view. The screenshot shows what was on screen when the visitor stopped.
Does a working test mean enquiries will come in?
It means one simulated visitor could send the form from the public address at that time. It does not predict how many real visitors will fill it in, and it does not check that your notification reaches your inbox.
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.