Flight log / Transmission 044

Form optimization: how many fields is too many?

A form isn't the Konami code. Nobody should need 11 inputs in the right order to earn a demo, yet Baymard's 2024 research found the average checkout still asks for 11.3 form fields when most sites need 8.

The form is where a paid click turns into a lead or turns into a cost. Everything above it, the ad, the headline, the proof, exists to get the visitor to this box. Then the box asks for their budget.

This guide covers how to decide which fields earn their place, what field-level drop-off looks like, when multi-step forms help, the input details that save taps on a phone, and how to test a shorter form without fooling yourself on lead quality.

What is form optimization?

Form optimization is making a form easier to finish without losing information you actually need. It has three levers: how many fields you ask for, how each field is built (labels, input types, autocomplete, errors), and how the form is staged (one screen or several).

On a paid landing page it has a fourth lever most teams skip: what the form is for. A form attached to a "free checklist" ad and a form attached to a "book a demo" ad should not ask the same questions. The offer sets how much the visitor is willing to give.

How many form fields is too many?

The best public research on field count comes from e-commerce checkout, not B2B lead forms, but the direction carries over. Baymard Institute's 2024 benchmark found the average checkout flow contains 11.3 form fields, down from 11.8 in 2021 and 12.7 in 2019, while its testing suggests most sites need only 8.

Even a well-studied, revenue-critical form type is still carrying about 3 extra fields on average. Baymard also notes that the number of fields affects checkout usability far more than the number of steps. Lead forms on paid landing pages rarely get that level of scrutiny.

For B2B lead forms there's no equivalent public benchmark worth quoting, so here is the shape in a hypothetical account. Each extra field shaves a little off the conversion rate, and the drop speeds up once the form starts asking for things the visitor has to think about.

Fewer fields is not always better, though. In the same hypothetical account, say sales accepts 31% of leads from a 2-field form and 52% from a 5-field form, because the extra fields filter out students and job seekers. Per 1,000 clicks that's about 24 accepted leads from the short form and about 31 from the 5-field form. The right number is the one that maximizes qualified leads, not form fills.

Which fields should you keep, defer or cut?

Run every field through one question: will someone use this answer before the first conversation? If yes, keep it. If it's useful later, defer it to the thank-you page, the follow-up email or the call. If nobody can say who reads it, cut it.

MDN documents each of those autocomplete values, and it also notes that a single name field is generally preferred over splitting first and last name, because human names don't all fit that pattern. That's one fewer field for free.

Some data you need doesn't have to come from the visitor at all. Campaign, keyword and click ID can be passed into hidden fields from the URL, so the form doesn't need to ask "How did you hear about us?" of someone who just clicked your ad.

Where do people abandon a form?

A form-level conversion rate tells you that people leave. Field-level drop-off tells you where. If your analytics records which field a visitor last touched before leaving, you can rank fields by how many starters abandon there. The chart below is illustrative, not from a real account, but it reflects the pattern that shows up in most B2B accounts: the fields that cost the most are the ones that ask for commitment or effort, not the ones that ask for identity.

In this hypothetical form, about 28% of starters abandon, and phone plus budget account for more than half of that. Those are the first two fields to make optional or defer. Notice that email and name barely register. People expect to give those.

If you can't measure field-level drop-off, do it by hand: fill the form on a phone, slowly, and note every field where you hesitated. Then ask three people outside marketing to do the same. Hesitation is a decent proxy for abandonment.

Do multi-step forms convert better?

Sometimes. The argument for multi-step: a short, easy first step (email, or a single multiple-choice question) lowers the cost of starting, and people who start tend to finish. The argument against: more screens means more loading, more taps and more chances to leave, and Baymard's checkout research found field count matters far more to usability than step count.

Here is an illustrative comparison: the same six fields, shown either on one screen or split into two short steps with the easiest fields first.

In this hypothetical case the two-step form finishes 5 points ahead, mostly because the first step feels easy. Notice the dip where step 2 begins: that's the moment visitors see what's left. If step 2 is long, the advantage disappears. The order of operations is: cut fields first, then test whether splitting the rest helps. Splitting a bloated form into steps hides the bloat; it doesn't remove it.

What small field details make the biggest difference?

Once the field list is right, the remaining friction lives in the build. Most of these take minutes.

• Visible labels, not placeholders. web.dev's guidance is direct: don't use placeholders as input labels. Baymard's mobile testing found inline labels cause a loss of context once someone starts typing, and recommends separate labels for any form with three or more fields.
• Mark required and optional. Baymard recommends marking both explicitly. Its 2021 benchmark found only 14% of e-commerce sites did so on desktop and 6% on mobile.
• Right input types. type="email" brings up an email keyboard and basic validation; type="tel" brings up a phone keypad. Per web.dev, both matter most on mobile.
• Autocomplete on every identity field. web.dev notes that with autofill, people don't have to remember information or re-enter data. Missing or wrong autocomplete values are the cheapest fix on most forms.
• Errors that say what to do. "Enter a work email, like name@company.com" beats "Invalid input." Show the error next to the field, not at the top of the page.
• A button that names the outcome. "Get the checklist" or "Book my demo," not "Submit." It should match what the ad promised.
• Say why you ask. Google Ads Help advises that when you collect personal information, you make it clear why you're asking and what you'll do with it. One line under the phone field does the job.

On a phone each of these counts double, because every field is a tap, a keyboard switch and a scroll. The mobile landing page field guide covers tap targets and speed around the form.

How do you test a shorter form without fooling yourself?

1. Pick one change. Remove or make optional one or two fields, not five. You want to know which change did the work.
2. Define success downstream. Track form fills, but call the winner on sales-accepted leads or opportunities per click. A shorter form that doubles fills and halves acceptance is a wash with more admin.
3. Size the test before you start. B2B forms convert at low single digits, so differences take a long time to show. Our guide to landing page testing covers sample size and when to stop.
4. Wait for the pipeline. Lead quality shows up in the CRM weeks later. Decide in advance how long you'll wait before judging.
5. Re-check after launch. Forms drift. Someone adds "just one field" for a campaign and it stays for a year. Put forms on the same review list as pages; the CRO audit checklist includes them.

Where this advice breaks down

• The best public data is e-commerce. Baymard studies checkouts, where the buyer has already decided. A demo request is a different decision, so use its findings for usability, not for a target field count.
• Some friction is useful. If sales is drowning in unqualified leads, a field that screens them out can be the right call. That's a deliberate trade, not a failure.
• Field-level data is noisy. "Last field touched" is a proxy. A visitor who stops at phone may have been planning to leave anyway.
• Low volume limits testing. A form with 40 submissions a month won't give you a clean answer quickly. Lean on the keep, defer or cut rule and the manual walkthrough.

For the rest of the page around the form, see B2B landing page best practices.

FAQ