The UX Audit Framework We Use Before Redesigning a B2B Website

Most UX advice for business websites is vague: "make it intuitive," "reduce friction," "think like your user." None of that tells you what to actually check before you approve a redesign budget.

Here's the audit we run on a client's existing site before we touch layout, copy, or code. It's a checklist, not a sales pitch — you can run most of it yourself, with a stopwatch and five people who've never seen the site.

Why audit before you redesign

A redesign without an audit usually just moves the same problems to a nicer template. Research on web credibility has found that users form a judgment about a company's trustworthiness largely from how a site looks and behaves — not from what it says. Stanford's Web Credibility research from the early 2000s put that effect — design gets judged before content does — on the map, and it hasn't gone away; it's just moved from desktop chrome to mobile load times and layout shift.

If a redesign doesn't touch the actual sources of that judgment — speed, clarity, and whether the site does what a visitor expects — it's decoration.

The five things we check

1. Time to first meaningful action

Open the site cold, on a phone, on mobile data. Time how long it takes to reach the thing a visitor actually came for: a price, a contact form, a portfolio piece, a booking slot. If that number is more than a few seconds — because of a hero video, a cookie banner fight, or three menu levels — that's the first fix, before any visual work.

2. Navigation depth versus real tasks

List the three or four things visitors actually do on the site (get a quote, see past work, check pricing, contact support). For each, count the clicks from homepage to done. Then compare that to how the menu is actually structured. Menus built around how the company is organized internally ("About," "Solutions," "Resources") routinely bury the tasks visitors came for two or three levels down.

3. Mobile parity, not mobile responsiveness

Responsive is a given in 2026 — the real check is: does the mobile version have the same functional coverage as desktop, or does something drop? Tables that collapse into unreadable stacks, filters that only exist on desktop, forms that lose fields on smaller viewports. We test the exact same 3-4 tasks from point 2, on mobile, and note where they get harder or impossible.

4. Form friction

Every field in a lead form has a cost. We count fields, flag anything that isn't strictly needed for a useful first conversation (job title, company size, budget range — often better asked on a call), and check whether the form gives any feedback before submission (validation, expected next step, response time). A form with 12 fields and no confirmation message is a leak, not a lead gate.

5. Trust signals above the fold