What is a UX audit?

A UX audit is an expert review of a website or product flow, examined against usability and conversion principles, that produces a prioritised list of what is costing you users and what to change. It is a diagnosis, not a redesign — the output is findings and recommendations, not new screens.

The term covers a wide range of work in practice. At one end it means a two-hour skim and a list of opinions; at the other, a multi-week research programme. What follows is the useful middle: what a good audit actually contains, when it is the right instrument, and what it cannot tell you.

What does a UX audit include?

A complete UX audit contains four things: a structured examination of the experience against defined criteria, a prioritised list of problems ordered by what they cost, specific recommended changes for each, and enough reasoning that someone who disagrees can say where. Anything missing the last part is a list of opinions.

The reasoning matters more than it sounds. A finding that says “the signup form is too long” is not actionable — long compared to what, and which field would you remove? A finding that says “the form asks for company size and phone number before the visitor has seen the product work, and both can be collected after activation instead” tells the reader what to do and lets them push back with information you did not have.

Most audits are organised around a small number of lenses rather than a flat list of heuristics. A common structure — the one used in the Uxerfy Score — runs four passes over the same page:

• First impression. What a first-time visitor understands in five seconds, and whether there is one obvious next step or several competing.
• The path to value. Every step between arriving and the core action, and which of them could be deferred.
• Clarity of copy. Whether the page is written for the reader or for the system behind it.
• Trust and friction. Whether the price is legible, whether reassurance appears where the doubt happens, and whether anything asks for more commitment than has been earned.

The order is not arbitrary. A page that fails the first lens rarely gets a fair reading of the fourth, because nobody stays long enough to reach it.

What is the difference between a UX audit and usability testing?

A UX audit is an expert inspecting the interface; usability testing is real people attempting real tasks while you watch. The audit is faster and cheaper and finds problems a trained reviewer recognises on sight. Testing is slower and more expensive and finds the problems nobody predicted, including the ones the expert would have defended.

They answer different questions and the honest position is that you want both, in that order. The audit removes the obvious failures so that testing sessions are not spent watching five people struggle with the same broken button. Testing then finds what remains, which is usually stranger and more specific than anything an inspection would have flagged.

Where budget forces a choice, the deciding factor is whether you already know that something is wrong. If conversion has dropped and nobody knows why, an audit will usually surface a candidate within hours. If the experience is broadly working and you are optimising, testing earns its cost faster.

Heuristic evaluation sits inside this. It is the formal name for inspecting an interface against a published set of principles — most often Nielsen’s ten usability heuristics. A UX audit typically includes a heuristic evaluation and adds the things heuristics do not cover: copy, pricing legibility, trust signals, and the commercial question of what each problem is costing.

When do you need a UX audit?

A UX audit is worth running when you have traffic that is not converting, when you are about to spend on acquisition, before a redesign rather than after one, or when the team has stopped being able to see the product. Those are four different problems and the audit is a useful first instrument for all of them.

The strongest case is before increasing spend. Paid acquisition into a leaking funnel multiplies the leak. An audit that costs a fraction of one month’s ad budget and finds a broken step in the signup will return more than the campaign it precedes.

The second strongest is before a redesign. Redesigns that begin without a diagnosis tend to preserve the original problems in new visual clothing, because nobody wrote down what was wrong. A page can be rebuilt beautifully and still ask for a phone number too early.

The case people underrate is when the team has been looking at it too long. Everyone who works on a product loses the ability to see it. You know where the button is, so you cannot experience not knowing. This is not a failure of skill — it is unavoidable, and it is the specific thing an outside reviewer is for.

When a UX audit is the wrong instrument

• You have no traffic. An audit will improve the conversion rate of a number close to zero. Get people to the page first.
• You already know what is wrong. If three people have told you the checkout breaks on mobile, fix that. Do not buy a document that says so.
• The problem is the product, not the interface. No amount of interface work fixes something people do not want. An audit will tell you the page is clear; it will not tell you the market is not there.
• You cannot act on the findings. A report nobody has time to implement is an expensive way to feel productive.

How is a UX audit carried out?

An auditor walks the experience the way a first-time visitor would, records friction as it occurs rather than reconstructing it afterwards, then examines the same screens a second time against a structured checklist. The first pass catches what a real visitor would feel; the second catches what a visitor would never articulate.

The order matters, and it is the part most often skipped. Once you have examined a page closely you can no longer experience it naively, so the naive pass has to come first and has to be recorded as it happens. Notes written afterwards are notes about what you now know, not what you first felt.

The full process is here, step by step, including the part most people skip.

A serious audit will also state its own limits. Nothing that runs from the outside can tell you whether real users succeed, whether the page performs under load in every market, or what is happening behind a login the reviewer was not given access to. An audit that claims otherwise is overselling.

What does a UX audit report look like?

A useful report leads with a small number of prioritised findings rather than an exhaustive list. A typical shape is a score for orientation, the three problems costing the most, five changes that can ship immediately, and a note on the copy — enough to act on this week, with the reasoning attached to each item.

The temptation is to include everything found, and it is worth resisting. A document with thirty findings gets read once and actioned never; three things a team can argue about over one meeting get done. Everything else belongs in the report, but further down.

Two practical tests of a report’s quality:

1. Can someone who was not in the room act on it? If a finding needs the author present to be understood, it will not survive being forwarded.
2. Is the priority order about cost or about effort? Those are different sorts. Ordering by effort puts the cheap and harmless changes at the top, which is how a report ends up feeling productive and changing nothing.

You can see the full shape of one in a sample report, and the same method applied in public in the teardowns. What goes in a UX audit report covers the deliverable in detail, including how to write a finding somebody can act on.

How much does a UX audit cost?

A single-page UX audit from an independent practitioner typically runs between $150 and $800. Agency engagements covering a full product start around $2,000 and rise quickly with scope. The range is wide because “UX audit” describes both a half-day inspection and a multi-week research programme.

What moves the price is scope and format rather than skill: how many surfaces are covered, whether user research is included, whether there is a presentation, and whether implementation support follows. A focused audit of one high-stakes page is the highest-return version for most teams, because the findings on a pricing page or a signup flow apply directly to revenue.

UX audit pricing in detail breaks down what actually moves the number and how to judge whether a quote is worth paying. What an audit costs here is one price for one page or flow, with the scope stated on the page.

What a UX audit will not do

It will not tell you whether people want the product. It will not replace talking to your customers. It will not produce a redesign — the output is a diagnosis, and someone still has to do the work. And it will not, honestly, predict a percentage lift: anyone promising one before seeing your traffic is guessing, and a specific number is a good signal to be sceptical.

What it does reliably is convert a vague sense that something is wrong into a short, ordered list of specific things that are, each with a reason attached. For most teams that is the bottleneck — not knowing what to fix rather than not being able to fix it.