How to Improve Enquiry Form Conversion: Fix the Leak Before You Buy More Traffic

Most businesses that come to us convinced they need more traffic are quietly losing the leads they already have. The ads work. The rankings are fine. Someone lands on the page, reads it, decides they are interested, and then meets a form that wants eleven pieces of information before it will let them speak to a human. Enquiry form conversion is the least glamorous number in digital marketing and almost always the cheapest one to move. It does not need a bigger budget. It needs you to stop making people work for the privilege of giving you money.

More traffic will not fix a form problem

Run the arithmetic on your own site. If 1,000 people visit your contact page in a month and 20 of them send an enquiry, doubling your ad spend to bring 2,000 people gets you 40 enquiries and double the media cost. Getting that same 1,000 visitors to send 30 enquiries instead gets you half the increase for nothing. One of those levers you pay for every month forever. The other you pull once.

This is why we push back when a client asks for a budget increase before anyone has looked at the page the budget points at. Buying more traffic into a leaking form is the most expensive way to grow, and it is the option most agencies will happily sell you.

It is not only a lead volume issue either. On paid search, the page you send people to is assessed as part of ad quality. Google treats landing page experience as one of the three components of Quality Score, alongside expected clickthrough rate and ad relevance. A page that frustrates people is a page that costs you twice.

Every field is a question you are asking a stranger

The single most common fault we find is field count. Someone in the business wanted to know company size, so a dropdown got added. Someone in sales wanted budget range, so that got added too. Then "how did you hear about us", then a second phone number, then a checkbox nobody reads.

Each of those is a small ask made of a person who has known you for ninety seconds. Be honest about which answers you genuinely need before you can have a useful conversation, and which ones you just quite like having. For most service businesses the honest answer is a name, a way to reply, and a box where they can say what they want. You can ask everything else on the call.

If your sales team insists on qualification data, get it after the enquiry, not before. A short follow-up email to someone who has already raised their hand converts far better than a dropdown to someone who has not.

Make the form behave like a form

There is a well-established body of guidance here, and it is not the sort of thing you need to test from scratch. Chrome's own guidance on form design basics covers most of it: give every control a visible label, put that label above the field rather than beside it so the page can be scanned in one pass, and use a single column so there is only ever one direction to travel.

A few specifics from the same guidance that get ignored constantly:

Placeholders are not labels. Grey text inside the box disappears the moment someone starts typing, which means anyone who gets interrupted has to delete their answer to remember what was being asked.

Tap targets should be at least 48px. Buttons and checkboxes sized for a mouse are a genuine obstacle on a phone, and phones are where most of your enquiry traffic is.

Set form fields to at least 1rem. Anything smaller triggers a zoom on iOS Safari the moment a field is focused, which throws the layout around and feels broken even though nothing has actually broken.

Use the right input type. A telephone input type gives someone a number pad, and an email input type gives them a keyboard with an @ on it. This is a one-line change that removes real friction on every mobile enquiry you ever receive.

Errors should not be a guessing game

Second only to field count, the thing that kills a half-completed form is a validation message that appears at the top of the page saying something went wrong, without saying where. Show the error next to the field it belongs to, and when a submission fails, move the user to the first invalid field rather than leaving them to hunt.

The same applies to requirements. If the phone field will reject anything with spaces in it, say so before someone types their number with spaces in it. Rejecting an answer you never explained you needed is the fastest way to lose an enquiry that was already yours.

You cannot fix what you are not measuring

Plenty of sites we audit have no reliable record of form submissions at all. Someone is counting thank-you page views, which misses every AJAX form, or counting nothing and going on gut feel.

Google Analytics collects a generic form submission event, but that lumps every form on the site together, including newsletter signups and search boxes. The useful setup is to create a specific event for your lead form and mark it as a key event, matched on the form's name attribute. That gives you a number you can actually watch, and a number you can feed back into your ad platforms.

Once you have that, the diagnosis gets much easier. If people reach the page and never start the form, the problem is the page or the offer. If they start it and abandon it, the problem is the form itself.

Where to start this week

Open your own enquiry form on your own phone, on mobile data, and fill it in properly. Not a test submission with "test" in every box. A real one, as a stranger would. Most people find at least two of the faults above inside a minute.

Then cut the fields you cannot defend, fix the labels, and make sure the submission is being tracked. That is a morning of work on most sites and it costs nothing per month, which is more than can be said for the alternative.

If you want someone to go through it properly, our conversion rate optimisation work starts with exactly this kind of audit, and our web development team can implement the fixes if your current setup will not let you. Get in touch and we will tell you what we would change.