When a website has visitors and no enquiries, the cause is rarely the contact button, and redesigning the page is rarely the first fix. The leak is usually earlier in the visitor's journey: the wrong people are arriving, the first screen does not say what you do and for whom, or the way forward is unclear. The efficient method is to check in the order a visitor meets the site, because a fault early on makes every later fix irrelevant.
First: are these the people you want?
Traffic is not demand. A page that ranks for a broad phrase can collect a large audience of people who were never going to buy: students, competitors, people looking for something adjacent. Look at the queries and sources that actually bring visitors, and ask honestly whether the person behind each one has a problem you solve.
This is the cheapest diagnosis and the one most often skipped, because it implies the traffic is worth less than the report says. If a small share of visitors are the right ones, no amount of work on the page will raise the number past the size of that share.
Second: does the first screen say what you do, and for whom?
A visitor decides within seconds whether this is the right place, and they decide on the first screen. It needs to say what you offer, who it is for, and why it is different, in words a stranger understands. Phrases that could describe any company in your category tell the visitor nothing.
A useful test is to show the first screen to someone unfamiliar with your business for five seconds, then ask what the company does and who it is for. Whatever they cannot say is where the page is losing people.
Third: is there one obvious next step?
Pages that offer a phone number, a form, a chat window, three downloads and a newsletter ask the visitor to choose, and a visitor who has to choose often does not. Decide what the single most valuable action is and make it the most visible one, with the others plainly secondary.
The step should also match how ready the visitor is. Someone reading about a service for the first time is not ready for “book a call”; offering a lower-commitment step, such as a clear description of how the process works, can be the difference between leaving and writing to you.
Fourth: what does it cost to ask?
Every field in a form is a small cost, and on a phone, where typing is slow, the cost is larger. Open your own contact form on a mid-range phone and complete it. Notice what is hard: a keyboard that covers the field, a required question that feels intrusive, an error that appears only after sending.
Remove what you do not need to reply, and make the remaining questions easy. You can ask for the rest in your answer.
Fifth: is anyone counting correctly?
Before concluding that nobody is enquiring, confirm that enquiries are being counted. Calls, messages through a chat app, and forms that fail silently do not appear in many reports. If the form's confirmation never reaches your inbox, or the phone number is tapped but never recorded, the site may be working better than the figures say.
Send a test enquiry through every route a visitor can use and check that each one arrives where a person will see it, and that it is counted. This is the quickest step on the list, and it sometimes ends the investigation.
What not to do first
Do not start by redesigning the home page, buying more traffic, or adding a pop-up. Each of them works on a later link in the chain while the faulty one is earlier, and more traffic through a leaking page simply means more people leaving. Decide first what counts as an enquiry, how you will recognise one, and what the current rate is. Without that baseline you cannot tell whether anything you change has helped, and every change becomes a matter of opinion.
And then the reply
Even a perfectly working site loses enquiries to slow answers. Someone comparing three suppliers writes to all three, and the one who replies first and clearly is usually the one who gets the conversation. This sits outside the website, but it is the last link in the same chain, and it is worth looking at before paying for any further changes to the page.