The One-Hour Conversion Audit: A Structured First Pass

Run five passes in order. One: the funnel's step rates against baseline, by device (ten minutes) - note the worst stage. Two: the arrival pass - your top three landing pages against the ads, emails or results that feed them (ten minutes). Three: the shortlist test - find three specific products as a stranger, on a phone, timing the narrowing (fifteen minutes). Four: the mechanical pass - one full test purchase per main product type, including one deliberate form mistake (fifteen minutes). Five: the cold read - one page read aloud by someone who did not build it (ten minutes). Write findings in the audit format as you go; the hour ends with defects listed and one stage nominated for the full-day audit.

Starting with pages invites the audit to become a taste tour. Start with rates: the five-line funnel, this period against baseline, split by device and by new versus returning where the tools allow. Mark the stages whose movement needs explaining and the stages that are stable; the audit's remaining fifty minutes belong disproportionately to the movers. If a rate cannot be produced for a stage, that absence is itself a finding - an unmeasured stage gets an instrumentation task on the fix list, ranked above most page work.

The arrival pass reuses the landing bench's match audit on the three pages that receive the most bought or sent traffic: promise in words, numbers and images checked against the source. The shortlist test then examines browsing honestly: pick three products a customer would plausibly seek (one popular, one obscure, one with a deciding attribute like a size or compatibility), and find each by navigation, filters and search, on a phone, noting every hesitation. Failures here are findings with timestamps, not impressions.

Buy something. A full test order per product type, on the phone, paying with a test method or the smallest real basket: add with variants, edit the cart, start checkout, make one deliberate error (a mistyped postcode, an incomplete card) and grade the recovery, complete or abandon at the payment step per your platform's test mode. Mechanical defects found here - the blocked add, the lost form, the error that clears the page - go to the top of the fix list regardless of the audit's other findings, because they tax intent that has already been won. Log the test orders so they can be excluded from the period's rates.

Close with fresh ears: a page (the worst stage's main page) read aloud by someone outside its making, paraphrasing the offer as they go. Their paraphrase beside the intended offer is the audit's most quotable finding. Then write up while the hour's evidence is warm: findings in format, defects first, the nominated stage for deep work second, and anything noticed but unproven parked in a clearly labelled 'leads' list, separated from findings so the fix list never confuses the two. The hour audit's honesty rule: it locates and nominates; it does not diagnose causes it did not have time to evidence.

Run the hour monthly, at the baseline review sitting, and let its nominations schedule the quarterly full-day audit. Over a year the hours compound into a surveillance system: mechanical defects caught within weeks of their introduction, stages nominated on movement rather than on hunches, and a findings archive that shows the funnel's biography. The hour is deliberately small enough to survive busy months; an audit rhythm that collapses under workload is a plan, not a system.

Fix the hour's shape in a one-page template so it survives tired months: the five passes with their minutes, the finding line (stage, observation, evidence, class: defect, nomination or lead), and the closing counts - defects found, stage nominated, leads parked. Print the template; audits conducted from a sheet get finished, while audits conducted from memory quietly shrink to the passes the auditor enjoys. File the completed sheet with the month's baseline. After six months the stack of sheets is itself an instrument: defect types recurring across sheets name the process that keeps producing them, which is a finding no single hour could file.