An enquiry journey can fail between a promising first visit and the moment someone tries to contact you. The website may describe the wrong service, hide its coverage area or send a completed form to an inbox nobody checks.
This scorecard follows that journey in order. Use a phone, choose one service and test the website as a new customer would.
There are ten checks, each worth up to two points. Give zero when the task fails, one when it works with difficulty and two when it is clear and straightforward. The maximum is 20. Use your score to track improvements on your own site rather than as an industry benchmark.
Open the page a potential customer would reach from search. Can you identify the service without returning to the homepage?
Write down any important information that only appears elsewhere. The landing page should give people enough context to continue.
Look for the locations you actually cover. A visitor in Abbeyleix or Stradbally should be able to work out whether it is sensible to enquire.
If travel limits, delivery zones or call-out conditions apply, make them easy to find. Only list places you genuinely serve.
Choose a common question from recent customer calls. Can the website answer it?
Examples include the type of work accepted, what information is needed for a quote or whether an appointment is required. Record the missing answer rather than adding a general FAQ for its own sake.
Look for an example, photograph or testimonial connected with the service you chose. Can you understand what the business did and why it is relevant?
Avoid treating a row of unexplained logos as a substitute for useful detail.
From that same page, find the route to call, book or request a quote. Check whether the wording matches what happens next.
A button labelled “Get a quote” should lead to a clear quote enquiry process, with any necessary next steps explained.
On your phone, tap the number and confirm that the expected number appears in the call screen. Cancel before placing the call unless you are ready to test the business response.
Check the number on the service page as well as the contact page.
Use a clearly labelled test enquiry. Check the labels, keyboard behaviour, required fields and any attachment limits.
Include the information a real customer would have. Note anything the form requires that they are unlikely to know.
After submitting, confirm that the website acknowledges the action. Does it explain what happens next?
Distinguish a message saying the form was submitted from proof that the business received it.
Check the intended inbox and any configured enquiry record. Verify that the message contains usable contact details and enough context to respond.
If it has not arrived, record the failure for investigation before changing design elements.
Try the same journey on a desktop or a second phone. Check menus, overlapping elements and buttons that become difficult to use at a different size.
Fix failed contact actions first, then unclear service information and unnecessary effort. Repeat the same tests after each change and record the result.
For help with page structure, see Web Design Laois. For ongoing technical care, review our maintenance plans. You can also send us your website address and describe where the enquiry journey is breaking down.
