TL;DR. Every field on a form costs you completions. Some fields cost a lot more than others. A phone number field drops 5-9% of visitors. A freeform "How did you hear about us?" textarea drops another 3-6%. The estimator does the math field by field so you can see exactly where your form starts bleeding.
The Form-Field Friction Estimator parses every form on a page, classifies each field by type (email, phone, textarea, select, checkbox cluster), applies published Zuko and Formisimo benchmark drop-off weights, and predicts the cumulative form-completion rate. It flags the one or two fields that are doing the most damage. Same chrome as every other jwatte.com tool. Deep-links from the mega analyzers, AI-prompt export, CSV/PDF/HTML download.
Parses every form on a page and estimates cumulative completion drop-off per field using published Formisimo / Zuko benchmark data. Surfaces the 1-2 fields that are destroying your conversion.
Why this dimension matters
Forms are the last mile of conversion. You can nail every other signal on the page. Clean copy, strong CTA, fast load time, good trust signals. None of it matters if the form at the bottom asks for twelve fields and loses half the visitors between field three and field seven.
The counterintuitive part: the worst offender usually isn't the field you'd expect. Name and email fields have low friction because visitors expect them and browsers autofill them. Phone number fields have high friction because people don't want to be called. Open-ended textareas have high friction because they require effort and creativity. A single "Company name" field on a B2C form can cost you 3-4% of completions for zero business value.
Zuko (formerly Formisimo) published field-level analytics across millions of form interactions. Their data shows that the relationship between field count and completion rate isn't linear. Going from 4 fields to 5 costs less than going from 8 to 9. Friction compounds. The estimator applies those published weights to your specific form and shows you the compounding curve.
Common failure patterns
- Phone number on a lead-gen form. Unless you're running an outbound call center, you probably don't need a phone number at first contact. It's consistently the highest-friction single field in Zuko's benchmarks. If you do need it, mark it optional and put it last.
- "Message" textarea with no character guidance. Open-ended text fields intimidate people. A blank box with no placeholder, no character limit hint, and a vague label like "Message" causes visitors to stall. They don't know what to write, so they write nothing and leave.
- Asking for the same information twice. "Confirm email" and "confirm password" fields exist because developers didn't trust their validation. They double the friction on two of the most common fields. Inline validation on a single field is cheaper and more effective.
- Company name on a consumer form. If your product is B2C, a "Company" field signals that the form wasn't built for the visitor. It creates confusion and adds a field that most people will leave blank or fill with junk.
- Hidden required fields. A field that looks optional but throws a validation error on submit is worse than a field that's visibly marked required. The surprise rejection on submit costs you the entire session, not just the field.
How to fix it at the source
Run the estimator against your form and look at the cumulative completion curve. Find the field where the curve drops sharpest. That's your first cut candidate. If removing it isn't possible, try moving it to a second step (progressive disclosure), marking it optional, or replacing it with a less friction-heavy input type. A dropdown with three options has less friction than an open textarea.
After cutting, run the estimator again. Compare the predicted completion rates. The tool makes the before/after math visible so you can justify the change to a stakeholder who insists every field is necessary.
Thresholds that matter
| Signal | Target |
|---|---|
| Total visible fields | 5 or fewer for lead-gen. 7 or fewer for checkout. Every field above threshold costs ~2-5% completion. |
| Phone number field | Optional, not required. If required, expect 5-9% incremental drop-off. |
| Open textarea | Include placeholder text and a character-count hint. Expect 3-6% drop-off regardless. |
| Confirm/repeat fields | Remove. Use inline validation on the original field instead. |
| Predicted completion rate | Above 60% for lead-gen forms. Below 40% means the form needs surgery, not tweaks. |
| Autofill coverage | Every name, email, phone, and address field should carry the correct autocomplete attribute. |
Example fix
Replacing a high-friction phone + textarea pair with a lower-friction alternative:
<!-- BEFORE: 3 high-friction fields -->
<label for="phone">Phone number *</label>
<input type="tel" id="phone" name="phone" required />
<label for="company">Company name *</label>
<input type="text" id="company" name="company" required />
<label for="message">How can we help?</label>
<textarea id="message" name="message" rows="5"></textarea>
<!-- AFTER: 1 optional field with guidance -->
<label for="topic">What are you looking for? (optional)</label>
<select id="topic" name="topic">
<option value="">Select a topic</option>
<option value="pricing">Pricing question</option>
<option value="support">Technical support</option>
<option value="partnership">Partnership inquiry</option>
<option value="other">Something else</option>
</select>
When to run the audit
- Before launching any new form. Get the predicted completion rate before real visitors hit it.
- When form completion rates drop and you haven't changed the form. Sometimes a CMS update or A/B test re-adds a field you cut.
- After a redesign. New layouts often add "nice to have" fields that weren't in the original.
- Quarterly on your highest-traffic forms. Even stable forms benefit from re-evaluation as benchmarks update and visitor expectations shift.
Reading the output
Every finding is severity-classified. The playbook is the same across tools:
- Critical / red — same-week fixes. These block the primary signal and cascade into downstream dimensions.
- Warning / amber — same-month fixes. Drag the score, usually don't block.
- Info / blue — context only. Often what a PR reviewer would flag but that doesn't block merge.
- Pass / green — confirmation. Keep the control in place.
Every audit also emits an "AI fix prompt" you can paste into ChatGPT / Claude / Gemini for exact copy-paste code patches tied to your specific stack.
Related tools in this family
- Checkout Abandonment Autopsy — if the form is a checkout, this audit catches the broader friction patterns beyond individual fields.
- Form Conversion Audit — checks label association, autocomplete attributes, tab order, and ARIA markup on your forms.
- Trust Signal Surface Audit — trust signals near a form (privacy notice, SSL badge) affect completion as much as field count.
- WCAG Accessibility Audit — inaccessible form fields don't just fail compliance. They fail completion for keyboard and screen-reader users.
- Scroll-Depth CTA Visibility Map — if the submit button is below the fold, visitors who filled every field still won't convert.
Fact-check notes and sources
- Zuko (formerly Formisimo): Form Analytics Benchmarks — field-level drop-off weights
- Baymard Institute: Checkout Usability: Reducing Form Fields — field count and completion rate correlation
- HubSpot: How to Reduce Form Friction — B2B/B2C form optimization data
- Google Web Fundamentals: Create Amazing Forms — autocomplete attribute reference
This post is informational and not a substitute for professional consulting. Mentions of third-party platforms in the tool itself are nominative fair use. No affiliation is implied.
