By platform
Weebly contact form not working, field by field
The visitor fills in the form on a phone, presses Send, and nothing visible happens, or a thank you shows and the message never reaches you. Mimiq sends simulated visitors through the form and shows the step where each one stopped.
Why does my Weebly contact form stop working for visitors?
A stuck form usually comes from one of two places: a required field the visitor cannot see, which stops the submit with no visible message, or a notification sent to a mailbox you no longer read. Check the first by filling in the form on a phone, one field at a time, and the second by sending a message to the address the form names. Mimiq runs simulated visitors through the same form and shows the step where each one stopped, with a screenshot.
What this looks like in a report
“I filled in my name, my email and the date. The button does nothing. There must be a box I cannot see that says it is required. I give up and call the next bakery on the list.”
The fix. Make each required field visible at phone width, and show a line of text above Send that names any empty required field when the visitor presses it. Then submit on a phone with each field empty in turn to confirm the message appears.
An illustration. Run a test to see your own.See a real sample report
A required field off screen stops the submit with no message
The browser checks required fields before it sends a form. When a required field is empty, the browser blocks the submit and tries to point at that field with a small message bubble. If the field is hidden by the phone layout, pushed under a banner, or sitting in a section that is collapsed, the bubble points at nothing the visitor can see. The Send button seems to do nothing, and the visitor assumes the form is broken. You see no problem, because on a laptop the field is visible and already filled in from your last test.
- Is every required field visible at phone width, with its label above it?
- Does a required field sit inside a collapsed section or behind a banner?
- Does Send show a message under the form, or does nothing change at all?
- Does the notification reach the recipient set in the form's own settings?
Where a hidden required field hides on a phone
Phone layouts rearrange a form. Columns stack into one, labels move above their fields, and a section that looks open on a laptop can sit collapsed on a phone. A field that was required before the layout change keeps the flag. A required checkbox, such as a consent box, can be stacked under the cookie banner, which covers it at the bottom of the screen. The visitor sees a Send button and a form that looks complete, and nothing they can see explains the refusal.
A thank you on screen and a message that never arrives
The second failure is the mirror image. The form submits, the thank you appears, and the owner never sees the message. The notification goes to the recipient address set in the form's settings, and that address may be a mailbox you stopped reading, a typo, or an inbox that files mail from your domain as spam. A visitor cannot tell any of these from a success, so they stop waiting for an answer, and the owner takes the quiet inbox to mean nobody asked.
Check the recipient before the next run. Open the form's settings and read the address out loud, letter by letter. Then send a message from your own phone to that address and confirm it arrives in the inbox you read, not in a folder you never open. If it lands in spam, note the sender and the subject line, because a filter that caught one message can keep catching every later message from the same form.
Which failure you have, from the step where visitors stop
Run the visitors once and read the step, not the summary. A stop at the Send button with no thank you points at the hidden field, or at a blocked script. A thank you followed by silence in your inbox points at the recipient. The report keeps a screenshot of each step, so you can see whether a message appeared under a field or the page never changed. Compare that with one manual submission from your phone, using the same field values.
After a fix, run the same visitors again. The step where they stopped should move forward, and the screenshot of that step shows whether a message now appears under the field. If the thank you appears with every required field filled in, the next thing to check is the inbox, not the form. Keep the same visitors for every rerun, so you can compare one result with the last, and stop changing two things at once.
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 new form field or theme change can hide the button again
A form that worked last month can stop after a small edit: a new required field, a theme update that changes the phone layout, or a new banner that covers the bottom of the screen. Rerun the same visitors after each edit to the form or the site template. You find the field that now hides the button before a customer who wanted a quote finds it for you.
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 the test show me the message my form sent?
No. It shows whether the form returned a thank you, an error message or nothing, along with a screenshot of that step. It cannot tell you whether the message reached your inbox, or whether your mail provider filed it in spam. Send one message from your phone to check the inbox yourself.
Does a test submission send a real email to me?
It can. If the form sends a notification, the recipient set in the form's settings gets it, the same as for any visitor. Point the form at an inbox you read, or use a test inbox during the run, and clear the test messages afterward.
Can a visitor fill in a field that asks for a phone code?
No. Visitors cannot receive a text message, so a form that sends a code by SMS stops at that step, and the test ends there. Use a version of the form that does not ask for a code while you test, and keep the code step for a separate check.
Does a CAPTCHA on the form stop the visitors?
It can. A visitor stopped by a CAPTCHA or bot protection is marked as blocked by the site, and the report shows the step where the check stopped them. Leave the check on, because turning it off would test a form your visitors never see.
Does the test check the wording of my cookie banner?
No. It cannot tell you whether the consent text meets a privacy law, and it does not judge how a banner is worded. It shows whether the banner covers a field or a button, and the step where that happened.
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.