Form optimisation means removing the friction, confusion and doubt that stop willing visitors from finishing an enquiry or sign-up form. The biggest gains usually come from asking fewer and clearer questions, labelling every field, showing helpful errors, working well on mobile, explaining what happens next and making sure every submission reaches a person.
Forms are where interest turns into a lead, and where many leads are quietly lost. This listicle gives 20 practical fixes, grouped by stage, each with what it is, why it matters and how to do it. Most can be made in a day without a redesign.
Key takeaways
- Every extra field is a cost. Ask only what you need for the next step, and collect the rest later.
- Visible labels, sensible input types and clear error messages fix a large share of form problems.
- Accessibility and conversion overlap: an unlabelled field is both a barrier and a lost lead.
- Trust matters at the moment of submission. Say what happens next, how fast you reply and how data is used.
- A form is only as good as its delivery. Test that every submission reaches the CRM and a real inbox.
What does recent research say about form friction?
Basic form accessibility is still widely broken. The WebAIM Million 2025 report, which tested the home pages of the top one million websites, found missing form input labels on 48.2% of pages. Home pages had 6.3 form inputs on average, and 34.2% of those inputs were not properly labelled.
Long forms remain common too. Baymard Institute’s checkout research finds that the average US checkout shows 23.48 form elements by default, although its testing suggests an ideal checkout can be as short as 12 to 14 elements. In its survey of US online shoppers, 17% said they had abandoned an order because the checkout was too long or complicated, and 18% because the site wanted them to create an account.
Form friction in recent research
Checkout and enquiry forms are not the same, but the lessons transfer: every field must earn its place, and every field must be understandable to every user.
Fixes 1–5: How do you decide what the form should ask?
1. Start from the next step, not the CRM wish list
What: list only the information needed to take the next action, such as replying or preparing a first call. Why: forms often grow because every team adds a field “just in case”. How: for each field ask “what do we do differently with this answer?” If the answer is nothing, remove it.
2. Remove or defer optional fields
What: move nice-to-have questions out of the first form. Why: optional fields still look like work. How: collect company size, budget or job title later in the first call, a follow-up email or an enrichment tool.
3. Combine and simplify fields
What: use one “Full name” field instead of separate first and last names where you can. Why: fewer boxes feel faster, and many names do not split neatly. How: check whether your CRM truly needs separate fields before splitting them.
4. Ask one open question that helps you prepare
What: a short “What would you like help with?” or “Your website URL” field. Why: one well-chosen question lets you reply with something useful instead of a generic sales email. How: keep it optional or short, and use it to prepare the first reply.
5. Use smart defaults and preselection
What: preselect the service or topic when the form sits on a specific page. Why: it saves a step and improves routing. How: pass the page’s service as a hidden or preselected value, and still allow the visitor to change it.
Fixes 6–10: How do you make every field clear?
6. Give every field a visible label
What: a permanent text label above or beside each field. Why: placeholder-only labels disappear as people type and are not reliably announced to screen readers, which is why missing labels top the WebAIM failure list. How: use a proper <label> element connected to each input, as shown in the W3C forms tutorial on labelling controls.
7. Use the right input type
What: email, tel, url and number input types. Why: mobile devices show the right keyboard and browsers can autofill correctly. How: set type=”email” for email, type=”tel” for phone, and add autocomplete attributes such as name, email and tel.
8. Mark required and optional fields consistently
What: a clear rule, such as marking optional fields as “(optional)”. Why: people should not discover required fields only after pressing submit. How: choose one convention for the whole site and explain any symbol you use.
9. Explain why you ask for sensitive data
What: a short helper line under fields such as phone number or budget. Why: unexplained personal questions trigger doubt. How: “We will only call if you prefer a call” or “Helps us suggest the right plan” next to the field.
10. Keep phone and country fields forgiving
What: accept phone numbers with spaces, dashes or a country code. Why: strict formats reject valid numbers, especially for international visitors. How: normalise the format after submission instead of forcing users to type it your way.
Fixes 11–15: How do you handle errors, mobile and speed?
11. Validate inline, after the field is completed
What: check each field when the user leaves it, not on every keystroke. Why: early warnings feel like nagging; late warnings feel like a trap. How: show the message next to the field once the user moves on, and clear it as soon as it is fixed.
12. Write error messages that say how to fix the problem
What: “Please enter an email like name@company.com” instead of “Invalid input”. Why: people fix specific problems quickly and give up on vague ones. How: connect the message to the field so assistive technologies announce it, and never clear valid answers after an error.
13. Design for thumbs
What: full-width fields and buttons large enough to tap. Why: many enquiries now start on a phone. How: use a single column, generous spacing and a submit button that stays visible.
14. Keep the form fast to load and respond
What: a form that is usable as soon as the page appears. Why: heavy scripts delay typing and button presses, which shows up as poor Interaction to Next Paint. How: avoid loading large form plugins or multiple trackers on every page; our Core Web Vitals guide explains how to diagnose slow interactions.
15. Use spam protection that does not punish humans
What: honeypot fields, time checks or invisible challenges before visible puzzles. Why: difficult CAPTCHAs block real people, including users of assistive technology. How: start with invisible methods and add a visible challenge only if spam continues.
| Form type | Typical fields worth asking | Fields to defer |
|---|---|---|
| Contact or enquiry | Name, email, what you need help with | Budget, company size, job title |
| Free audit or plan request | Name, email, website URL, main goal | Tools used, monthly traffic, revenue |
| Resource download | Email, optionally name | Phone number, company details |
| Newsletter | Email only | Everything else |
| Demo or consultation booking | Name, work email, preferred time | Detailed requirements (ask on the call) |
Fixes 16–18: How do you build trust at the moment of submission?
16. Say what happens after submission
What: one line next to the button, such as “We reply within one working day by email.” Why: uncertainty about what comes next is a quiet reason people do not submit. How: only promise a response time your team can actually meet.
17. Use honest button text
What: a label that describes the action, such as “Send my enquiry” or “Get the guide”. Why: “Submit” says nothing, and misleading labels damage trust. How: match the button to the promise in the page heading.
18. Make consent clear and separate
What: plain-language consent text and an unticked, optional box for marketing emails. Why: buyers want to know how their data is used, and privacy laws increasingly expect clear consent. How: link to your privacy policy and keep marketing consent separate from the enquiry itself. This is general guidance, not legal advice.
Fixes 19–20: How do you make sure every lead arrives and is measured?
19. Test delivery end to end
What: a regular test submission from each form to the CRM, the team inbox and the auto-reply. Why: forms often “work” on the page while emails land in spam or CRM integrations silently fail. How: send email through authenticated SMTP, check SPF, DKIM and DMARC, and test after every plugin or theme update.
20. Track submissions as real outcomes
What: a conversion event on successful submission, plus source and page data stored with the lead. Why: button clicks are not leads, and leads are not customers. How: fire a generate_lead event in GA4 only after a successful submission, pass UTM and page data into the CRM, and review qualified leads by form, as explained in the marketing analytics and attribution guide.
Four questions to ask of every form
Does each field change the next step?
Can every user understand and complete it?
Does the visitor know what happens next?
Does every submission reach a person and the CRM?
How should you test form changes?
Many sites do not have enough traffic for statistically reliable A/B tests on forms. That is fine. Combine methods:
- Task testing: ask three to five people to complete the form on their own phones while you watch. You will see most problems quickly.
- Field analytics: track where people start and abandon the form, and which errors appear most often.
- Session recordings: tools such as Microsoft Clarity show where users hesitate, as long as you mask personal data.
- Downstream quality: compare qualified leads before and after a change, not just submissions. A shorter form can raise volume and lower quality; you want the balance that fits your sales capacity.
The conversion rate optimisation guide explains how to decide whether an apparent win holds up downstream.
How do forms differ for B2B leads, checkout and WhatsApp?
The fixes above apply everywhere, but each context has its own priorities:
- B2B enquiry forms need just enough context to route and prepare: name, work email, company or website, and what the buyer needs. Ask about budget and timeline on the first call, not in the form, unless sales capacity is very limited.
- eCommerce checkout needs guest checkout, address autocomplete, clear delivery costs before the payment step and the payment methods your buyers expect. Baymard’s research on checkout length and forced accounts applies most directly here.
- WhatsApp or chat as an alternative. In India especially, many buyers prefer to start a conversation on WhatsApp. A prefilled WhatsApp link next to the form gives them that choice, but log those conversations in the CRM too, or they disappear from reporting.
- Gated resources such as whitepapers or assessments should ask only for an email and perhaps a name. Asking for a phone number to download a guide signals a sales call nobody wanted.
What should a form audit cover?
If you manage several forms, audit them together once a quarter. A simple audit sheet should record, for each form:
- The page it sits on and its job (enquiry, download, booking, newsletter).
- Number of fields, how many are required and which could be deferred.
- Whether every field has a visible, connected label and correct input type.
- How errors are shown and whether answers survive an error.
- What the button says and what the page promises happens next.
- Where submissions go: CRM, inbox, auto-reply, and whether a test submission arrived.
- Whether a conversion event fires only on success, and whether UTM and page data reach the CRM.
- Completion rate, top error and the share of submissions that became qualified leads.
Fix the issues that block delivery or accessibility first, then the ones that add effort, then the ones that affect trust.
Which hidden fields help most when routing leads in a CRM?
Some of the most useful data never needs to be typed by the visitor. Hidden fields captured automatically make routing and reporting far better without adding effort:
- Page URL and page title of the form, so you know which service or guide produced the lead.
- UTM source, medium and campaign, stored from the first visit, so paid and organic leads can be separated.
- Click IDs such as gclid, so offline conversions can be sent back to ad platforms.
- Preselected service or topic from the page, so the lead reaches the right person.
- Consent status, recorded as a separate field, so marketing emails only go to people who agreed.
Tell visitors in your privacy policy what you collect and why. Keep the visible form short and let these fields do the background work.
Which related guides should you read next?
- Landing page optimisation covers the page that leads to the form.
- Service pages that convert sets up the promise the form must keep.
- Website performance and accessibility covers labels, focus and keyboard testing in depth.
- Conversion rate optimisation explains how to test changes properly.
- Lead management and sales handoffs makes sure submissions become conversations.
Frequently asked questions
How many fields should a contact form have?
As few as the next step needs, often three or four: name, email and a short message or URL. Collect other details later.
Do multi-step forms convert better?
They can for longer forms, because each step feels smaller, but they add clicks. Test with real users and measure completed, qualified submissions rather than step-one starts.
Should I ask for a phone number?
Only if you will use it, and say why. Making phone optional usually reduces drop-off while still letting interested buyers share it.
Is placeholder text enough as a label?
No. Placeholders disappear when people type and are not a reliable label for assistive technologies. Use a visible label for every field.
How do I know my form submissions are not being lost?
Send a test entry from each form regularly and check that it appears in the CRM, the team inbox and the visitor’s auto-reply, including the spam folder.
Should I add a WhatsApp option next to my form?
If your buyers commonly use WhatsApp and your team can reply quickly, yes. Make sure those conversations are logged in your CRM so they count in reporting.
Sources and further reading
- WebAIM Million 2025: accessibility of the top one million home pages
- Baymard Institute: cart abandonment and checkout research
- W3C Web Accessibility Initiative: labelling form controls
- W3C: WCAG 2.2 quick reference
- web.dev: INP becomes a Core Web Vital (March 2024)
- Microsoft Clarity: session recordings overview
- The field recommendations and review framework are Bargaon’s editorial guidance, not research data.
Want forms that bring in more qualified enquiries and never lose a lead? Bargaon’s conversion optimisation service audits your forms, fixes friction and connects every submission to your CRM.