Service inquiryUX audit services

UX audit: find friction before a redesign.

We review the journeys that matter: finding a service, completing a form, signing up or using a product. A UX audit gives your team a prioritised set of usability findings, evidence and changes to consider before committing to design or development.

  • Agreed journeys and devices
  • Evidence with each finding
  • Priorities your team can use
01 / The operating gap

People reach your website but struggle to finish the job.

We start with the point where value, trust or control is being lost. That keeps the project tied to a business decision instead of a generic list of deliverables.

The next step is unclearVisitors cannot compare options, find an answer or understand what will happen after clicking.
Forms create unnecessary effortConfusing fields, validation and mobile interactions can interrupt inquiries or onboarding.
A redesign starts with opinionsTeams debate screens without a shared view of which problems matter or how improvements will be checked.
02 / What you get

What you receive from a website UX audit

We agree the pages, flows, devices and evidence sources before starting. The deliverable connects each observation to a user task and an improvement decision.

01

Journey and interface review

A review of navigation, page hierarchy, service or product information, forms and the agreed conversion journeys on desktop and mobile.

02

Evidence for each finding

Annotated screens, reproduction steps and available analytics or feedback. Expert observations are distinguished from measured behaviour and hypotheses.

03

Prioritised usability report

Findings grouped by severity, confidence and the effort needed to investigate or change them. Dependencies and unanswered questions stay visible.

04

Improvement brief

Recommended changes and acceptance checks that your design or development team can use. Prototype work and user testing are scoped when they are needed.

05

Review and next steps

A walkthrough of the findings, a first improvement backlog and options for implementation with your team or ours.

03 / Delivery path

Review a defined journey, then verify the improvement

  1. 01

    Set the boundary

    Agree user groups, target actions, relevant pages, devices and available access. Decide what success would look like.

  2. 02

    Examine the evidence

    Walk through the journeys and review relevant analytics, support feedback or recordings where available and permitted.

  3. 03

    Rank the findings

    Separate reproducible issues from assumptions and identify the smallest useful group of improvements.

  4. 04

    Plan the follow-through

    Review findings together. Agree whether the next step is a fix, prototype, research task or a broader redesign.

04 / Fit and boundary

Useful before choosing what to redesign or fix

A strong starting scope is specific enough to verify and important enough to change an operating or commercial result.

Good starting conditions

  • A website receives visits but the inquiry journey is confusing.
  • A product team needs an outside review of onboarding or a core workflow.
  • A planned redesign needs evidence to set priorities.
Scope considerations

  • An outage or broken integration should receive technical investigation first.
  • A new product may need discovery and prototype testing before an audit of screens.
  • An audit identifies improvements; implementation and measured outcomes require follow-through.
05 / Questions

What buyers usually need to clarify before scoping the work.

The answers below define the normal starting boundary. The final scope follows your systems, evidence, risk and operating constraints.

Can you audit a website with little traffic?

Yes. Expert review can identify usability issues without a large sample. We label those observations clearly and avoid claiming statistically proven conversion effects from limited data.

Is user testing included?

It depends on the scope. Expert review, analytics analysis and moderated user testing answer different questions. Participant recruitment, test sessions and prototypes are agreed explicitly.

What is the difference between a UX audit and a redesign?

An audit identifies and prioritises problems. A redesign creates and implements changed interfaces. You can commission an audit as a standalone engagement and choose the next step afterwards.

Can you implement the recommendations?

Yes. We can scope design, development and a follow-up check, or provide a backlog for your existing team. Implementation is estimated separately unless it is included in the agreed engagement.

How much does a UX audit cost?

The estimate follows the number and complexity of journeys, devices, research methods and access needed. A free consultation helps us establish an appropriate scope before quoting.

Next useful step

We will help choose the journeys worth reviewing.

Book a free consultation about your website or product. We will clarify the user task, available evidence and a useful audit scope.

Project request

We will propose the first practical step.


    Protected by reCAPTCHA. The Google Privacy Policy and Terms of Service apply.