Start with one real visitor goal
Website reports show which pages people open, but they rarely show whether people accomplish what they came to do. A visitor might read three pages because the information is helpful—or because it is hard to find. To examine the difference, choose one task and watch how a few people attempt it. This is a practical measurement exercise, not a test of the people taking part.
Pick a task that matters to your visitors and has a recognizable end point. Examples include finding the opening hours for a particular service, locating eligibility requirements or identifying how to request a quote. State the goal without giving away the route: “Find out how to request a quote for this service” is more useful than “Open the Contact page and click the quote button.” Keep the task narrow enough that you can observe what happens from start to finish.
Set up a small, fair check
Ask a few people who are not responsible for maintaining the site to try the task. They do not need to represent every visitor for the exercise to reveal confusing labels or missing information. If possible, include people who use different devices or ways of navigating. Let each person use a device and browser they are comfortable with, and tell them that stopping or asking for clarification is fine.
Give everyone the same starting point, such as the homepage or a relevant page that visitors commonly reach. Read the same task wording each time. Avoid hints while someone works; a prompt such as “Have you tried the menu?” changes what you are measuring. If a person gets stuck, note where it happened before offering help. Ask permission before taking notes or recording anything, and avoid collecting names or other details you do not need.
Record behavior, not just a pass or fail
Prepare a simple sheet with the task, starting page and a few observation fields. Record whether the person reached the correct destination, where they first looked, which labels they chose and where they hesitated or turned back. Note whether they needed help and what help was given. You can also record an approximate completion time, but do not treat a small timing difference as proof that one design is better.
Separate what you saw from what you think it means. “Opened Services, returned to the homepage, then used search” is an observation. “The Services menu is confusing” is a possible explanation that needs checking. After the attempt, ask a neutral question such as “What, if anything, made that difficult?” A person may explain a choice you could not understand from clicks alone.
Look for patterns you can act on
Review the attempts together rather than treating every wrong turn as a separate problem. Did several people overlook the same link? Did they expect one label to lead somewhere else? Did they find a page but remain unsure what to do next? These patterns can point to manageable changes: a clearer link label, a more direct page heading, a missing detail or a stronger next step.
Prioritize problems by their effect on the task. A minor detour is less urgent than a dead end that prevents someone from getting essential information. Before changing the site, write down what you expect the change to improve. For example: “A link labeled ‘Request a quote’ on the service page should make the next step easier to spot.” This gives you a specific question to revisit instead of a vague hope that the site will feel better.
Repeat the task after making a change
Make one or two focused changes, then ask different people to attempt the same task from the same starting point. Compare the routes they take, the places they hesitate and whether they can finish without help. A small check cannot establish how every visitor behaves, but it can show whether an obvious obstacle persists. If the change helps one task while making another harder, examine both before declaring the work finished.
Keep a short record of the task wording, observations, changes and follow-up results. Over time, these notes become a useful companion to analytics: the numbers may show where visitors go, while task checks help explain what they can actually do there. Repeat the exercise when an important service, navigation label or page structure changes, rather than waiting for a large redesign.
