A UX audit is a structured review of an existing website or app that finds where users struggle, explains why, and ranks what to fix first. It is the design equivalent of a code review: an outside, evidence-based look at a live product, usually because conversion has stalled, support tickets keep repeating, or a redesign is on the table and nobody is sure what is actually broken.
This guide covers what a UX audit checks, the methods behind it, how the process runs, what the final report should contain, and how the work is scoped. It is written for founders and product owners deciding whether they need one.
What a UX audit is, and what it is not
A UX audit looks at a product that already exists. It asks whether people can find what they need, complete the key tasks, understand what is happening, and recover from mistakes. It combines expert review with whatever evidence the product already produces: analytics, session recordings, search logs, support tickets and customer feedback.
It is not a redesign, and it is not a visual critique. A good review may find that the interface looks fine and the real problem is a confusing pricing page, a form that asks for too much, or error messages that do not say what to do next. If you need a refresher on that distinction, our explainer on UI vs UX covers where the interface ends and the wider experience begins.
| UX audit | Usability testing | Redesign | |
|---|---|---|---|
| Starts from | The live product and its data | A product or prototype plus real users | A decision to change the product |
| Main method | Expert review plus analytics | Watching users attempt tasks | Research, design and build |
| Output | Prioritized list of issues and fixes | Observed problems and severity | New designs and code |
| Best when | You need to know what is broken and where to start | You need proof of how users behave | The audit shows structural problems |
What a UX audit checks
The scope depends on the product, but most audits cover the same core areas:
- Key journeys. Sign-up, onboarding, search, checkout, booking or whatever the product exists to do.
- Navigation and information architecture. Whether labels make sense and things live where users expect.
- Forms and inputs. Field count, labels, validation, error handling and defaults.
- Content and microcopy. Whether the words explain what to do, what happens next and what went wrong.
- Consistency. Whether the same component behaves the same way everywhere.
- Accessibility. Contrast, keyboard use, focus states, target sizes and screen reader basics.
- Performance as users feel it. Slow screens, layout shifts and missing loading states.
- Trust signals. Pricing clarity, security cues, reviews and policies at the point of decision.
The methods behind a UX audit
Heuristic evaluation
Most audits start with a heuristic evaluation: reviewers judge the interface against established usability principles. The best known are Jakob Nielsen's 10 usability heuristics, which include visibility of system status, match between the system and the real world, user control and freedom, consistency and standards, and error prevention. Nielsen Norman Group's guide on how to conduct a heuristic evaluation recommends that three to five people evaluate independently, so one reviewer's blind spots do not shape the result.
Analytics and funnel review
Analytics show where users drop out of key flows, which pages have high exit rates, what people search for and fail to find, and which devices perform worse. Session recordings and heatmaps, where available, show what happened on those pages. This is what turns opinions into priorities.
Accessibility review
The W3C's WCAG 2.2 is the usual benchmark. An audit checks the criteria that most often fail in practice, such as a contrast ratio of at least 4.5:1 for normal text, visible keyboard focus, a minimum size for pointer targets, labeled form fields and meaningful alternative text. A full conformance audit is a bigger job; a UX audit should at least flag the issues that block real users.
Usability testing
An expert review predicts problems; testing confirms them. Even a small round of sessions with real users on the two or three most important tasks adds evidence that is hard to argue with, and it often surfaces issues no reviewer expected.
Why checkout is where many audits pay off
For online stores, the checkout is usually the highest-value flow to audit. Baymard Institute's cart abandonment research puts the average documented abandonment rate at 70.22%, based on 50 studies. Many of those shoppers were only browsing, but Baymard's survey data shows that 17% of US online shoppers have abandoned an order because of a too long or complicated checkout process, and 40% cite extra costs such as shipping, tax and fees being too high.
The same research reports that an ideal checkout flow can be as short as 12 to 14 form elements, while the average US checkout shows 23.48 form elements by default. That gap between what is needed and what is shown is exactly the kind of issue an audit is built to find, and it is usually cheaper to fix than a new marketing campaign is to run.
How the UX audit process runs
- Agree goals and scope. Which journeys, which devices, and what business problem the audit should explain.
- Gather evidence. Analytics access, recordings, support themes, previous research and any known complaints.
- Map the key journeys. Walk each flow step by step on real devices and record every screen and state.
- Run the expert review. Independent heuristic evaluation and an accessibility pass.
- Test with users on the most important tasks, if scope allows.
- Consolidate and rate severity. Merge findings, remove duplicates and score each issue by impact and frequency.
- Recommend and prioritize. Pair each issue with a fix and an effort estimate, then order the list.
- Walk the team through it. A working session with design, product and engineering so fixes get owners.
The audit should feed directly into the next cycle of work. Fixes that need research or new flows go back into the normal UX design process; fixes to repeated components are best made once in a shared component library, which is the argument our design systems guide makes in detail.
What the UX audit report should contain
| Section | What it should include |
|---|---|
| Summary | The few issues that matter most, in plain language, with their business impact |
| Findings | Each issue with a screenshot, where it occurs, the principle or data behind it and its severity |
| Evidence | Analytics, recordings or test clips that support each major finding |
| Recommendations | A specific fix per issue, not "improve the UX" |
| Priority list | Issues ordered by impact versus effort, so the team knows what to do first |
| Quick wins | Changes that are cheap and low risk, such as copy, labels and field removal |
How a UX audit is scoped and priced
There is no standard price for a UX audit, because the work scales with what is reviewed. The main drivers are the number of journeys and platforms, whether usability testing is included, the depth of the accessibility review, how much analytics data exists, and whether the report includes design mockups of the fixes. An audit of one checkout flow on mobile is a very different job from a review of a multi-role SaaS product on web and two apps.
When you compare proposals, ask which journeys are covered, how many reviewers take part, whether real users are tested, what the report contains and whether a walkthrough session is included. Those answers explain most of the difference between quotes.
Running a UX audit with us
Our UI/UX and product design team runs audits that combine independent expert review, analytics, an accessibility pass and, where it matters, a short round of user testing. You get a prioritized fix list with evidence for each item and a working session with your team. Because we also build products, we can estimate the engineering effort behind each fix, and help ship them if you want.
If your product has a flow where users keep dropping off and you are not sure why, tell us what you are seeing. We will reply within one business day with how we would scope the review.
Frequently asked questions
What are UX audits?
A UX audit is a structured review of an existing website or app that finds where users struggle and ranks what to fix first. It usually combines a heuristic evaluation, analytics review, an accessibility check and sometimes usability testing. The output is a prioritized list of issues with evidence and recommended fixes.
How much does an UX audit cost?
There is no standard price, because the cost scales with scope. The main drivers are how many journeys and platforms are reviewed, whether real users are tested, the depth of the accessibility review and whether the report includes redesigned screens. Ask for a written scope that lists those items so quotes can be compared fairly.
What exactly does UX mean?
UX stands for user experience. Nielsen Norman Group defines it as all aspects of the end user's interaction with a company, its services and its products. It is broader than the interface: it includes whether the product actually meets the user's need, from first visit to getting help.
Is UI/UX replaced by AI?
In our view, no. AI tools can speed up parts of the work, such as summarizing feedback or spotting patterns in analytics. They cannot watch your users struggle with a real task, weigh a fix against business constraints or take responsibility for a design decision, and those are the core of a UX audit.
What is the difference between a UX audit and usability testing?
A UX audit is a broad expert review of a live product, supported by analytics and standards such as WCAG. Usability testing means watching real users attempt specific tasks. A good audit often includes a small round of usability testing to confirm the most important findings.
