Web Forms That Convert: Every Field You Remove Is Another Sale
The form is where all your traffic turns into business or disappears. And it's almost always the part of the site nobody reviewed: inherited fields, incomprehensible errors, and a "thank you" that says nothing.
May 25, 20226 min readIn this article
- Every field has a price, and you pay it in enquiries
- Visible labels and errors people can understand
- On mobile, the right keyboard changes everything
- Blocking spam without punishing the customer
- What happens after submit is part of the form
- Where does what people write actually go?
- Consent and data: the minimum, done properly
- Frequently asked questions
You can have the best design, the best copy and traffic to spare. If the form asks for fourteen pieces of information and returns "Error in field 3", none of that matters. The form is the bottleneck of the entire website, and it's the piece that gets the least attention on almost every project.
The good news is that fixing it is cheap and the effect is immediate and measurable. You don't need to redesign anything: you need to remove things, order what's left, and say clearly what happens next.
Every field has a price, and you pay it in enquiries
The relationship is fairly direct: more fields, fewer people finish. Not because they're hard, but because each one is a micro-decision — why do they want this? are they going to ring me? — and accumulated micro-decisions produce abandonment.
The test that settles the argument is this: for each field, ask what you'd do differently without it. If the answer is "nothing", the field goes. Usually the casualties are surname, company, "how did you hear about us?", and the country dropdown nobody uses.
| Type | Minimum viable fields | What's usually surplus |
|---|---|---|
| General contact | Name, one contact route, message | Surname, company, subject line, phone when you already ask for email |
| Quote request | Contact + type of work + location + timing | Exact budget, technical detail they don't know yet |
| Booking or appointment | Contact + preferred date or time window | Detailed reason, things better asked in person |
Visible labels and errors people can understand
Putting the text inside the field instead of above it looks elegant until the user starts typing: the label vanishes and they no longer know what belonged there. And if they make a mistake and have to come back, they're guessing. Labels go outside, always visible.
- Label above the field, not inside it. Placeholder text can coexist, but not replace it.
- Mark what's optional, not what's required. If nearly everything is required, flagging the exceptions is quieter.
- Put the error next to the field that failed, not in a red banner at the top that has to be decoded.
- Say what's expected, not that it's wrong: "the email needs an @" rather than "invalid format".
- Never wipe what they already typed. A form that empties itself on failure doesn't get filled in twice.
On mobile, the right keyboard changes everything
Most of your forms are completed with a thumb. That makes things matter that are invisible on desktop: the phone field opening the numeric keypad, the email field offering the @, autocorrect not mangling the name, and the submit button not sitting behind the keyboard.
Each is a one-line detail, and together they explain much of the gap between a form that gets completed and one abandoned halfway. Test yours on your own phone before arguing about anything else.
Blocking spam without punishing the customer
Spam is real and has to be stopped, but a captcha full of blurry traffic lights is a tax you charge the person who genuinely wants to contact you. On mobile, on a weak signal, it's simply an exit.
What happens after submit is part of the form
"Thank you, your message has been sent" is a wasted opportunity. The person has just done what you asked and is at their peak attention: that's the moment to tell them exactly what to expect.
- When you'll reply: "we'll get back to you today" or "within 24 working hours".
- Which address or number you'll write from, so it isn't lost to spam or ignored as an unknown caller.
- What they can do meanwhile: see case studies, read a guide, send a photo on WhatsApp.
- An automatic confirmation email, which also proves the address was correct.
And above all: meet the deadline you stated. Promising a reply in two hours and answering in three days is worse than promising nothing, because the first impression has already formed. What holds all of this together is in what your website needs to sell.
Where does what people write actually go?
It's the question almost nobody asks when accepting a new website, and the one that causes the most silent losses. A form pointing at a misconfigured address, or landing in the owner's own spam folder, can swallow enquiries for months without anyone noticing.
- Test the form yourself after launch, and again every few months.
- Send it to more than one person or a shared inbox — not the personal address of whoever goes on holiday.
- Keep a copy outside email: if the mailbox fills up or gets wiped, the enquiry history goes with it.
- Check the recipient's spam folder: it's where a lot of form notifications end up.
Consent and data: the minimum, done properly
If you collect personal data — and a name and an email are exactly that — you need to say what you use it for, how long you keep it, and how deletion is requested. You don't need an enormous legal wall: you need two honest lines next to the button, linked to the privacy policy.
And a checkbox that isn't pre-ticked if you're adding that person to a mailing list. Ticking it for them saves one click and costs the trust of everyone who notices — which is more people than you think.
Frequently asked questions
How many fields is too many?
It depends on what the person is asking for. For general contact, more than four is already a lot. For a construction quote or a serious application, seven or eight are tolerated because the user understands they're needed. The rule isn't a number: it's that every field justifies itself by something you'll actually do with it.
Do multi-step forms work better?
They work when there genuinely is a lot to ask, because they reduce the sense of effort and show progress. But splitting four fields across three screens is worse than leaving them on one: you've added clicks without removing work. Use them from eight or ten fields upward, not before.
Should the form go on the homepage?
A short homepage form usually performs well, especially for service businesses. What doesn't work is a long form right at the top, before you've explained anything: nobody hands over their details to a company whose offer they haven't understood yet. Argument first, question second.
Does WhatsApp replace the form?
It complements it. WhatsApp converts better because the user already has it open and expects an immediate reply, but it leaves no orderly record and fails when nobody's answering out of hours. The sensible setup is both: WhatsApp for the impatient, a form for whoever writes at eleven at night.