How to Run a Website UX Audit That Finds Lost Leads

Most B2B sites lose buyers long before the sales team ever hears about them. A prospect lands on a service page, hunts for pricing, can't find it, opens a competitor tab, and is gone. No form, no signal, no trace in your CRM. The traffic report looks fine. The pipeline doesn't.

A UX audit is how you find those silent exits. Done well, it tells you exactly where attention drops, which screens confuse people, and which two or three fixes will move conversion the most. This guide walks through a practical audit you can run yourself: what to look at, in what order, and how to decide what to fix first so you spend effort where the money is.

This is not a redesign brief. The goal is a ranked list of friction points backed by evidence, not opinions about whether the hero image should be bigger.

Start with the business question, not the homepage

Before you open a single analytics tool, write down the one outcome the site exists to produce. For most B2B companies that's a qualified inquiry: a demo request, a quote, a contact form from someone who fits your target profile. Everything in the audit gets judged against that outcome.

This keeps you honest. A bounce rate on a blog post barely matters. A 12% drop-off on the demo form matters a great deal. Naming the primary conversion up front stops you from "fixing" pages that were never meant to convert and ignoring the ones that carry the pipeline.

Then list your top conversion paths. Usually there are three or four:

Paid traffic to a landing page to a form.
Organic search to a service page to a form.
Homepage to pricing or case studies to a form.
Returning visitor straight to contact.

You'll audit these paths, not the site as a random collection of pages. A path-based view shows you where people fall out of a sequence, which is where leads actually leak.

The two layers of a UX audit

A complete audit has a quantitative layer and a qualitative layer. Skip either one and you get a half-picture.

The quantitative layer tells you where people drop off and how many. The qualitative layer tells you why. Numbers without observed behavior lead to guessing; observed behavior without numbers leads to over-reacting to a single annoyed visitor. You want both.

Two layers of a website UX audit (numbers are illustrative)
Layer	Question it answers	Tools and methods
Quantitative	Where and how much do people drop off?	GA4 funnels, page reports, form analytics, site speed tools
Qualitative	Why do they drop off?	Session recordings, heatmaps, user testing, support and sales notes

Pulling the quantitative picture

Open GA4 (or whatever analytics you trust) and build a funnel for each conversion path. You're looking for the step with the steepest fall. If 1,000 people reach a landing page, 400 scroll to the form, 120 start filling it, and 70 submit, the biggest leak isn't the form, it's the 600 who never scrolled to it.

Things worth measuring page by page:

Entry and exit rates: which pages quietly end sessions.
Scroll depth: how far down the page attention actually reaches.
Time on key pages versus task complexity.
Conversion rate by device, because mobile and desktop often behave very differently.
Form completion versus form abandonment, field by field if you can.

Segment by device early. A site that converts at 4% on desktop and 0.6% on mobile doesn't have a generic UX problem, it has a mobile problem, and that changes your whole priority list. If mobile is where the gap is, focus there first.

Watching real sessions

Numbers point you to the rooms; recordings show you what's broken inside them. Tools like Hotjar, Microsoft Clarity, or FullStory let you watch anonymized sessions and view heatmaps of clicks, movement, and scroll.

Watch ten to twenty sessions on each problem page and look for the tells:

Rage clicks: repeated clicking on something that isn't a button.
Dead clicks: clicks on elements that don't respond.
Hesitation before a form, then a leave.
Erratic scrolling, the cursor hunting for something that isn't there.
People reaching the price question and immediately bouncing.

You will see patterns within a dozen sessions. When five people in a row click a non-clickable feature graphic expecting it to expand, that's not a coincidence, that's a fix.

The audit checklist, screen by screen

With the data layer in place, walk your key pages against a consistent set of questions. Here is the checklist I use, grouped by what it protects.

Clarity (the five-second test). Can a first-time visitor tell what you do, who it's for, and what to do next, within five seconds? Show the page to someone outside your company for five seconds, hide it, and ask them to describe it. If they can't, your headline and hero are doing the work poorly. This single test catches more lost leads than any heatmap.

Navigation and findability. Can people reach pricing, case studies, and contact in one or two clicks? Is the menu labeled in customer language or internal jargon? B2B buyers research in a specific order: what you do, proof you've done it, what it costs, how to start. If any of those is buried, the path breaks.

Trust. B2B purchases carry career risk for the buyer, so doubt is expensive. Check for logos, named case studies, real testimonials, certifications, and clear company details. Thin or generic trust signals stall serious buyers. A focused pass on trust signals for B2B sites is worth doing as part of the audit.

Forms and conversion points. Count the fields. Every extra field costs completions. Is the call to action specific ("Get a quote") or vague ("Submit")? Does the form explain what happens after submission? Form friction is one of the highest-leverage fixes because the visitor has already raised their hand.

Speed and technical feel. Slow pages bleed conversions, especially on mobile and especially on paid traffic you've paid to acquire. Run the key pages through PageSpeed Insights and check Core Web Vitals. The connection between page speed and conversion is direct and measurable: tenths of a second move real percentages.

Mobile experience. Don't assume the desktop layout "just works" smaller. Tap targets, readable text without zoom, forms that don't fight the keyboard, sticky bars that don't eat half the screen. Audit mobile as its own thing.

