UX audit: what you get and when it is worth it
A UX audit is a structured expert review of a website or app that ends in a prioritised list of usability problems and fixes. It takes days or weeks, needs no test participants and costs less than most research. It is worth buying when you have a live product, a suspicion that something is wrong and no clear list of what to fix first.
What a UX audit is
In an audit, one or more specialists walk through your key journeys and assess them against established usability principles, accessibility guidance and, in some cases, a benchmark database. The same activity is sold as an expert review or a heuristic evaluation.
An audit relies on expert judgement. It predicts where users will struggle. It does not observe them struggling, which is the job of usability testing.
What you should receive
| Deliverable | What it contains | How you use it |
|---|---|---|
| Issue list | Each problem with a screenshot, location and explanation | Becomes backlog tickets |
| Severity rating | A ranking of issues by impact on users and on the business | Decides what to fix first |
| Recommendations | A proposed fix for each issue, sometimes with a sketch | Briefs designers and developers |
| Scorecard or benchmark | Scores per area, compared with a standard or with competitors | Shows progress when the audit is repeated |
| Walkthrough session | A presentation of the findings with time for questions | Aligns stakeholders on priorities |
Two published examples
Clearleft sells an expert UX review as a fixed package. Two senior consultants review up to three key journeys in two weeks, for £7,475 excluding VAT.
Baymard Institute's standard UX audit is aimed at e-commerce sites. It reviews desktop and mobile across six core UX areas and delivers a performance scorecard, a report with 40 prioritised improvements, a presentation of about two hours and up to four advisory calls. Baymard gives a typical timeline of 15 to 25 business days and tailors the price to the site.
The two show the main variants. One is a general review by senior practitioners. The other measures a site against a research database for one sector.
When an audit is worth the money
- The product is live and has real traffic, but conversion or task completion is below expectations
- A redesign is planned and you want to know what to keep and what to change
- The team disagrees about priorities and needs an outside view
- You inherited a product and want a fast assessment of its condition
- Budget or time rules out a full research study this quarter
When to skip it
- The product does not exist yet. Concept testing or interviews will tell you more.
- The real doubt is whether anyone wants the product. An audit checks usability, not demand.
- Nobody has capacity to fix what the audit finds.
- You were audited recently and have not implemented the last set of findings.
Audit or usability test
An audit is faster and needs no recruitment. It finds violations of known principles, such as unclear labels, missing feedback or forms that ask for too much.
A usability test finds problems specific to your users and your content, which no checklist can predict. It also produces recordings, and those persuade sceptical stakeholders better than a report does.
The two work well in sequence. Audit first, fix the obvious issues, then test, so participants spend their time on problems an expert could not foresee.
How to prepare for an audit
- Choose the two or three journeys that matter most to revenue or to support costs.
- Share analytics for those journeys, including drop-off points.
- Provide test accounts and realistic data, so reviewers see what customers see.
- Name one person who will own the findings afterwards.
- Reserve design and development time for the weeks after delivery.
Common questions
How long does a UX audit take?
Published packages give a range of two to five weeks. Clearleft's expert review takes two weeks. Baymard Institute states 15 to 25 business days for its standard audit. A larger product or more journeys will extend that.
Can we run a UX audit ourselves?
Yes, and it is a useful exercise. The limits are familiarity and politics. People who built a product stop noticing its obstacles, and internal findings are easier to dismiss than an outside report.
Does a UX audit cover accessibility?
Only partly, unless the scope says so. A UX audit will usually flag visible issues such as contrast and missing labels. A full accessibility audit against WCAG is a separate, more technical piece of work.