Website visits without enough enquiries

People visit your website. What stops them taking the next step?

The reports show visits. The inbox doesn’t show enquiries to match. Between the two sit four questions, each with a different answer. Are these the right visitors? Does the page help them decide? Can they actually complete the action? And is that action being recorded properly? A low conversion rate answers none of them on its own. It’s a reason to look.
Talk about your website’s performance
Look at where the journey breaks down

First, agree what a useful conversion means.

Start with the number, because it may be counting the wrong thing. A visit is a person arriving. A click on “Contact us” is a person considering it. A form confirmation is a message that left their screen, which isn’t the same as one that arrived. A submission is anyone who filled the form in, including the people you’d never take on. What the business actually wants is narrower than all of those: a suitable enquiry that reached the right person. If your rate counts anything else, it’s telling you something. Just not that.

Then ask what’s being mixed together. One headline figure often blends phones and desktops, every page on the site and every source of traffic. A form that fails on a phone can hide inside a healthy average. So can a campaign sending the wrong people. There’s no universal good conversion rate. Compare a page with itself, over time, for one defined action.

Follow the journey from arrival to enquiry.

Pick one page that matters and one kind of visitor who should enquire. Then walk their route. Four things have to go right, in order, and each one can be checked.
01

Arrival. Did they expect this?

Did the visitor expect the service and the audience this page serves?
Check
Where they came from, whether the search term, the ad or the link, against the first thing the page says.
02

Decision. Can they judge you?

Can they understand the offer and find enough proof to decide?
Check
The page content, how clearly the service is explained, whether there are useful examples, and what intended users say when you watch them try.
03

Action. Is the next step reasonable?

Is it the right step for where they are, and practical to complete?
Check
The calls to action, what the form demands, how it behaves on a phone, the error messages, and anything that blocks someone using a keyboard or a screen reader.
04

Completion. Did it arrive?

Does the action work and reach its intended destination?
Check
A controlled test submission, confirmation from the recipient, and whether the records on both sides match.
Most obstacles found this way are hypotheses, not verdicts. Someone experienced can spot likely trouble on a page. They can’t tell you the commercial cost of every design choice by looking. That takes evidence, and the strip shows where to gather it.

Fix what is broken. Investigate what is uncertain.

Three kinds of finding come out of a walk-through. The sentence you’d use to describe each one tells you how to treat it.

“It doesn’t work.”

The form fails, the booking button does nothing on a phone, the enquiry lands in an inbox nobody reads. That’s a fault. Fix it, then verify it end to end.

“People don’t get it.”

The service is hard to understand, or the next step isn’t clear. That’s a usability or communication concern. Investigate it with the people it’s for and the evidence you have, then change what the evidence supports.

“It might do better.”

A different headline, a different layout, a shorter form. That’s a hypothesis. Whether you can evaluate it properly depends on how many suitable visitors and completed actions you have.
The last one matters for specialist and smaller businesses. A controlled comparison needs a volume most enquiry-led sites don’t have. Without it, user feedback, journey checks and carefully watched changes still inform good decisions. You just stay honest about what they prove. A rise after a change is worth noticing. It isn’t proof that the change caused it.

More form submissions are not always better.

The budget question

An illustration of the judgement involved. Not a client, and not a result.
A renovation builder’s enquiry form asks for an approximate budget. Someone suggests removing it, because shorter forms get more submissions. That’s probably true. It’s also true that the budget question is how the estimator tells a large project from a small repair before spending an afternoon on it. Remove it and submissions rise, the good enquiries get harder to spot, and the team pays the difference in time. The right call weighs what the question does against the cost of asking it, to the visitor, and the cost of not knowing, to the team. Sometimes the answer is to keep it, make it optional and say why it’s asked.
THE COST OF ASKINGto the visitorTHE COST OF NOT KNOWINGto the team

The wrong crowd

Same label.
A landing page for an ad campaign converts poorly. The button is fine. The ad’s wording is broad, so half the visitors want something the page doesn’t offer. A more prominent button would ask the wrong people to enquire more often. The fix is the ad, the audience or the first line of the page. And if most of your visitors are the wrong people across the whole site, the issue isn’t conversion at all. It’s who’s arriving.

Make the change the evidence supports.

Our part is to agree the action that matters, walk one important journey, check the implementation and the measurement, and agree which changes are worth making. Then make them, and check that they did what we expected. That might be focused copy, design, development or tracking work. It doesn’t always mean a website project. Where the experience needs broader work, that’s design. Where the implementation is the problem, that’s development.

The first conversation is free. Investigation and implementation are scoped separately, and the Conversion Optimisation page explains how that engagement works.

Tell us which page, which action visitors should be completing, and what the reports say now.

Talk about your website’s performance

Two things this page doesn’t cover.

If enquiries arrive and then stall, that’s a different problem.
We get enquiries but not enough sales
If you can’t trust the reports across your channels, that’s another.
We don’t know what’s working