What Is a UX Audit?

A UX audit is a systematic evaluation of a digital product — website, app, or platform — to identify usability problems, friction points, and opportunities for improvement. It's one of the most valuable services a UX designer can offer, and one of the clearest ways to demonstrate the ROI of good design to clients and stakeholders.

Unlike user testing, which involves real users completing tasks, a UX audit is typically conducted by a designer using established heuristics, design principles, and data analysis. Think of it as a design health check.

When Should You Run a UX Audit?

  • Before a major redesign — to understand existing problems before building something new
  • When conversion rates are declining unexpectedly
  • When user feedback surfaces recurring complaints
  • After inheriting a product from another team
  • As part of a regular maintenance schedule (annually is a solid baseline)

Step 1: Define Scope and Goals

A UX audit without a defined scope quickly becomes overwhelming. Start by asking:

  • What pages or flows are we auditing? (Entire site, or specific journeys like onboarding/checkout?)
  • What are the business goals? (More signups, reduced support tickets, higher retention?)
  • What user goals are we evaluating against?

Document this clearly. It becomes the benchmark against which every finding is measured.

Step 2: Gather Existing Data

Don't start with gut feel — start with data. Collect:

  • Analytics: Bounce rates, drop-off points in funnels, time on page, search queries
  • Support tickets and chat logs: Where are users getting confused?
  • Previous user research: Surveys, interviews, usability tests
  • Heatmaps and session recordings (from tools like Hotjar or Microsoft Clarity)

This data directs your attention to the highest-impact areas before you even open the product.

Step 3: Heuristic Evaluation

Walk through the product using Nielsen's 10 Usability Heuristics as your evaluation framework. These include:

  1. Visibility of system status
  2. Match between system and the real world
  3. User control and freedom
  4. Consistency and standards
  5. Error prevention
  6. Recognition rather than recall
  7. Flexibility and efficiency of use
  8. Aesthetic and minimalist design
  9. Help users recognize, diagnose, and recover from errors
  10. Help and documentation

For each screen or flow, note violations of these heuristics with screenshots and severity ratings (1–4 scale).

Step 4: Accessibility Check

Accessibility is not optional — it's a legal requirement in many regions and a core quality signal. Run the product through:

  • WAVE or Axe browser extensions for automated accessibility checking
  • Keyboard navigation testing (can all interactive elements be reached?)
  • Color contrast ratios (WCAG AA minimum: 4.5:1 for body text)
  • Screen reader testing with NVDA (Windows) or VoiceOver (Mac/iOS)

Step 5: Compile and Prioritize Findings

Categorize findings by severity and impact:

  • Critical: Blocks users from completing key tasks
  • Major: Causes significant friction or confusion
  • Minor: Reduces polish or creates small inconsistencies

Use a simple matrix — impact vs. effort — to prioritize which issues to address first. Quick wins (high impact, low effort) should be tackled immediately.

Step 6: Deliver Actionable Recommendations

A good UX audit report doesn't just list problems — it provides specific, actionable recommendations for each finding. Frame every issue with: what the problem is, why it matters, and what to do about it. Screenshots and annotated mockups make recommendations far easier for development teams to implement.

Delivered well, a UX audit becomes a strategic roadmap — not just a criticism document.