Start with a specific visitor task
Choose an important service page and a real situation from your sales conversations. Give someone from your target audience a task like the example. Avoid explaining the page as they go: ask them to show where they look for an answer and what next step they expect.
Record the URL, device, language, task and exact place where they get stuck. “Cannot find the service scope” is more useful than “The design looks dated”. If an external participant is unavailable, start with a colleague who did not help create the page.
Separate the offer, suitability and evidence
Can the participant explain what you deliver? Do they recognise which situations the offer suits and which services are excluded? Can they find evidence for your claims? A reference describing a specific task and result answers a different question from a sample deliverable. Make that distinction clear.
Present the key answers as visible text. Google recommends making important content available in text form for its search and AI features. For multilingual sites, check the service scope and contact journey in each language; translating menu items alone is insufficient.
Check mobile use, loading and the form together
Repeat the task on a phone and a desktop. While loading, note whether the offer and contact route are already usable, whether content shifts, and whether a banner or on-screen keyboard covers a button. Investigate specific images or embedded elements that cause problems; an overall score alone cannot tell you whether the task succeeds.
Check the form with the person responsible: are required details understandable, do labels remain visible while typing, and can an input error be corrected? W3C explains how labels are technically associated with their fields. Send an agreed test message and verify the confirmation, actual receipt and responsibility for replying.
Choose the next change from the observed obstacle
First fix errors that prevent enquiries or cause them to be lost. Then address misunderstandings about the offer and suitability, and missing evidence. Prioritise a loading problem immediately if it makes content or controls unusable; in the example, a late decorative image matters less than the covered send button.
For each change, write down the observed obstacle, proposed correction, responsible person and task for the repeat test. Start with the existing website. An unclear introduction initially needs clearer text. Whether the system needs replacing depends on whether the necessary changes can be implemented reliably within it.
Assess removed obstacles and suitable enquiries separately
Repeat the same visitor task after a correction. Record a concrete result: “Participant can name the service” or “Test enquiry arrived”. This verifies the individual improvement, but not an increase in suitable enquiries.
Separately define a suitable enquiry, such as a maintenance request for supported equipment in the service area. Distinguish a contact click, a received enquiry and a suitable prospect. Compare over a meaningful period and record changes to campaigns or offers. Individual days and a handful of contacts do not support a reliable claim of increased conversion.