UX audit: method, deliverables and what to fix first

A UX audit is a structured diagnosis of the experience people have on a website or web application. It identifies the friction that stops your users from reaching their goal, and stops you from reaching yours. Here is how it unfolds, what you should get out of it and how to decide what to fix first.

UX audit, usability audit, user testing: what are the differences?

A UX audit is a comprehensive analysis of the user experience: navigation, user journeys, content, forms, interface and accessibility, all tied to business goals. It combines an expert's assessment, usage data and, when needed, a few field observations.

A usability audit is more targeted. It evaluates the usability of an interface against recognized principles, in particular Nielsen's heuristics. User testing, for its part, observes real people performing specific tasks.

User testing deserves its own method, which we will cover in an upcoming article. In an audit, it remains an occasional complement.

A clarification to avoid confusion: a UX audit has nothing to do with a code audit. The latter analyzes the technical quality, security and maintainability of software, as described on our code audit page and in the glossary entry on technical audits.

When should you run a UX audit?

A UX audit is justified when your business metrics drop without a clear cause. Four signals come up systematically with our clients.

• Stagnating conversion: the traffic is there, but few visitors request a quote, create an account or buy.
• Drop-offs concentrated on one step: cart, form, payment, initial setup.
• A support team flooded with repetitive questions: a feature nobody can find or an incomprehensible error message gets paid for in tickets.
• High churn or low activation: users don't perceive the product's value quickly enough.

The stakes are real. According to the Baymard Institute, about 70% of e-commerce carts are abandoned, and 18% of abandonments are due to a checkout process deemed too long or complicated. An interface flaw turns directly into lost revenue.

An audit is also an excellent first step before a redesign. It avoids reproducing the old interface's mistakes in the new one. If you want an overview of the most common flaws, our article on common UI/UX design mistakes lists them.

How does a UX audit work: the 5-step method

An effective audit method starts from goals, not screens. Here is the sequence we apply.

1. Define the scope and goals

We define the product, the target users, the problematic KPIs and the constraints. The scope must be explicit: full website, conversion funnel, customer portal or onboarding.

2. Choose the key journeys

Analyzing every page at the same level of detail is a mistake. We select three to five key journeys (buying, requesting a quote, creating an account, using the core feature) and describe them from the user's point of view: goal, steps, obstacles.

3. Read the analytics data

Drop-off rates, form errors, internal searches, behavior by device: analytics show where to look. They don't say why. That is the role of the next steps.

4. Conduct the heuristic evaluation

A heuristic evaluation consists of inspecting each screen against Jakob Nielsen's ten usability heuristics, published by the Nielsen Norman Group. These are general rules: visibility of system status, error prevention, consistency, recognition rather than recall, help with errors.

For each problem, we record the screen concerned, the heuristic violated, the affected task, the severity and a recommendation. NN/g points out that a single evaluator detects only a limited share of problems and recommends combining several perspectives. We see it in the field: an audit reviewed by a second designer or a developer brings out problems the first one had come to see as normal.

A UX/UI audit also covers visual hierarchy, contrast, label clarity, empty, loading and error states, as well as consistency between desktop and mobile. Accessibility is part of the scope: keyboard navigation, field labels, heading structure. For the regulatory framework, see our guide on digital accessibility, RGAA and EAA.

5. Confirm with quick tests

When the budget allows, a few tests on critical tasks validate the hypotheses. According to NN/g, five users are enough to reveal most of the usability problems in a journey. The goal is not statistical rigor, but to confront the expert's assessment with real behavior.

What deliverables should you expect from a good UX audit?

A good audit delivers decisions, not just findings. If you receive an 80-page PDF with no order of priority, the audit is incomplete. Here is the minimum you should demand.

• An audit report: scope, method, journeys studied, findings illustrated with annotated screenshots.
• Recommendation sheets: each problem is located, backed by evidence (screenshot, data or observation), rated for impact and effort, with a tracking KPI.
• A list of quick wins: fast fixes, such as an ambiguous label, an error message or an unnecessary field.
• A prioritized UX backlog: the recommendations turned into tickets ready to schedule in your sprints.
• Corrective mockups for the workstreams that require rethinking several screens together.
• A debrief: a 60 to 90-minute session with your teams, focused on the three to five major problems.

We stand by a clear position: an audit is only valuable if it leads to an actionable backlog. A report that sits in a shared folder changes nothing about your conversion.

What to fix first: the impact / effort matrix

The impact / effort matrix crosses the expected benefit of a fix with the cost of making it. It is the simplest and most effective prioritization tool.

Impact is measured with explicit criteria: number of users affected, frequency of the problem, importance of the journey, risk to conversion, cost to support, accessibility risk. Effort includes UX complexity, technical dependencies and regression risk.

For severity, NN/g offers a severity scale from 0 to 4, from cosmetic detail to blocking problem. Cross it with frequency: a moderate flaw encountered by every visitor weighs more than a severe flaw on a page nobody opens.

In practice, the order of treatment we recommend is the following:

1. Blockers on essential journeys (unable to pay, sign up or get in touch).
2. Problems that cause measurable errors or drop-offs.
3. Major accessibility flaws.
4. Inconsistencies repeated across several screens.
5. Quick wins with measurable impact.
6. Purely cosmetic improvements, last.

How much does a UX audit cost and what does it return?

The price of a UX audit depends on its scope, not on a standard rate. It varies with the number of journeys and screens, the number of user profiles, whether tests are included, the production of mockups and the support provided after the debrief. An audit focused on a conversion funnel takes a few days. One for a multi-role business application takes weeks.

Compare offers on deliverables and depth, not on the number of days. A low-cost proposal limited to a list of remarks ends up costing more than a structured audit with a prioritized backlog and a debrief.

The return is measured against metrics defined before the fixes:

• conversion rate and journey completion rate;
• form error rate;
• number of support tickets;
• activation and retention rates.

Let's be honest: an audit doesn't generate gains automatically. Its value comes from the ability to target the most costly problems and to replace intuition with a roadmap. Our article on UX/UI as a key investment details this return-on-investment logic.

Frequently asked questions

What is a UX audit? A UX audit is a structured analysis of the user experience of a website or application. It combines heuristic evaluation, analytics data and a study of key journeys to identify friction, then ranks it by priority with concrete recommendations.

What is the difference between a UX audit and a usability audit? A usability audit focuses on the usability of the interface, often based on Nielsen's heuristics. A UX audit is broader: it incorporates business goals, usage data, complete journeys and the prioritization of fixes.

How do you prioritize fixes after a UX audit? Cross impact (users affected, frequency, importance of the journey) with implementation effort in an impact / effort matrix. Address blockers on essential journeys first, then problems that cause drop-offs or errors, then quick wins.

Why is a UX audit important before a redesign? It identifies what works and what actually blocks users. Without it, a redesign risks reproducing the same flaws in a newer interface, at a much higher cost.

Conclusion

A useful UX audit fits in one sentence: a diagnosis grounded in journeys, heuristics and data, which results in a prioritized backlog. The method matters less than the final deliverable, which must enable your team to decide and act as early as the following week.

Start small: one critical journey, five tests, one impact / effort matrix. You will quickly see where the most costly friction is hiding.

Launch your UX audit with Fragments Studio

If your conversion, activation or support metrics signal friction, a structured audit will save you weeks of trial and error.

• Discover our UX/UI design services to turn audit findings into clearer, higher-performing journeys.
• If your project involves a technical overhaul or an internal tool, our custom development team can support you.
• Get a first estimate with our project estimator.
• Or let's talk directly.