A landing page audit you can run in ten minutes
These are the checks I run on every landing page I design or review, written so you can run them yourself. Work down the list with your page open beside it, on a phone as well as a laptop, and answer each check honestly: Yes, Partly, No, or Not relevant when it doesn't apply to this page.
Unlike graders that scan a live URL, this landing page checklist works on a page that isn't live yet: a Figma file, a staging link or a draft. Nothing is sent anywhere. Your answers stay in your browser and in the page's address, so you can come back to them, or send the link to whoever is fixing the page.
How the landing page score works
Each check carries a weight of 1, 2 or 3 for how much it tends to move conversions. A Yes earns the full weight, Partly half and No nothing. Not relevant takes the check out of the sum, so a page with no form isn't marked down for form errors.
- 85 and up, Strong: the basics are in place; test the headline and the offer next.
- 70 to 84, Good: a solid page with a few gaps.
- 50 to 69, Needs work: visitors are leaving for reasons you can fix.
- Under 50, Losing visitors: fix the first screen and the form before spending on traffic.
Fix these first lists the five misses that weigh the most, with a No ahead of a Partly. Start at the top: those are the fixes most likely to change the result.
The checks that matter most
Across the 35 checks, seven carry the top weight, and they are where most landing pages lose people: a headline that says what it is and who it's for, a button on the first screen, one goal per page, real testimonials, a short form, the main content showing in under 2.5 seconds, and a conversion you can measure.
If time is short, run only those. A page that gets them right usually converts well before any of the finer points are done.
Speed and mobile: measure, don't guess
The speed checks follow Google's Core Web Vitals: the main content should show within 2.5 seconds (Largest Contentful Paint), the layout should stay still (Cumulative Layout Shift) and taps should respond at once (Interaction to Next Paint). Run the page through PageSpeed Insights and answer from its field data where it has some.
For the mobile checks, use a real phone, not only a narrow browser window. Tap every button with your thumb, fill the form, and read a full section without zooming. For readable type at every width, the fluid typography calculator writes the CSS; for a button that stands out and stays legible, check its colours in the colour contrast grid.
Share the report and fix in order
The page's address updates with every answer, so Copy share link gives a link that opens this exact audit for anyone, with no account. Copy report gives the whole result as Markdown for a ticket, a doc or a chat, and Print gives a clean page to save as a PDF.
Fix the top items, then run the audit again. When the score moves past 85, the next gains come from testing: one change at a time, against real numbers.
When the fix is bigger than a tweak
Some misses take an afternoon: a button label, a form field, a compressed image. Others mean a new message, new proof and a faster build, which is a redesign. That is what I do in landing page design: one page, one job, designed and built in one pass.