The 30-Minute Landing Page Audit

Minutes 0–5: message

Before opening the page, write down two things: the audience it is meant to serve and the one action it should produce. If you cannot state both from memory, that is your first finding.

Now load the page on a phone, cold, and look only at the first viewport. Ask what is being offered, to whom, why it is credible, and what to do next. Anything you cannot answer in five seconds is a message problem, not a design preference.

• Does the headline name an outcome rather than describe the company?
• Does the page repeat the promise from the ad, email, or query that drives its traffic?
• Is the primary action visible without scrolling?
• Is the deliverable concrete—what arrives, and when?
• Would the intended audience recognize themselves in the first two lines?

Write findings as observations rather than instructions: “the hero describes the platform, not the buyer’s outcome” is actionable by anyone. “Make the headline better” is not.

Minutes 5–12: argument

Read only the section headings, top to bottom. They should form a coherent argument on their own: relevance, outcome, mechanism, proof, objections, close. If the headings read as a feature list, the page is describing rather than persuading.

Then check each section for a single contribution. Any section that does not add new information—new proof, a new objection handled, a new part of the mechanism—is padding, however handsome it looks.

Look specifically at proof placement. Is evidence beside the claim it supports, or collected in one block near the footer? Is it attributed and specific? Is anything asserted that the page cannot substantiate? Unsupported numbers are a finding, not a style note.

Finish this block by listing the top three objections a qualified buyer would raise—cost, effort, credibility, timing, internal approval—and checking whether the page answers each one. Unanswered objections are usually the largest available conversion gain.

Minutes 12–20: interaction

Now use the page as a visitor rather than reviewing it as a reader. Throttle the connection, reload, and watch what appears first and what moves after it.

1. Does the hero content render quickly, or wait on images, fonts, or scripts?
2. Does anything shift position as assets arrive?
3. Does the primary button respond immediately when tapped?
4. Fill the form with autofill: do the input types and labels cooperate?
5. Submit it wrong on purpose: is the error specific, adjacent, and helpful?
6. Submit it correctly: is the confirmation clear about what happens next?

Then run one keyboard-only pass. Tab through the page, confirm focus is always visible and ordered sensibly, and complete the form without touching the mouse. Zoom to 200 percent and check that nothing is clipped or overlapping.

Count the form fields and ask, for each one, whether the promised next step genuinely requires it. Fields that exist for future reporting are friction you are paying for with campaign budget.

Minutes 20–26: trust and measurement

Look at the page the way a cautious buyer would. Is it obvious who is behind it? Are there real people, real work, and verifiable specifics? Is the privacy language plain and the data request proportionate?

Check what the page avoids saying. Pages that never mention price, timeline, scope boundaries, or who they are wrong for tend to read as evasive to experienced buyers, and they generate inquiries the sales team then has to disqualify.

Then verify the plumbing. Does the conversion event fire once and only once? Does the submission reach the destination system with campaign and page context attached? Is someone specific responsible for responding, within the time the page promises? Does the confirmation email match that promise?

Finally, look at the numbers you already have: conversion by device, scroll depth, form field drop-off, and qualified rate by campaign. Field data will often confirm or overturn half of what you assumed in the first twenty minutes.

Minutes 26–30: prioritize

You now have a list of findings and four minutes to make it useful. Sort each item on two axes: likely impact on the decision, and effort to implement.

Take the high-impact, low-effort items first—they are usually a rewritten headline, an honest button label, a hero image sized correctly, two fields removed from the form, and one line about what happens after submission. Those five changes routinely address the most consequential friction on a page.

Then name the one structural bet worth planning: a reordered page, a different offer, a new proof strategy, or price disclosure. Structural changes are also the only ones large enough to test meaningfully on typical campaign traffic.

Write the output as a short prioritized list with an owner and a date for each item, plus the single metric you expect to move. A page audit that produces four scheduled changes beats one that produces forty observations nobody actions.

Then put the audit on a recurring schedule. Offers change, campaigns change, and pages decay quietly; a repeatable half hour every quarter keeps that decay from becoming a rebuild.