Rewriting Your Homepage for a Distracted Reader
Your homepage should be written for someone doing three other things at once, because that's who's reading it.
Picture the person actually reading your homepage. Not the one you imagine — leaning in, coffee in hand, giving you their full attention. The real one. They’re on a phone, on a train, with a message thread open in another app. They tapped your link from somewhere, half-remember why, and will be interrupted within thirty seconds by something that beeps. This is your reader. Nearly all of your readers. And almost every homepage I audit is written for the other person, the attentive one, who barely exists.
Writing for the distracted reader is a distinct craft, and the first move is to front-load ruthlessly. Distracted reading is prefix reading: people read the first words of a headline, the first sentence of a paragraph, the first line of a list, and bail the moment the payoff seems far away. So the payload has to come first, everywhere, at every scale. Not “With over a decade of experience helping teams collaborate, Acme is the platform that…” but “Acme finds the bugs in your checkout flow.” The first version makes me wade through fifteen words of throat-clearing to reach the point. The distracted reader doesn’t wade. They’ve already flicked back to their messages.
The second move is to kill the warm-up. Most homepage copy begins the way people begin speeches, with context-setting: the world has changed, work is more complex, customers expect more. The writer needs this ramp to get going, and that’s fine — write the ramp, then delete it. The essay can keep its wind-up. The homepage can’t, because the distracted reader budget is maybe two sentences before the first judgment, and if both get spent agreeing that the world has changed, you’ve bought nothing with them. I tell people: your first draft’s third paragraph is usually your real first paragraph. Find it and promote it.
The third move is subtler: write for re-entry. The distracted reader doesn’t read your page once, top to bottom. They read a bit, get pulled away, come back, and land somewhere in the middle with no memory of what came before. A page written as one continuous argument punishes them; understanding paragraph four requires paragraphs one through three, which are gone. A page written for re-entry makes each section self-sufficient. The section heading restates its subject instead of coyly referencing the previous section. Pronouns get replaced with nouns at section boundaries — “it” becomes “the scanner” — so a reader parachuting in mid-page knows what’s being discussed. This feels redundant when you read the page straight through. Almost nobody reads the page straight through.
Then there’s the sentence-level work, which is mostly subtraction. Distraction shrinks working memory, so sentences that are merely long become effectively unreadable. A subordinate clause the attentive reader carries with ease gets dropped by the distracted one, and when the clause carried the meaning, the meaning is gone. The practical rule: one idea per sentence, subject near the front, verb close behind it. This produces prose that a sophisticated writer might find plain. Good. Plain is what survives interruption. Nobody ever bounced from a homepage because it was too easy to understand.
What I find interesting, having built a tool that grades this, is how measurable the gap is between how sites are written and how they’re read. GazeSite looks at a page the way a stranger does — a screenshot, a few seconds, what’s actually visible on a phone — and the readability findings on homepages are strikingly uniform: sentences built for print, key claims buried mid-paragraph, meaning that only emerges if you read everything in order. These aren’t careless sites. They’re often carefully written sites, carefully written for the wrong reader. The care went into flow and elegance, qualities that pay off over sustained attention, which is precisely the thing the medium doesn’t supply.
There’s an objection worth taking seriously: doesn’t this pander? If we write for the least attentive reader, don’t we insult the attentive one? I used to worry about this and no longer do, for two reasons. First, the attentive reader is not harmed by front-loaded, plain, re-enterable prose; they just read it faster. Clarity has no ceiling on who it serves. Second, attention isn’t a personality trait, it’s a state. Your most sophisticated prospect — the one you’d write the elegant version for — is also on a train, also has the message thread open. Writing for the distracted reader isn’t writing for dumb people. It’s writing for smart people at a bad moment, which is when they happen to be reading you.
So here’s the rewrite procedure I’d actually suggest. Open your homepage on your phone. Read it in three-second bursts, looking away between bursts, the way you’d read while walking. After each burst, say out loud what you learned. Wherever you learned nothing — that’s a burst you paid for and the page wasted — cut or front-load until the burst pays. It’s a crude method. But your reader is reading crudely, and the page that works under crude reading is the page that works.
More articles
Complicated language locks people out of your site as surely as bad contrast does, and simplifying it is the accessibility fix that needs no code.
Read →The page shown right after signup is seen by every single customer at their moment of peak attention, and it's usually the least designed page on the site.
Read →The issue GazeSite flags most often is not a technical bug but a page that never says what the site does.
Read →