Brandon WatkinsFounder, Flowlabz
On this page9 chapters
You usually know something's wrong before you know what it is. The numbers are softer than they should be, the same questions keep landing in support, or a feature you were proud of barely gets used. A UX audit turns that feeling into a specific, prioritised list of what's getting in your users' way.
What a UX audit is
A UX audit is an expert review of how your website or app works for the people using it. An experienced designer walks through the product's most important journeys, checks them against established usability principles, and looks at your real data to see where people struggle and drop off.
The result isn't a critique of how it looks. It's a clear account of where the product is leaking conversions, causing friction or losing trust, ranked by what matters most to fix.
What it looks at
- Your key journeys. Sign-up, onboarding, the core task, checkout, getting help. The handful of paths that matter most to your users and your business.
- Usability principles. Is it clear what to do next? Do errors help people recover? Is the language the user's, or yours?
- Your analytics. Where people exit, which steps lose them, and how mobile compares with desktop.
- Consistency. Whether buttons, forms and patterns behave the same way across the product.
- Mobile and accessibility. Whether the product works on a phone, with a keyboard, and for people with different needs.
- The patterns people expect. How your product compares with the tools your users already know.
What you get at the end
A good audit delivers findings you can act on straight away:
- the problems, each tied to a specific screen or step, with evidence;
- a severity for each, so you know what's hurting most;
- a recommendation for each, from quick fixes to structural changes;
- a short list of what to fix first.
What you shouldn't get is a sixty-page document nobody reads. If the findings don't make it obvious what to do on Monday, the audit hasn't done its job.
Signs your product needs one
- Sign-ups, activations or conversions have stalled, and nobody can say why.
- Support keeps answering the same questions.
- Users drop off during onboarding, before they've seen the value.
- You're about to redesign, and want to fix the right things rather than repaint the wrong ones.
- The product has grown quickly, feature by feature, and no longer feels like one product. We've written about why web apps end up feeling hard to use.
- Large parts of it were built with AI tools, and it shows. Here's how to make an AI-built app look professional.
A UX audit vs user testing
They answer different questions, and they work best together. An audit is an expert review, backed by your data: fast, and good at finding known problems across the whole product. User testing means watching real people use the product, which is slower but uncovers the surprises no expert would predict. An audit is often the best place to start, because it tells you what to test.
How long it takes
A focused audit doesn't need weeks. Scoped to the journeys that matter most, it can go from first click to a prioritised report in days. We've written up how to run a UX audit in 48 hours, if you'd like to see the process in detail.
What to have ready
- Access to the product, including an account for each type of user.
- Access to your analytics, or an export of the key numbers.
- Your goals: what the product should be achieving that it isn't.
- What you already know: support themes, customer feedback, the complaints you hear most.
What happens after the audit
The audit tells you what's wrong. Then it needs fixing. UX audits are a common starting point for our UX and UI design work: we diagnose where the product is leaking conversions, friction or trust, then design the fix, from a few screens to a full redesign. Design engagements are priced per project once we've seen the product.
If you suspect your product has a UX problem, tell us about it.
Questions we get asked
What's the difference between a UX audit and usability testing?
A UX audit is an expert review of the product, backed by your data. Usability testing means watching real users try it. An audit is faster and finds known problems across the product; testing uncovers the surprises. They work best together.
How long does a UX audit take?
A focused audit, scoped to the journeys that matter most, can be done in days rather than weeks.
What do I need to provide?
Access to the product, access to your analytics, your goals, and what you already know from support and customer feedback.
Will the audit tell me what to fix first?
It should. A good audit ranks every finding by severity and ends with a short list of what to fix first.
What happens after the audit?
You fix what it found. UX audits are a common starting point for our redesign work: we diagnose where the product is leaking conversions, friction or trust, then design the fix.
