Guide · Design & UX

UI/UX design audit: what to check before redesigning a website

Most redesigns begin with a feeling that something is wrong and end with a new surface over the same structure. An audit turns the feeling into a list — what is unclear, what is slow, what breaks, and which of those is worth fixing first.

What is a UI/UX design audit?

A UI/UX audit is a structured review of an existing website or product against how people actually use it. It examines the interface — layout, hierarchy, typography, components, states — and the experience around it: whether the structure makes sense, whether journeys complete, and where people are likely to stall.

The output is not an opinion about taste. It is a documented set of observations, each tied to a specific screen or flow, with a judgement about severity and effort. That document is what a redesign should be scoped from.

Why audit before redesigning?

Redesigning without an audit means rebuilding on assumptions. The visual language changes, the underlying problems move house. If navigation labels were confusing, they are still confusing in a new typeface. If a form asked for too much, it still does.

An audit also protects what already works. Every site has pages, patterns, and copy that perform their job well; a full rebuild frequently discards them by accident. A review makes those parts explicit before anything is touched.

Finally, it scopes the work honestly. Some findings are one-line fixes. Some require a new information architecture. Knowing the split before committing is the difference between a targeted improvement and an open-ended project.

What to check during a UI/UX audit

Usability

Can a first-time visitor understand what this is, who it is for, and what to do next — without scrolling to find out? Check that interactive elements look interactive, that labels say what will happen, that errors explain how to recover, and that nothing important depends on the visitor guessing.

Navigation and information architecture

List every page and ask where it lives and who it serves. Look for categories that overlap, sections that exist for internal reasons, orphaned pages with no inbound link, and menu labels borrowed from internal vocabulary. A structure is working when someone can predict where a thing will be before clicking.

User flows

Walk the two or three journeys that matter most — enquiry, purchase, sign-up, booking — from entry to completion, on a real device, as a stranger would. Count the steps, note every point where the next action is unclear, and record anything that forces a return to a previous screen.

Visual hierarchy

On each key template, identify the single most important element and check that size, weight, contrast, and position agree with that decision. Competing emphasis is the most common hierarchy failure: when three things shout, the page reads as noise and the visitor picks none of them.

Typography and readability

Check body size on a phone rather than a large monitor, measure line length, review line height, and confirm contrast between text and background. Look for headings that skip levels, long paragraphs with no break, and decorative weights used where plain text would read faster.

Mobile and responsive experience

Review the small screen as a design in its own right. Check tap target size and spacing, sticky elements that cover content, tables and charts that overflow, menus that trap focus, and hover-only interactions that have no touch equivalent.

Accessibility

Navigate the site with a keyboard alone and confirm a visible focus indicator throughout. Check colour contrast, alternative text on meaningful images, form labels tied to their inputs, correct heading order, and whether any information is carried by colour alone. Accessibility findings usually improve clarity for everyone, not only for assistive-technology users.

Forms and conversion paths

For each form, question every field: is it required to complete this step, or is it convenient for someone internally? Check label clarity, input types on mobile keyboards, inline validation, error messages that name the fix, disabled-state behaviour, and what the visitor sees after submitting. The path from interest to contact deserves the same scrutiny as the homepage — the contact page is often where a well-designed site quietly loses people.

Performance and interaction

Performance is a UX property. Check how long the first meaningful content takes to appear, whether layout shifts as images and fonts load, whether animation delays the moment a page becomes usable, and whether actions confirm themselves promptly. Motion should support comprehension, not stand in front of it.

Consistency and content clarity

Collect every button, card, and form field across the site and look for unintentional variants. Then read the copy aloud: headings that describe rather than tease, sentences that a newcomer can follow, and no term used in two different senses on two different pages.

Common UX problems an audit surfaces

Navigation labels written in internal language rather than the words visitors use.
Several competing calls to action on one screen, so none of them reads as primary.
Body text set too small, too light, or too wide to read comfortably.
Mobile layouts that are a compressed desktop rather than a considered arrangement.
Forms asking for information that is not needed to complete the current step.
Interactive elements with no visible focus, hover, loading, or error state.
Content that describes the offering from the inside out instead of the outside in.
Inconsistent components — three button styles, four card styles, no shared rule.

How to prioritise UX problems

An audit that lists everything equally is hard to act on. Score each finding two ways: how much it affects someone trying to complete a primary task, and how much work the fix requires. That gives four groups and a sensible order.

High impact, low effort — do these first; they usually change the experience within days.
High impact, high effort — this is the real scope of a redesign, and worth planning properly.
Low impact, low effort — batch them into routine maintenance.
Low impact, high effort — record them and move on.

Weight anything sitting on a primary journey above anything on a page few people reach, and treat accessibility barriers as higher priority than their traffic suggests — they exclude people outright rather than slowing them down.

When is a website ready for a redesign?

A redesign is justified when the findings are structural rather than cosmetic: the information architecture no longer matches what the business does, the offering has changed and the site still describes the old one, the interface has accumulated so many variants that consistency cannot be restored incrementally, or the underlying build makes ordinary changes expensive.

If the findings are mostly clarity, hierarchy, and copy on existing templates, a focused round of fixes will usually get you further, faster. You can see how finished projects are structured in the selected work, and how the design engagement itself runs on the UI/UX design services page.

Frequently Asked Questions

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

A UI audit looks at the surface: typography, spacing, colour, component consistency, and states. A UX audit looks at the experience around it: whether people can find things, understand them, and complete what they came to do. Most useful audits cover both, because a clear interface built on a confused structure still fails.

How long does a UI/UX audit take?

It depends on the number of templates and the number of distinct user journeys, not the number of pages. A small marketing site with a handful of templates is a short review. A product with account areas, dashboards, and transactional flows takes longer because each flow has to be walked end to end.

Do I need analytics data to run an audit?

No, but it helps. A heuristic review can identify problems on its own. Analytics tells you which of those problems sit on the paths people actually use, which changes the order you fix them in.

Can an audit replace a redesign?

Sometimes. An audit often surfaces a set of targeted fixes — navigation labels, form fields, hierarchy on key templates — that resolve the original complaint without rebuilding anything. A redesign becomes the right answer when the underlying structure, not the surface, is the problem.

Who should be involved in the audit?

Whoever owns the outcome, plus whoever hears from customers. Support and sales conversations usually describe the same friction the audit finds, in different words, and they are useful for deciding what matters most.

About the author

Written by Anas Essam, a technology consultant and creative director working on AI systems, web design, branding, and digital growth. Based in Egypt, working with teams worldwide.

Audit first, redesign second

Bring the page you are least happy with and we can walk through it together. More writing lives in Insights, including a guide to AI automation examples for the operational side of the same problem.

Start a conversation