Website Form UX: Fewer Fields, More Enquiries

Every form is a negotiation. You want information; the visitor wants to be done. Most forms lose because they ask for things nobody needs yet, then fail to explain what went wrong. Fixing that is some of the highest-return work you can do on a website.

Ask for less

Go through your form field by field and ask who reads this and what decision it changes. Company size, budget range, "how did you hear about us", and phone number are the usual candidates for deletion. You can ask anything you like in the reply email; you cannot ask anything at all if they abandon the form.

One column, always

Two-column forms make people zigzag and cause skipped fields. A single column with labels above the inputs is faster to complete on every screen size — and it is the only version that survives a phone, per responsive best practices.

Labels above, and never only a placeholder

Placeholder-only labels vanish the moment someone starts typing, so nobody can check their work, and screen readers handle them inconsistently. Use a real <label> with a for attribute, and keep placeholders for format examples.

Let the browser help

Correct type and autocomplete attributes are the highest-value five minutes in form work: type="email" brings up the right keyboard, type="tel" the numeric pad, and autocomplete="name email tel" lets a phone fill the whole thing in one tap. Get these wrong and mobile users type everything by hand.

Validate at the right moment

Not on every keystroke — telling someone their email is invalid while they are still typing it is hostile. Validate on blur, confirm success visibly, and keep the error message specific: "Enter an email address like name@company.com" rather than "Invalid input". Show errors beside the field, not in a banner at the top.

Never lose what they typed

If submission fails, every value must still be there. Losing a long message to a validation error is the fastest way to lose the enquiry entirely — and it is the moment people give up and use a competitor's form instead.

Make the submit state obvious

Disable the button, change the label to "Sending…", and confirm success on the page rather than only by email. Silence after a click is why people submit three times. The mechanics are in micro-interactions, and the button itself in CTA button design.

Handle spam without punishing humans

A honeypot field plus a server-side check plus an invisible reCAPTCHA stops the overwhelming majority of bots with zero friction. Puzzle challenges cost you real enquiries; use them only if you have a demonstrated problem that the quieter measures did not solve.

Keyboard and accessibility basics

• Logical tab order, visible focus states on every field.
• Errors announced, not just coloured — never colour alone, per colour theory.
• Enter submits the form.
• Group related fields with fieldset and legend.

Measure the leak

Track views, starts, submissions, and validation errors per field. One field is usually responsible for most of the abandonment, and it is almost never the field you would guess. Fix that one before redesigning anything.

If your contact form is quiet but your traffic is not, it is usually the form. Ask me to check yours.