How Many Contact Form Fields Does a Small Site Need?
An enquiry form stops working one well-meaning field at a time. How many contact form fields does a small site actually need? On 19 September 2026 we counted the four forms we run, put the counts next to a HubSpot analysis of 40,000 landing pages and the Nielsen Norman Group framework for trimming form effort, and the answer sits in a narrow range: three to four fields for a typical enquiry, more only where every extra field changes what happens next.
Every form grows the same way
Two of the four forms we run are lean because the outcome is a conversation. The callback form on warasat.com.pk asks for a name, a phone number and an optional message; an agent needs nothing else to ring someone back. The quote flow on truckaxic.com opens with four fields, because the first screen only has to prove you are a real person with a real truck.
The other two carry more weight. The MRI booking form on mtufaildiagnosticcenter.com asks for eight fields before it accepts a request, and our own form on dev2production.com/contact asks for nine. The interesting question is not which number is right; it is whether that weight is earned or habit. That question needs data before opinions.
What 40,000 landing pages say about field types
Dan Zarrella’s analysis for HubSpot, updated 6 June 2025, covered more than 40,000 customer landing pages. Conversion rates did fall as field count rose, but “not as steeply as I expected”, and adding single-line text fields produced very little decline. Field type mattered more than count: multiple multi-line textareas had “a powerful depressing effect” on conversion, and pages with several dropdown selects tended to convert lower. HubSpot’s takeaway is blunt: use as few fields as you can, and be especially cautious with textareas and select boxes.
Every field is a withdrawal
Nielsen Norman Group published the EAS framework in March 2025, by Huei-Hsin Wang: Eliminate first, automate where possible, simplify what remains. The order is the point. Their framing: “Building a good form is like managing a bank account of trust. Every question is a withdrawal.” They also hand you one filter that kills most fields on a small-business form: “Do we need this information now?”
A company name can wait until the second conversation. A budget range can be asked on the first call. If the answer can wait, the field can wait, because the visitor who fills eleven boxes for an enquiry is rarer than the one who fills three.
Four forms we run, counted
| Form | Fields | Required | What the weight buys |
|---|---|---|---|
| warasat.com.pk callback | 3 | 2 | A name and a number are all an agent needs to call back |
| truckaxic.com quote, step 1 of 4 | 4 | 3 | Company is optional because a one-truck owner-operator has none |
| mtufaildiagnosticcenter.com booking | 8 | 6 | Service, date and a 13-slot time select book a real scanner slot |
| dev2production.com/contact | 9 | 4 | The required budget field is why the first reply can be an assessment instead of a chain of clarifying questions |
The dispatch site’s email field shows the automate half of EAS in the wild: it asks for a Google-linked address and says why, because the address gets verified with Google in the final step. The booking form’s eight fields all change what the clinic does next, down to the gender field, which is required there and is the clinic’s call, not a UX opinion. Our nine-field form is the one we would argue about. Run it through the test below and phone and company are the first two we would put on the chopping block.
This kind of call is made during the build, not after it; it is part of how we run web development projects.
The test every field has to survive
| Ask of every field | If the answer is no |
|---|---|
| What breaks this week if we delete it? | Delete it |
| Does the first reply or the first call surface it anyway? | Postpone it, the NN/g “do we need this now” filter |
| Can the browser or a signed-in account fill it for the visitor? | Automate it |
| Is it a textarea or a dropdown? | Shrink it or delete it, the HubSpot finding |
When fields only apply to some visitors, branch instead of stacking. NN/g puts it plainly: avoid asking questions that do not apply, place the branching questions early, and show each path only its own fields. A form is not the only friction on a small site either; page weight on mobile data costs visitors the same way, which we measured on a real build in a separate post.
When the better form is a link
Both consumer sites we built keep a form, and neither makes it the only door. Warasat’s WhatsApp button opens a chat with the first half-sentence already typed: “Hi Warasat, I would like to ask about”, and the visitor finishes the thought. The diagnostic centre puts a Book via WhatsApp button next to its submit button, and the prefilled message already says what the patient wants: an appointment at the centre.
For someone on a phone with one thumb free, a half-written message is a lower wall than any form. The trade-off is real: a chat gives you no structured record, so if you need a paper trail or route enquiries to different staff, keep the form. If your outcome is a phone call, the link may be the whole answer.
Count your contact form fields, then delete two
Open your form and count the fields, required or not. An enquiry form lands at three or four: a name, a way to reach you, and one box for the reason. A booking form can run longer, but every field should change what happens next, or it is another withdrawal from an account you did not know you were overdrawn on. Delete two and watch a week of enquiries before you judge the change.
If you want a second pair of eyes on the count, the form on our contact page is the fastest way to reach us, and yes, it has nine fields. We are working on it.
FAQ
How many fields should a contact form have?
Three for a basic enquiry: a name, a phone number or email, and one message box. Four if a second way to reach you earns its place. Our own live forms sit in that range: a three-field callback for a real-estate agency and a four-field opening step on a four-step quote flow. A booking form is a different animal. The diagnostic centre’s MRI form runs eight fields because each one changes which slot the staff book.
Do optional fields lower conversion?
Far less than heavy field types. In the HubSpot data, conversion declined very little as single-line text fields accumulated; multi-line textareas and dropdowns were the ones that dragged rates down. The stronger argument against optional fields is practical: they invite junk answers, and every junk answer costs you a follow-up later. If a field is not worth requiring, ask whether it is worth displaying at all.
Is a multi-step form better than one long form?
Longer flows work when the first screen stays small. The truck dispatch site we built runs a four-step quote flow, and step one holds four fields: name, optional company, email and phone. Each later step asks only what the next step needs. The design to avoid is the single page that shows every step’s fields at once, which is the dropdown and textarea pileup the 40,000-page study warns about.
Should I replace my form with a WhatsApp link?
For a local business whose goal is a conversation, often yes. Both sites we run for a real-estate agency and a diagnostic centre keep a WhatsApp button that opens a chat with the first sentence already typed. The trade-off: chats create no structured record, so a form is safer when you need a paper trail or route enquiries to different staff. When the outcome is a phone call, the link is hard to beat.