Clipboard checklist next to a laptop
Home / CRO & Experience Audits / UX audits
CRO & Experience Audits · UX audits

UX audits that find the real problems - and rank them

A structured, evidence-based review of your product's key journeys that identifies where users struggle, explains why, and tells you which fixes will make the biggest difference first.

Journey reviewSeverity ratingsAccessibility checksPrioritised fix list

What a UX audit is

A UX audit is a structured review of a product or website that identifies usability problems, explains their causes and recommends fixes - ranked so your team knows where to start. It is a diagnostic, not a redesign. Its value is in telling you what to change and what to leave alone before you spend on either.

Good audits are grounded in evidence rather than taste. They review real journeys against established usability principles, check what analytics and support data say, test the biggest suspicions with users where possible, and include accessibility so every issue is prioritised together.

Is this you?

When a UX audit makes sense

01

Before a redesign

To find out what must change and what can stay.

02

Metrics have stalled

Activation, completion or conversion aren't improving despite new features.

03

Support volume is growing

The same "how do I" and "where is" questions keep arriving.

04

After rapid growth

Many teams have added features and the product no longer feels coherent.

05

Before a big sales push or pilot

You want the product ready for scrutiny.

06

A new team has inherited the product

You need an independent baseline.

What the audit reviews

AreaQuestions asked
Navigation and structureCan users find features and content? Do labels match their language?
Key task flowsCan users complete core tasks without confusion, dead ends or repeated steps?
Feedback and statusDoes the product show what's happening, what's next and who needs to act?
Forms and inputsAre fields clear, validated helpfully and forgiving of different formats?
Errors and recoveryDo errors explain what happened and how to fix it, without losing work?
Content and terminologyIs language clear, consistent and appropriate for the audience?
Visual hierarchyDoes the most important information stand out? Are actions obvious?
ConsistencyDo the same things look and behave the same way across the product?
AccessibilityContrast, keyboard access, labels, focus and structure against WCAG 2.1 AA
Performance perceptionDo loading and waiting states keep users informed?

The review draws on Jakob Nielsen's 10 usability heuristics - principles first published in 1994 and still unchanged in substance - applied to your specific users and context.

Evidence behind every finding

Each finding in the audit report includes:

  • Where - the page, screen or step, with a screenshot.
  • What - a plain description of the problem.
  • Why it matters - the principle it breaks and the user impact.
  • Evidence - analytics, support themes, test observations or benchmark comparisons.
  • Severity - how badly it affects users and the business.
  • Recommendation - a specific fix, with an example where useful.
  • Effort - a rough estimate agreed with your team where possible.

Where evidence is thin, the recommendation says so - and suggests a quick test rather than a confident change.

Severity and prioritisation

SeverityDefinitionExample
CriticalPrevents task completion or creates riskA required form can't be submitted by keyboard; a status is misleading
MajorCauses frequent errors, delays or abandonmentUsers repeatedly enter the same data; errors lose progress
ModerateSlows users or causes confusion they recover fromAmbiguous labels; inconsistent button placement
MinorCosmetic or low-frequencySpacing inconsistencies; typos

Combining severity with effort gives the fix-first list: high-severity, low-effort issues at the top. In regulated contexts such as healthcare, a third factor - compliance risk - is added. See UX audits for healthcare platforms.

Validating with users

An expert review finds a lot, but users confirm what matters. Where time allows, I run a small round of moderated sessions on the biggest suspected issues. Testing with about five users per round uncovers roughly 85% of usability problems, according to Jakob Nielsen's analysis - enough to confirm or rule out the top findings quickly.

The process

How I run a UX audit

  1. 01

    Scope and goals

    Agree the journeys, user types and questions the audit must answer.

  2. 02

    Evidence gathering

    Analytics, support tickets, recordings where permitted, stakeholder input.

  3. 03

    Expert review

    Heuristic and accessibility review of each journey, documented with screenshots.

  4. 04

    Validation

    Quick user sessions on the biggest issues where possible.

  5. 05

    Prioritisation

    Severity, effort and (where relevant) compliance risk for every finding.

  6. 06

    Readout

    A working session with your team and a report built for action.

What you get

01

Executive summary

The five to ten findings that matter most, on one page.

02

Detailed findings

Every issue with evidence, severity and recommendation.

03

Prioritised fix list

Quick wins separated from structural changes.

04

Accessibility findings

Integrated with the rest, mapped to WCAG criteria.

05

Recommendations with examples

Sketches or references for key fixes.

06

Readout session

A working session to agree next steps with your team.

Unified brand and product experience for a healthcare platform
From the work

Small frictions, fixed together, in a healthcare product

On a healthcare credentialing platform, the audit findings that mattered most were not dramatic. They were small, cumulative frictions across the credentialing journey.

  • Ambiguous status labels, repeated data entry and forms that didn't explain themselves.
  • Fixed together, they changed how trustworthy the whole product felt.
Read the healthcare case study →

Frequently asked questions

How is a UX audit different from usability testing?

Usability testing observes users doing tasks. A UX audit combines expert review, data and benchmarking, and often includes a small amount of testing to validate the biggest findings.

How many journeys should an audit cover?

Usually three to six critical journeys. Covering everything at once dilutes the findings; focus on what matters most to users and the business.

Do we need to give you access to our live product?

Access to a test or staging environment with realistic data is ideal. Screenshots and screen recordings can work where access is restricted.

What format is the report?

A concise document or slide deck with an executive summary, detailed findings and a prioritised list - plus a working readout session.

Can the audit include our marketing website?

Yes. Many audits cover the path from website to sign-up or enquiry, since problems often sit at the handoff between marketing and product.

Sources

Every statistic in this page links to its original publisher. Figures were checked against these sources on September 29, 2026.

  1. 10 Usability Heuristics for User Interface Design - Jakob Nielsen, Nielsen Norman Group
  2. Why You Only Need to Test with 5 Users - Jakob Nielsen, Nielsen Norman Group, 2000
Let's solve something

Want an honest view of your product's UX?

Book a 30-minute call. We'll agree which journeys matter and what the audit should answer.

Book a 30-min call ↗