Reputifly editorial · Reviewed 27 September 2026 · 2 min read
Assess clarity, navigation, evidence, performance and enquiry handling through actual visitor tasks.
Give someone a task
Choose a realistic task such as finding a service price range, checking relevant work or requesting a quote. Let someone unfamiliar with the site attempt it without coaching. Record where they pause, misunderstand or leave. A design preference is useful feedback; an observed task failure is stronger evidence for a repair.
Use five tests
- Clarity: can the visitor identify the offer and who it suits?
- Navigation: can they reach the information needed to make a decision?
- Evidence: can they inspect real work, credentials or attributed feedback?
- Performance: does the page remain usable while media loads?
- Completion: does the enquiry reach the team, with an understandable confirmation?
Test more than the opening screen
On mobile, open the menu, scroll through a long page, expand an image and use a form with the keyboard visible. On desktop, use the keyboard to reach links and controls. Test a failed submission as well as a successful one; errors should explain the correction without clearing everything the visitor entered.
Separate measurements from impressions
Record the device, browser, URL and steps for every defect. Performance testing should distinguish a controlled lab result from real visitor data. Core Web Vitals cover loading, responsiveness and layout stability; they do not replace a usability review.
Turn the review into a small repair list
Fix blocked tasks first, misleading or missing information next, and decorative refinements afterwards. Give each repair an acceptance check: for example, “a mobile visitor can submit a valid enquiry and see the confirmation without horizontal scrolling”. Revisit the same task after deployment.
