UX audits: finding real obstacles in a website
Choose meaningful journeys, gather evidence, prioritise findings and verify fixes without turning an audit into a list of personal preferences.
ecomvision editorial team
2 min
Published
Key takeaways
- 01Start with user tasks and available evidence.
- 02Describe observable problems in each finding.
- 03Prioritise consequences and frequency rather than visual prominence.
Select the journeys
Define tasks such as choosing a service, comparing options or sending an enquiry. Record the entry point, device and expected result.
Support requests and analytics help select an area, but they do not automatically explain the cause of behaviour.
Capture observations
Record the step, difficulty and consequence. “The button is invisible” is weaker than describing a user repeating submission because an error appeared outside the viewport.
Separate observation from interpretation. Suggest a study or measurement when the cause remains uncertain.
Assess the impact
Prioritise blocked journeys and lost data, then comprehension and unnecessary actions. Consider frequency, affected users, implementation cost and confidence.
A critical obstacle can matter more than numerous spacing comments.
Verify the fix
Define an acceptance condition and repeat the same task after changes. Compare similar traffic sources and periods when evaluating business effects.
The deliverable is an evidence-based plan. A complete redesign is not always required; a precise change to copy, feedback or structure may resolve the main issue.
- Context and steps to reproduce the issue.
- The observation separated from its possible cause.
- A priority and proposed solution.
- A verifiable acceptance condition.