Eleanor Whitfield
Your Reader Is Skimming, and That Is Alright
You spend three hours polishing a blog post. You hit publish, check the analytics a day later, and discover the average visitor stayed for eleven seconds. It stings. But it is not a verdict on your writing.
People read online differently from the way they read a novel. They arrive mid-task, often from a search result or a crowded inbox, looking for one specific answer. Their eyes jump down the page hunting for the part that matters. If they cannot find it quickly, they leave — not because your prose is poor, but because the shape of the page gave them nothing to hold on to.
Scannable writing is not dumbing down. It is a courtesy. It means the reader who skims still comes away with your main point, and the reader who stays gets the full argument in a comfortable order.
Front-Load Every Point You Make
Front-loading means putting the conclusion first, then the reasoning. Academic writing builds towards a revelation; web writing hands over the answer and then explains how you got there.
Compare these two openings:
Buried: "After weighing up a number of factors, including cost, setup time and ongoing maintenance, it became clear to us that..."
Front-loaded: "Choose the simple setup. Here is why the cheaper, plainer option wins for most small sites."
The second version respects the reader's time. It also survives skimming: even if someone reads only the first sentence of each paragraph, they still follow your argument. Apply the same rule at sentence level — lead with the subject and the verb rather than a long qualifying clause.
Keep Paragraphs Short Enough to Breathe
On screen, a paragraph of six dense lines looks like a wall. A paragraph of two or three sentences looks like an invitation.
Aim for roughly forty to sixty words per paragraph. Vary it: one-line paragraphs add punch and give the eye somewhere to rest. Where you would use a semicolon to bolt two ideas together, try a full stop instead.
White space is not wasted space. Margins, line breaks and short blocks of text make a page feel approachable, and approachable pages get read further down. If a paragraph runs past four lines on a laptop screen, look for a natural place to break it.
Write Subheadings That Do Real Work
Subheadings are the skeleton of your article. Many readers will scan them alone and decide from that whether to read on, so they need to say something.
- Be specific. "How to Cut a Draft by a Third" beats "Editing Tips".
- Make a promise. "Three Ways to Open a Post" tells the reader exactly what is coming.
- Use the reader's words. If they search for "how often should I blog", a heading that echoes that phrase feels like an answer.
- Keep them parallel. If one heading is a question, make its siblings questions too. Consistency makes the structure legible at a glance.
Avoid clever headings that only make sense once the section has been read. The heading is a signpost, not a punchline.
Use Lists, Bold Text and Other Handholds
Lists are the most scannable structure on the web, but they work best with restraint. A page made entirely of bullet points reads like a slide deck. Mix prose and lists: explain in paragraphs, then summarise in a list.
The same goes for bold. Reach for it when a phrase genuinely carries the point — a key takeaway, a warning, a term the reader might be hunting for. If half a paragraph is bold, nothing stands out. A useful test: cover the page, look only at the bold text, and check whether the argument still makes sense. If it does, your emphasis is doing its job.
Numbers help too. "Three steps", "two common mistakes", "five minutes a day" give the reader a sense of scale before they commit to reading.
A Quick Editing Pass for Web Copy
Once the draft is done, read it through with structure in mind rather than grammar. Ask yourself:
- Does the first sentence of each paragraph carry the point?
- Are any paragraphs longer than four lines on a screen?
- Could a subheading be more specific?
- Is there a list hiding inside a dense paragraph?
- Have I bolded anything that does not deserve it?
Then read it on a phone. Most of your readers will, and a phone is an unforgiving editor: long paragraphs look longer, vague headings vanish, and good structure becomes obvious. Fix what jars, then publish.
None of this takes much longer than writing the way you always have. It is simply a matter of deciding, sentence by sentence, to make things easy for the person on the other side of the screen. Do that, and they will stay a little longer than eleven seconds.
