What is a UX audit?
A UX audit is a structured review of an existing product that finds usability problems and ranks them by how much they hurt users.
also calledUX review · usability audit · heuristic evaluation · experience audit
Think of a home inspection before you renovate. Nobody tears out walls at random; someone walks through the house with a checklist, notes the leaky pipe and the crooked stairs, and tells you which repairs matter first. A UX audit does that for a website or app that already exists.
- An audit reviews an existing product against agreed standards and produces a ranked list of issues.
- Severity ratings matter more than the length of the list.
- It is expert judgment, so pair it with real user testing before big decisions.
- Run one before a redesign, not after.
What actually happens during an audit
An auditor goes through your product the way a stranger would, screen by screen and task by task, and compares what they find against a set of agreed standards. Those standards are often usability heuristics, accessibility guidelines and your own design system or brand rules.
The raw material comes from a few places: the live product itself, analytics that show where people drop off, support tickets, and any past research. The output is not a vague opinion. It is a list of specific findings, each with a screenshot, a short explanation and a severity rating.
Why bother when you could just redesign?
Because a redesign without a diagnosis is a guess with a big budget attached. An audit tells you whether the real problem is the navigation, the checkout form, the copy or something nobody had thought about, like text that fails contrast checks.
It also gives a team a shared, neutral document. Instead of three people arguing about what feels off, you point at finding number 14 and its severity score. That alone saves a surprising number of meetings.
How to run one, step by step
- Agree on scope. A whole product, one funnel, or just the sign-up flow? Smaller is usually better for a first audit.
- Collect context: goals, analytics, support complaints, earlier research.
- Pick your yardstick, for example Nielsen's ten heuristics plus WCAG for accessibility.
- Walk the key journeys and note every issue with a screenshot and where it happened.
- Rate each finding by severity and by how many users it likely affects.
- Write it up so a busy stakeholder can read the top five findings in two minutes, with the full list behind it.
Having two reviewers work independently and then compare notes catches a lot more than one pair of eyes.
Where audits go wrong
The classic failure is a 90-page report that nobody opens. If every finding is labelled critical, none of them are. Prioritize hard and recommend what to fix first.
The other trap is treating an audit as proof. It is an expert judgment, not evidence from real users. An auditor can tell you a form looks confusing; only watching people use it tells you for sure. Good teams use the audit to decide what to test next.
When an audit makes sense, and when it does not
Reach for one before a redesign, after a drop in conversions you cannot explain, when you inherit a product you did not build, or when a new designer needs to understand the current state quickly.
Skip it for something that has not launched, since there is nothing to audit yet. In that case, usability testing on a prototype gives you more.
UX audit: your questions, answered
What is a UX audit?
A UX audit is a systematic review of a live product, checking its screens and journeys against usability, accessibility and brand standards. The result is a prioritized list of problems with evidence and recommended fixes, so a team knows what to improve first.
How long does a UX audit take?
A focused audit of one flow can take a couple of days, while a full product review might run two to four weeks. The time depends on scope, how much analytics data you can access, and how many reviewers are involved. Narrow the scope first if the timeline is tight.
What does a UX audit include?
Usually a scope statement, the criteria used, a list of findings with screenshots, severity ratings, and prioritized recommendations. Many also include analytics highlights and an accessibility check. A short executive summary on top helps stakeholders who will not read the whole thing.
Who should perform a UX audit?
Ideally someone who did not design the product, because fresh eyes spot things the team has stopped seeing. That can be an internal designer from another team or an outside consultant. Two independent reviewers is better than one if you can manage it.
What is the difference between a UX audit and usability testing?
An audit is an expert reviewing the product against standards, while usability testing watches real people try to complete tasks. The audit is faster and cheaper, but only testing shows how actual users behave. They work best together.
More quick answers
Is a UX audit the same as a heuristic evaluation?
Not quite. A heuristic evaluation is one method that can be part of an audit. An audit is broader and may also cover accessibility, analytics and content.
How much does a UX audit cost?
It varies widely with scope and who does it. A single-flow review is far cheaper than a full-product audit, and an internal review costs only your team's time.
What tools do you need for a UX audit?
A spreadsheet or Figma file for logging findings, screenshots, and access to analytics are usually enough. Accessibility checkers and screen recording tools help but are optional.
When should you do a UX audit?
Before a redesign, after an unexplained drop in conversions, or when you inherit a product. It is also useful once a year as a health check on a mature product.
Can you audit a product that has not launched?
You can review a prototype against heuristics, but a true audit looks at a live product with real data. For unlaunched work, usability testing is usually the better use of time.
Heuristics in UX are broad rules of thumb for good interface design, used to judge a product and spot usability problems without running a full user study.
Usability testing in UX is a method where you watch real people try to complete realistic tasks with a product to find where they struggle.
Accessibility in UX means designing products so people with disabilities can perceive, operate and understand them, with or without assistive technology.
Competitor analysis in UX is studying how rival products solve the same user problems, so you can spot strengths to match and gaps your design can fill.
Usability in UX is how easily and satisfyingly specific users can reach their goals with a product, measured by learnability, efficiency and error rates.
Found this useful? A GitHub star helps other designers find it.