Deep dive: the "optional" field that still costs you conversions

Deep dive: the "optional" field that still costs you conversions

Form-friction research is usually summarized as "fewer fields = more conversions," but that's the shallow version. The deeper finding is that perceived field count and field type matter more than the raw number — and "optional" fields are a trap.

What the studies show: the classic field-reduction data (Expedia famously recovered a large revenue increase by removing a single confusing "Company" field; multiple form-optimization analyses replicate the direction) is real, but the more careful work finds the cost isn't linear. Some fields are nearly free (email), others are expensive out of proportion to their position — phone number, date of birth, and anything that triggers perceived risk.

The "optional" trap: marking a field optional does not remove its cost. Users still read it, evaluate whether to fill it, and often pause to decide. Cognitive-load research shows the decision itself is the friction — every optional field forces a micro-choice ("should I?") that consumes working memory and slows momentum. An optional phone field can depress completion almost as much as a required one, because the visitor still stops to weigh handing over their number.

The mechanism is decision load plus risk signaling. A phone field signals "someone will call me." A DOB field signals "why do they need this?" Each one raises perceived risk and invites abandonment, optional or not.

The fix:

— Delete optional fields, don't mark them optional. If you don't strictly need it to convert, remove it from the page entirely.
— Defer the rest: collect only what's needed for the first step; ask for phone/details after the commitment is made, on a thank-you or second screen.
— Replace risky inputs with lower-risk equivalents where possible (range/checkbox instead of exact DOB).
— Measure field-level drop-off, not just form-level — analytics that timestamp focus/blur per field reveal which one is the bleed point.

Practical implication: the question isn't "is this field required?" It's "does this field's information value exceed the momentum it costs?" Usually the optional ones fail that test.

TL;DR
— Optional fields still cost conversions because the user pauses to decide whether to fill them.
— Cost is non-linear: phone, DOB, and risk-signaling fields are far more expensive than position suggests.
— Delete rather than mark optional; defer everything non-essential to a later step.