Your site gets steady traffic, but sign-ups stay flat. Your app gets downloads, but people stop opening it after a week. Support keeps answering the same “where do I find…” questions. Something in the experience is getting in the way, and nobody on the team can point to exactly what.
A UX audit is how you find out. It is a structured review of a live website or app that combines expert inspection, analytics, session recordings and, ideally, testing with real users to find where people struggle and why. You need one when results drop without a clear cause, before a redesign, or after a big launch. This guide explains what an audit covers, the signs that you need one, the main methods, what you should get back, a practical checklist, and how to turn findings into fixes.
What a UX audit is (and what it is not)
A UX (user experience) audit is a diagnostic review of an existing product. The reviewer works through your most important user journeys, such as signing up, checking out or booking a demo, and records every point where the design slows people down, confuses them or causes errors. Each issue is backed by evidence, rated for severity and paired with a recommended fix.
An audit looks at what is live today and tells you what is broken. It does not redesign anything, but its findings decide whether you need targeted fixes or a bigger rebuild. Our guide to the UI/UX design process shows where an audit fits.
| UX audit | Usability test | Redesign | |
|---|---|---|---|
| What it is | Broad review of a live product using several methods | Watching real users attempt set tasks | Rebuilding the design, often from the structure up |
| Main question | Where and why do users struggle? | Can people complete these specific tasks? | What should the product look like now? |
| Output | Prioritized list of issues and fixes | Observed problems, notes and clips | New wireframes, designs and prototypes |
Signs you need a UX audit
- Traffic grows but conversions do not. More visitors with the same number of leads usually means a page or form is losing people. Our post on why a website is not generating leads covers the non-UX causes to rule out too.
- One funnel step loses far more people than the rest. A checkout page, a long form or the second onboarding screen is a common culprit.
- Support tickets repeat the same confusion. If many people ask where their invoice is, the interface is not answering that question.
- Mobile results trail desktop by a wide margin. Layouts designed on a large screen often break down on a phone.
- You are about to redesign. Auditing first means the redesign targets real problems instead of the loudest opinions in the room.
- You plan to spend more on ads. Paying for traffic that lands on a leaky page wastes budget, so fixing the page first makes any digital marketing spend work harder.
The main UX audit methods
No single method sees everything. Expert review finds likely problems quickly, data shows where problems happen and at what scale, and recordings and tests show why. A useful audit combines at least two of these.
Heuristic evaluation
A heuristic evaluation is an expert usability review against established principles. The most widely used set is Jakob Nielsen’s 10 usability heuristics, first published in 1994 and maintained by Nielsen Norman Group:
- Visibility of system status
- Match between the system and the real world
- User control and freedom
- Consistency and standards
- Error prevention
- Recognition rather than recall
- Flexibility and efficiency of use
- Aesthetic and minimalist design
- Help users recognize, diagnose, and recover from errors
- Help and documentation
For example, a sign-up form that wipes every field when one entry is invalid breaks both error prevention and error recovery. Nielsen Norman Group recommends that three to five people evaluate the same interface independently, because any single evaluator misses some issues. It also notes that heuristic evaluations are not a replacement for user research, so confirm the important findings.
Analytics review
Your analytics show where people leave. Look at funnel drop-off step by step, then split it by device, traffic source and landing page. Site search terms show what people expected to find and could not.
Check your tracking before trusting any of it, because duplicate events or missing conversions will send the audit in the wrong direction. Our guide to GA4 conversion tracking covers how to set this up properly.
Session recordings and heatmaps
Tools such as Microsoft Clarity or Hotjar record sessions and show where people click and scroll. Filter to visitors who dropped off at your problem step, then look for repeated clicks on things that are not clickable and form fields people start but abandon. Make sure personal data is masked and your cookie consent setup covers the tool.
Usability tests
Give a handful of people from your target audience realistic tasks and watch them work, either in person or over video. Ask them to think aloud. Nielsen Norman Group’s research found that testing with five users uncovers about 85% of usability problems, and that several small rounds with fixes in between beat one large study. Pick your tasks from the problem areas the analytics revealed.
| Method | What it finds | What it misses | Effort |
|---|---|---|---|
| Heuristic evaluation | Inconsistency, missing feedback, confusing labels | Whether real users care about the issue | Low |
| Analytics review | Where people drop off, and how many | Why they drop off | Low to medium |
| Session recordings | The behavior behind the drop-off | What users expected to happen | Medium |
| Usability tests | Why people struggle, in their own words | How often the problem occurs at scale | Medium to high |
What a UX audit should deliver
A good audit leaves you with something your team can act on, not a deck of opinions. Expect:
- Scope summary: which journeys, devices and methods were covered.
- Issue log: each problem with its location, a screenshot or clip, the evidence behind it and a recommended fix.
- Severity ratings: a simple scale such as critical (blocks the task), major (causes errors or delays) and minor (friction or polish).
- Prioritized roadmap: quick wins separated from larger changes that need design and development time.
- Baseline metrics: the current numbers you will measure improvements against.
For the bigger fixes, the next step is usually annotated wireframes or a clickable prototype, which is where UI/UX design work picks up from the audit.
A practical UX audit checklist
Use this usability review checklist on each key journey, on both desktop and mobile:
- Navigation: Can a new visitor tell what you offer and where to go next? Do menu labels use your customers’ words?
- Content: Is the main call to action obvious? Are prices and next steps easy to find?
- Forms: Do you ask only for what you need? Do error messages sit next to the field and explain the fix?
- Feedback: Does every action (saving, submitting, loading) show a clear response?
- Consistency: Do the same actions look and behave the same way everywhere?
- Mobile and speed: Are tap targets large enough, and do key pages load quickly on a phone?
- Accessibility: Is contrast sufficient and the flow usable by keyboard? Our website accessibility basics cover the essentials.
- Trust: Are contact details and policies visible where people hesitate, such as checkout?
How to act on the findings
An audit only pays off when the fixes ship. Work through it in this order:
- Score each issue by impact and effort. High impact and low effort goes first, high impact and high effort gets planned, and low impact and high effort can wait.
- Fix blockers immediately. A broken mobile button or a form that fails silently costs you money today.
- Ship quick wins in batches so you can see their effect in the data.
- Validate bigger changes before building them. With enough traffic, run an A/B test. Without it, prototype the change and test it with five users.
- Put owners and dates on everything by moving the issue log into your team’s backlog.
- Re-measure against the baseline a few weeks after each batch, and audit again after major releases.
Common mistakes
- Starting without goals. Define the journeys and metrics that matter before reviewing anything, or the audit drifts into personal taste.
- Relying on one method. Expert opinion without data, or data without observation, gives half the picture.
- Trusting broken tracking. Verify events and conversions first.
- Testing with the wrong people. Colleagues and friends already know the product. Recruit people who match your real customers.
- Treating every finding as equal. A long list with no priorities usually gets ignored.
- Jumping straight to a full redesign. Many problems are fixable in place, and a redesign without evidence can repeat the same mistakes.
Conclusion
A UX audit replaces guesswork with evidence. It shows where people struggle, why, and which fixes matter most. Start with your most important journey, combine at least two methods, and measure before and after.
If your audit points to fixes that need new wireframes, prototypes or a design system, that is what our UI/UX design service covers. Tell us about your product and what you are seeing, and we can talk through the next steps together.
