- May 29, 2026
- 4 min read
Above the Fold in Five Seconds: The Checklist I Wrote
Part 2 of the series. Part 1: a landing page pipeline that refuses to ship a bad offer.
The first screen of a landing page, before any scrolling, has one job: make a stranger understand what this is, who it’s for, and what to do next, in about five seconds. Everything else on the page is for the people who stayed.
This is the checklist I wrote for it. Most of it follows Alex Hormozi’s advice on headlines and offers; the rest comes from pages of my own I’d got wrong.
The anatomy
Top to bottom:
HEADLINE the result, not the product
DRAMA LINE a short, big line with the idea
Without:
· a specific pain
· another specific pain
· a third, at most a fourth
[ ONE BUTTON ] verb + outcome
risk reversal the guarantee in 15 words or fewer
proof strip only if it's real
The text sits in the lower left; the image behind it gets room to breathe.
Block by block
Headline: the result, not the product. Six to twelve words about what the customer gets.
- Bad: “AI-powered marketing automation platform.”
- Better: “Triple your qualified leads in 90 days.”
The “without” line. Hormozi’s pattern: after the result, remove the pains the reader already feels. Two to four, specific and, if possible, with a number.
- Bad: “Without complexity. Without high cost.”
- Better: “Without hiring a sales team. Without writing a cold email yourself.”
One call to action. A verb and an outcome: “Book the 90-day audit”, “Get the checklist”. Never “Submit”, “Learn more” or “Get started”. And only one: three buttons (“Free trial”, “Demo”, “Pricing”) is three decisions, so people make none.
Risk reversal under the button. The guarantee, compressed: 8 to 15 words, with a time window and what happens if it fails.
- “Hate it in 14 days? Full refund, no questions.”
It answers “will I lose money?” before the click, not three screens later.
Proof, only if it’s real. A row of client logos, a couple of numbers, or one quote with a name. If there’s no proof yet, there’s no strip. Placeholder testimonials are worse than none: a technical reader spots them at a glance.
The image. Behind the text, with a dark gradient so the text stays readable. No product screenshots (they belong further down), and no stock photos of people pointing at laptops.
Friction rules
- No cookie banner or popup over the first screen on first load.
- No autoplay video. A video is a card you click.
- On mobile, the menu collapses to the logo and the one button. The “without” lines stack, the button goes full width.
- A form on the first screen asks for three fields at most. Email alone is best.
The five-second test
Before shipping, show the page to someone who hasn’t seen it, for five seconds, then close it. They should be able to answer:
| Question | Answered by |
|---|---|
| What does this do? | the headline |
| Who is it for? | the headline or the “without” line |
| What do I get? | the result in the headline |
| What do I do next? | the button |
| Why should I trust it? | the risk reversal or the proof |
Any “I don’t know” means the first screen needs another pass. It’s cheap, humbling, and better than any analytics dashboard for a page nobody has visited yet.
How it maps to the copy file
In my blueprint every block is a
field in site.md, so the rules can be checked instead of remembered:
| Block | Field | Rule |
|---|---|---|
| Headline | hero.headline | result, not product |
| Drama line | hero.drama | one line |
| Without | hero.without[] | 2–4 items |
| Button | hero.cta_label, hero.cta_target | one, verb + outcome |
| Risk reversal | hero.risk_reversal | 15 words or fewer |
| Proof | social_proof[] | empty is allowed; fake is not |
Next: the offer I tested all of this on.
Takeaways
- Five seconds: what, for whom, what next.
- Headline = result. Sub-headline = the pains it removes.
- One button, with a verb and an outcome.
- Put the guarantee under the button, in 15 words.
- No proof is better than fake proof.
- Test with a stranger before you test with analytics.