Consistency. Buttons that look the same do the same thing. Headings follow a real hierarchy. Visual style holds across pages. Inconsistency makes people pause, and a pause near a decision point often becomes an exit.

Turn findings into a prioritized list

By now you have a long list of issues. The mistake here is trying to fix everything, which means nothing ships. Prioritize.

Score each finding on two axes: impact (how many people it affects and how close it sits to the conversion) and effort (how hard it is to change). A confusing pricing CTA on your highest-traffic landing page is high impact, low effort, so it goes first. A full navigation rebuild is high impact, high effort, so it gets planned, not rushed.

A simple way to sort:

Quick wins: high impact, low effort. Copy changes, removing a form field, fixing a broken CTA, reordering a section. Ship this week.
Big bets: high impact, high effort. New page templates, navigation overhaul, speed re-architecture. Plan and test.
Nice to have: low impact, low effort. Do them when convenient.
Skip or park: low impact, high effort. Be honest and let these go.

Tie each high-priority item to the conversion path it affects and, where you can, to a rough revenue estimate. "Fixing the mobile form could recover roughly 40 leads a month" gets approved. "The form feels clunky" does not.

Validate, don't just assume

An audit produces hypotheses, not certainties. You believe the long form is killing conversions. Maybe. The honest next step is to test the change rather than crown it.

For high-traffic pages, run an A/B test so you measure the lift instead of guessing at it. The fundamentals of A/B testing on your website keep you from shipping a "fix" that quietly makes things worse, which happens more often than people admit. For lower-traffic B2B pages where a clean test would take months, use judgment plus before-and-after monitoring, and accept that the read is softer.

One caveat worth stating plainly: B2B traffic is often too thin for fast, statistically clean tests. That's a real constraint, not a reason to skip measurement. Track the conversion rate before and after, watch session recordings on the changed page, and give it enough time to mean something.

A UX audit isn't a one-time project. The strongest teams run a light version quarterly and a deep one once or twice a year, because the site, the traffic mix, and the buyers all keep moving. If you want the full conversion side of this, pair the audit with a structured conversion rate optimization process so fixes feed a repeatable loop instead of a one-off cleanup.

Common mistakes that waste an audit

A few patterns ruin otherwise good audits.

Auditing on opinion instead of evidence. "I don't like this section" is not a finding. "62% of mobile users never scroll past it" is. Anchor every conclusion to data or observed behavior.

Auditing the whole site at once. You drown. Pick the two or three paths that carry the most pipeline and go deep there first.

Confusing pretty with effective. A cleaner design that converts worse is a failure, no matter how it looks in the portfolio. Judge by the business outcome you wrote down at the start.

Stopping at the report. A 40-page deck nobody acts on changes nothing. The deliverable that matters is a short, ranked list of fixes with owners and dates.

Frequently asked questions

How long does a website UX audit take?

A focused audit of your main conversion paths takes a few days to a week, depending on traffic volume and how much session data you need to watch. A full-site audit can run two to three weeks. Start narrow and expand only if the data tells you to.

What tools do I need?

At minimum: an analytics tool you trust for funnels (GA4 is the common standard), a session recording and heatmap tool (Microsoft Clarity is free and solid, Hotjar is popular), and a speed tester (PageSpeed Insights). For B2B, connecting analytics to your CRM matters too, so you measure lead quality and not just form submits. Proper conversion tracking is what lets you tell a good lead from a junk one in the data.

UX audit or CRO, what's the difference?

A UX audit diagnoses where and why users struggle. CRO is the ongoing practice of fixing and testing to raise conversion. The audit usually kicks off a CRO program: it produces the first prioritized backlog, then CRO works through it and keeps the cycle running.

How many user sessions should I watch?

Patterns tend to surface after ten to twenty recordings per problem page. You're not after statistical proof here, you're after recurring behaviors. When you keep seeing the same hesitation or the same dead click, you've found something real.

Can I run a UX audit without a designer?

Yes. Most high-impact findings, broken CTAs, slow pages, confusing copy, bloated forms, don't need a designer to spot. You'll want design help to implement bigger structural changes, but the diagnosis is well within reach for a marketer or founder who follows a checklist and reads the data.

How do I know the audit actually worked?

Compare conversion rate on the fixed paths before and after, watch fresh session recordings to confirm the friction is gone, and where traffic allows, validate with a test. If the qualified-lead count on those paths climbs and the data backs it, the audit earned its keep.

A short checklist to take with you

Write down the one conversion the site exists to produce.
Map your top three or four conversion paths and audit those, not random pages.
Pull the quantitative picture: funnels, drop-off, scroll depth, device splits.
Watch real sessions and heatmaps to learn why people leave.
Run pages against the checklist: clarity, navigation, trust, forms, speed, mobile, consistency.
Rank findings by impact and effort, ship the quick wins first.
Validate the big changes instead of assuming, and re-audit on a schedule.

If your traffic is steady but the qualified leads aren't showing up, the gap is usually on the site, not in the ad account, and a UX audit is the fastest way to find it. If you'd rather not do it solo, we can run a focused audit of your top conversion paths and hand you a ranked list of fixes tied to expected lift, so you know what to change first and why. Send us your busiest landing page and we'll point out the leaks.