A landing page friction checklist you can run in twenty minutes

You don't need an A/B testing platform or six weeks of traffic to find the obvious problems on a landing page. Most of them are visible in a few minutes, if you look at the page the way a distracted visitor on a mobile connection sees it.

Run through this on the actual page, on an actual phone.

1. Message match

Read the ad headline, then the landing page headline, in that order.

Does the page continue the sentence the ad started? If the ad promised a specific thing (a price, a location, a service, a free consultation) and the page opens with a generic brand statement, you've already lost some of the click you paid for.

The fix is almost always copy, not design.

2. The first screen

On a phone, before any scrolling:

• Is it obvious what this business does?
• Is it obvious what the visitor is supposed to do next?
• Is the primary action visible without scrolling?

If any answer is no, you have a friction problem that no amount of testing the button colour will fix.

3. The form

This is where most of the loss happens.

• Field count. Every field is a small tax. Does sales actually use all of them? If a field is collected but never read, delete it.
• Labels. Are they above the field, or placeholder-only? Placeholder-only labels vanish as soon as someone starts typing, and people forget what the field was for.
• Input types. Does the phone show a numeric keypad for a phone number? Does it show @ for the email field? Wrong keyboard type is a real, measurable drop-off on mobile.
• Optional fields. Are they obviously optional? If someone can't tell, they'll assume every field is required.
• Errors. Try submitting an empty form. Does it explain what's wrong, in place, on the field? A red outline with no text is not an error message.
• Duplication. Does the page ask for the same information twice? It happens more than you'd expect, usually when a booking widget was bolted onto an existing form.

4. What happens after submit

Submit with your own details and time what happens next.

• Is there a confirmation that says what will happen and when?
• Does the enquiry reach a human? Check the inbox, not just the notification settings.
• How long until someone could realistically respond?

A form that works but routes nowhere is not a lead generation system. It's a data collection exercise.

5. Trust signals

Not testimonials you don't have. The things that reduce perceived risk:

• A real phone number or WhatsApp option for people who don't want to fill in a form.
• Opening hours, or an honest statement of response time.
• A physical location or service area, if relevant.
• A named person rather than "our team".

6. Speed on a phone, on mobile data

Not on office wifi. If the hero image is 2MB and the page takes four seconds to become usable, everything above is academic.

What to do with the list

Fix the items that are unambiguous first. Most of this checklist is not a hypothesis. Asking for a phone number without a numeric keypad is just a defect.

Save your testing capacity for the questions where the direction is genuinely unclear: offer framing, headline angle, form length once it's already minimal. Those are worth testing properly. The rest is worth fixing today.