Digital Marketing
Landing-page forms: Why enquiries stall and what to check
A landing-page form should let people make the intended enquiry without unnecessary effort. A high bounce rate alone cannot explain why they leave. Review the entire journey: the promise on the page, the inputs, the confirmation and the message that actually reaches your team.
Do not start with a new button colour
Before changing colours or wording, submit a complete enquiry yourself. Test on a phone and on a desktop. Does the message arrive? Is submission clearly confirmed? What happens with an invalid email address or a temporary failure? An attractive interface cannot compensate for delivery failing silently.
Separate page views, form starts and successfully received enquiries. Clicking “Send” is not proof of successful delivery. Measurement must distinguish those states; tracking should follow applicable privacy requirements and should not collect the contents of form fields.
Every field needs a reason
List every field and explain why you need the information at first contact. Is a phone number essential, or would an email address work initially? Does a budget have to be specified now? Information needed later may be better discussed in a follow-up conversation.
W3C recommends requesting only information needed for the task. Irrelevant or excessive requests can contribute to people abandoning a form. This does not mean that every shorter form converts better. A necessary question can help qualify an enquiry. What matters is a reasoned selection, not a universal maximum number of fields.
Clear inputs, not guessing games
- Every field has a visible, understandable label.
- Required information is identifiable before submission.
- Where a format is required, an example is available beside the field.
- Optional inputs do not look like hidden requirements.
- A placeholder is not the only label: it disappears while typing.
Test with a keyboard too. Focus and errors must be discoverable. Uploads need understandable information about permitted formats and limits. “Invalid input” does not explain a problem adequately; a specific explanation with a way to correct it is more useful.
Errors and success belong in the design
Check whether previously entered information is preserved after an error. Put errors near the relevant inputs and make them perceivable to assistive technologies. Successful submission should clearly confirm that the enquiry has been received. Do not promise a response time your team cannot reliably meet.
A complete audit does not stop at the success message. Check that the enquiry arrives internally in a readable form and has an accountable owner. Test submissions should not become real sales figures; label and handle them appropriately.
A short audit protocol for your team
- Record the objective, audience and source of form visits.
- Test a successful submission and verify its arrival.
- Test missing required information, incorrect formats and delivery failures.
- Check mobile use, keyboard operation and understandable feedback.
- Prioritise technical obstacles before cosmetic changes.
- Change one reasoned hypothesis and test again afterwards.
With few enquiries, short-term percentage changes are not robust evidence of improvement. Supplement usage data with specific observations. When comparing variants, account for different traffic sources and compare consistently defined successful enquiries, not just button clicks.
Frequently asked questions
How many fields should a form contain?
As many as the task requires, but no more. Booking an appointment, applying for a job and discussing a project have different information needs.
Is an audit useful without much traffic?
Yes. Technical failures and unclear inputs can be tested directly. Reliable claims about conversion differences require sufficient relevant data.
Take the next step
Our article on landing-page structure and content complements this form audit. Explore web design and custom web development for design and implementation. To discuss a specific form, use our contact page.
Reference: W3C WAI: Forms Tutorial, particularly labels, instructions and notifications.
