Which form field makes people give up? How to find it and fix it (2026 data)
The Formleak team
Published
Quick answer
About a third of people who start a form don't finish it, and they don't leave evenly: password, email and phone fields lose the most people. To reduce form abandonment, find the one field your visitors quit on with field-level data, fix that field first, then check whether more people finish.
How many people abandon forms?
Zuko's benchmark data puts it at roughly 34% of people who start a form not finishing it (Zuko, updated December 2025). The same data shows big differences by form type: contact forms convert about 9% of the people who view them, and onboarding forms complete far less often on mobile (35%) than on desktop (51%).
Two numbers get mixed up here, which is why benchmarks seem to disagree:
- View-to-send: of everyone who saw the form, how many sent it. This is low for most forms, because many people never intended to fill it in.
- Start-to-send (completion rate): of everyone who started, how many sent it. This is the number your form itself is responsible for, and the one to improve.
Compare your form with itself over time rather than with an industry average: a short newsletter form and a ten-field checkout will never complete at the same rate.
Which form fields cause the most abandonment?
Across 1,362 forms, Zuko measured how often people abandon at each type of field (Zuko, updated October 2026):
| Field | Mean abandon rate |
|---|---|
| Password | 10.50% |
| 6.41% | |
| Phone | 6.28% |
| Name | 5.27% |
| Postcode | 4.82% |
| Address | 4.32% |
Two warnings before you start deleting fields. First, these are averages: the medians in the same study are much lower, because a few badly built forms pull the averages up. Your phone field may be fine; someone else's may be a disaster. Second, Zuko found that form length has almost no effect on conversion on its own. It's rarely about how many fields you have, and usually about which field.
That's why the next step matters more than any benchmark: finding the field on your form.
How to find the exact field your visitors quit on
What Google Analytics 4 can and can't tell you
GA4's enhanced measurement records two form events: form_start when someone first interacts with a form and form_submit when it's sent (Search Engine Land). That tells you how many people started and finished, but nothing about which field they stopped at. Practitioners also report that it misses forms sent without a page reload and can count submits that didn't happen (MeasureSchool). You can tag each field yourself in Google Tag Manager, but that's work per form, and breaks when the form changes.
Session recordings and heatmaps
Watching recordings shows you one visitor's struggle in detail, which is great for understanding why. But finding the field this way means watching dozens of sessions, recordings are usually sampled, and in the EU many recording tools need cookie consent first. Microsoft Clarity, for example, has enforced consent for visitors from the EEA, UK and Switzerland since 31 October 2025 (Microsoft).
A field-by-field funnel
The fastest way is a funnel per field. For every field you want to know:
- Reached: how many people who started the form got to this field.
- Left here: how many stopped at this field without sending the form.
- Time: how long people spend on it. A field that takes far longer than the others is a question people have to think about.
- Errors: how many see an error message, of which kind (required, wrong format), and how many give up after it.
- Corrections: how often people go back and change what they entered. Many corrections mean the format isn't clear.
This is exactly what Formleak measures, without cookies and without reading what anyone types: only whether a field is empty, how long it was used and the kind of error shown. Want to compare tools? See the best form analytics tools in 2026.
Fixes per field, with before/after wording
Once you know the field, the fix is usually small. Here are the most common problem fields, what goes wrong, and new wording you can use as a starting point.
Password
The rules are often only revealed after a mistake ("must contain a number"), so people fail, guess, fail again and leave. Show the rules up front, tick them off as they're met, add a show/hide button, and drop the "confirm password" field if you can.
- Before
- Password*
- After
- Choose a password: at least 8 characters, with one number
The rules are visible before typing, so nobody hits an error first.
Phone number
Many people don't want to be called, so they hesitate or leave. If you don't really need the number, make it optional. If you do, say why in one line. And accept every format: spaces, dashes, +31 or 06.
- Before
- Phone number*
- After
- Phone number (optional): only used if there's a problem with your order
Saying why removes the fear of sales calls; optional removes the blocker.
Email fields lose people to format errors and to worry about spam. Check the format gently while people type (not only after they press send), suggest a fix for typos like gmial.com, and say what you'll send.
- Before
- E-mail*
- After
- Email address: we'll send your confirmation here. No spam.
Clear purpose, and a promise that answers the unspoken question.
Name
Separate first and last name fields cause trouble: in Baymard's testing, 42% of people typed their full name into "first name" (Baymard). Use one "Full name" field unless you truly need them apart.
- Before
- First name* / Last name*
- After
- Full name
One field matches how people think about their name.
Address and postcode
Baymard saw 30% of participants stall at "Address line 2". Hide it behind a link ("+ Add apartment, suite…"), offer address lookup from the postcode where you can, and show the expected postcode format.
- Before
- Zip/Postal code*
- After
- Postcode (like 1234 AB, with or without a space)
An example prevents the most common format error.
Coupon code
70% of checkouts show a promo code field, according to Baymard, and a visible empty coupon box sends people off to search for a code. Put it behind a small "Have a code?" link.
Dropdowns
For short lists (up to about five options), radio buttons are faster than a dropdown: people see all the options at once. Keep dropdowns for long lists like countries, and pre-select the most likely one.
The last field, or the send button
When people fill in everything and still don't send, look at the end of the form: an unclear button ("Submit"), an error message far from the field it's about, or a surprise like shipping costs. Make the button say what happens next ("Get my quote") and show errors right next to the field.
Checkout forms: how many fields is too many?
Baymard's research finds the average checkout has 11.3 form fields, while most sites need only 8, and 17% of shoppers have abandoned an order because the checkout was too long or complicated (Baymard). The quickest wins are usually: one name field, hidden address line 2, a collapsed coupon field and no account required to buy.
On WordPress with WooCommerce? Formleak tracks the checkout like any other form. See how to install it on WordPress.
Prove the fix worked
Change one thing at a time, and write down the day you changed it. Then compare the completion rate before and after, for the same number of days on each side. A few things to keep in mind:
- Wait for enough people. With fewer than about 30 starts per side, one or two visitors decide the outcome.
- Seasons, campaigns and traffic changes move the numbers too. A difference shows what happened after your change, not proof it caused it.
- For certainty, run an A/B test: show the old and new version to half of your visitors each, at the same time.
Formleak does both: note a change and it shows the before and after, or set up an A/B test with two small markers on your form.
Tracking forms without cookies or reading what people type
You don't need to record people to fix your form. Whether a field was left empty, how long it took and which kind of error appeared tells you everything you need, and none of it is personal. Tools that record sessions or capture typed values need more care: masking, consent and a clear privacy policy.
Formleak sets no cookies, stores no IP addresses and never reads what people type. Read more in our privacy and GDPR guide. Whether you need consent for analytics depends on your country's rules, so check with your own adviser if you're unsure.
Frequently asked questions
- What is a good form completion rate?
- It depends on the form: short sign-up forms complete far more often than checkouts or quote requests. Benchmarks suggest about two-thirds of people who start a form finish it, but the most useful comparison is your own form before and after a change.
- Can Google Analytics 4 track which form field people quit on?
- Not out of the box. GA4 records form_start and form_submit only, without any field-level data. You need custom tagging per field in Google Tag Manager, or a form analytics tool.
- Does Microsoft Clarity show form field drop-off?
- Clarity has no dedicated field-by-field form report; you'd find the field by watching recordings. In the EEA, UK and Switzerland it also needs cookie consent since October 2025.
- Is there form analytics that works without cookies?
- Yes. Formleak sets no cookies and never reads what people type: it only measures whether fields are filled, how long they take and which kinds of errors appear.
- Should I make the phone number field optional?
- If you don't need it to deliver what people asked for, yes: phone is one of the fields that loses the most people. If you do need it, say why in one line next to the field.
- Are multi-step forms better than single-page forms?
- Not automatically. Multi-step forms can feel shorter and work well for long forms, but each step is a new point to leave. Measure each step: in Formleak you can link steps into a journey and see where people drop out between them.