People are leaving somewhere. An audit tells you where, and why.

A UX audit evaluates an existing product against usability heuristics and analytics data, then reports the friction points ranked by how much they cost the business. Haryes delivers findings with recommended fixes, not just a list of problems.

  • Heuristics and data
  • Ranked by cost
  • Fixes, not just findings

Everyone has an opinion about the site. Opinions are not evidence.

Someone thinks the menu is confusing, someone else wants the hero changed, and the developer says it is fine. Nobody has looked at where people actually stop, so the loudest view wins and the real problem survives the redesign.

An audit replaces that with evidence.

  • Drop-off points that nobody has looked at, because analytics is open twice a year.
  • A checkout or enquiry flow that has never been completed by anyone outside the business.
  • Mobile treated as the smaller version of desktop, on a site where most visits are mobile.
  • Accessibility problems that also happen to be usability problems for everyone.

How the audit runs

Two to three weeks, depending on the size of the product.

  1. Agree the journeys

    The two or three paths that actually matter to the business, rather than auditing every page equally.

    Focus on what earns.

  2. Review the data

    Analytics, funnel drop-off and session recordings where they exist, so findings start from behaviour.

    Evidence, not instinct.

  3. Heuristic review

    The product assessed against established usability principles, on real devices at real connection speeds.

    Problems named precisely.

  4. Accessibility pass

    Keyboard operation, contrast, focus states and labelling checked to WCAG 2.2 AA.

    Barriers found.

  5. Rank and recommend

    Every finding ranked by business impact against effort, with a specific fix for each.

    A plan in order.

Where friction usually hides

Four places that account for most of what we find.

  • The first screen

    If a visitor cannot tell what this is and whether it is for them, nothing further down matters.

    Clarity before beauty.

  • Forms

    Unnecessary fields, unclear errors, and validation that rejects a perfectly valid Kenyan phone number.

    The cheapest wins.

  • Mobile reality

    Tested on a mid-tier Android over mobile data, not on a designer's laptop on fibre.

    Test on what people hold.

  • The moment of commitment

    Checkout, booking or enquiry. Missing information about price, timing or what happens next loses people who were ready.

    Answer before they ask.

What you receive

Delivered as a document and a recorded walkthrough, with Figma files where we propose changes.

  • Ranked findings

    By impact, with reasoning shown.

    • Business impact estimated
    • Effort to fix stated
    • Evidence attached to each
  • Recommended fixes

    Specific, not general advice.

    • What to change, concretely
    • Wireframes where it helps
    • Priority order for your team
  • Accessibility findings

    Checked to WCAG 2.2 AA.

    • Keyboard and focus
    • Contrast and labelling
    • Issues ranked alongside the rest
  • A walkthrough

    Recorded for the whole team.

    • Findings explained in order
    • Questions answered live
    • The recording is yours

Questions clients ask before they commit

  • Is this the same as usability testing?

    No. An audit is expert review against principles and data, which is faster and cheaper. Usability testing watches real people attempt real tasks. They answer different questions and work well in that order.

  • Do you redesign the site afterwards?

    Only if you want us to. The audit is written so your own team or developer can act on it, and plenty of clients do exactly that.

  • Will you audit an app as well as a website?

    Yes. The method is the same for a web application, a portal or a store, and the journeys that matter are agreed with you at the start.

  • What if the finding is that we need a rebuild?

    Then we say so, with the reasoning. It is not the answer we hope for, and telling you otherwise would waste a year of incremental fixes.

What prompted this?

Traffic, no conversions

People arrive and leave without acting.

The audit finds where and gives you the order to fix it in.

Book a UX audit
Planning a rebuild

You are about to spend on a new site or product.

Audit first, so you do not rebuild the same problems.

See UI/UX design

Most sites do not need a redesign. They need four specific things fixed, and nobody has identified which four.

Haryes KebeyaFounder, Haryes Web Developers