To test a contact form properly you need two checks: that a visitor can actually complete and submit it, on desktop and on a phone, and that the message then arrives where it should. This free scan handles the first part in a real browser: it finds the form, presses submit on an empty form to see whether validation appears, checks the layout at phone width, and records JavaScript errors and failed requests. The second part, delivery to your inbox, only you can confirm, by sending yourself a test message from a private window.
What it checks
Validation on an empty submit
The scan presses the submit button without filling anything in. A healthy form shows which fields are required; a broken one does nothing, or worse, pretends to succeed.
Submit button reachable on a phone
At phone width, fields and buttons pushed off screen, covered by a sticky bar or squeezed too small to tap are flagged with a screenshot.
JavaScript errors and failed requests
Many silent form failures leave a trace: a script error when the page loads or a request to a form endpoint that returns an error. Both are recorded and shown in the report.
Labels and accessibility
Fields without labels, poor contrast and missing error descriptions are checked with axe-core, because a form that a screen reader cannot use is also a form that confuses everyone else.
How to read your results
- If empty submit showed no validation, try it yourself in a private window. No message at all usually means the form’s script failed to load.
- A failed request in the report that mentions your form provider, email service or a backend function is the most direct clue to why messages are not arriving.
- If the scan is clean, finish with the delivery test: send a real message to yourself and check the inbox and spam folder.
What an automated check can't tell you
- The scan does not fill in and send real messages, so it cannot confirm that an email reached your inbox. That would also fill your inbox with test leads.
- It does not get past CAPTCHA challenges, and it should not: if your form has one, the delivery test has to be done by hand.
- The free scan looks at your homepage form; forms on other pages need a paid report or the manual test.
Want to see a full report before you scan? Here's a real sample report.
Frequently asked questions
How do I test if my contact form is working?
Open the live site in a private window, submit a real test message from an address you control, and check that it arrives in the inbox the form should deliver to, including the spam folder. Repeat on a phone. A success message on screen does not prove delivery.
Why does my form say sent but I never get the email?
The success message and the delivery are separate steps. Common causes are email sent without SPF and DKIM landing in spam, a recipient address nobody reads, an expired key for the email service, or on AI-built sites a backend that only worked in the builder preview.
How do I keep test submissions out of my real leads?
Use an obvious subject such as FORM TEST with the date, and an address you recognise, so you can filter them out. That is also why an automated scan should not send real submissions to someone else’s form.
How often should I test my website forms?
After every change to the site, plugin or email setup, and once a month even when nothing changed, because the email side can break without anything on your site moving.
Rather have a QA engineer test it by hand?
An automated check covers what a visitor sees on load. For logged-in flows, checkout, or a launch that has to go right, I'll test the site by hand.
- Up to 10 key pages tested by hand, not a scan
- Every flow a customer uses: forms, sign-up, checkout, booking
- Real mobile and desktop browsers
- A written report in plain language, with screenshots
- A 15-minute call to walk you through it
- 10 years of professional QA experience
Tell me about your site and I'll reply personally, usually the same day.
No payment now. I'll confirm scope and price first.
Related fix guides
Other free tools: Free mobile-friendly test · Broken button checker · JavaScript error checker · Free website bug checker · AI website tester
Built by Waqas Ahmad, QA engineer with 10 years of professional testing experience. Last checked October 26, 2026.
Sources: HackerNoon: testing website contact forms · Website form monitoring guide