The first law we build by is blunt: never ship a wall of text. Every section on every page has to survive a three-second scan. If a visitor cannot tell what a section is about, and what to do next, in about the time it takes to scroll past it, the section has failed, no matter how good the writing is.
Three seconds is not a scientific constant. It is an honest description of how people actually move through a page: scroll, land, glance, decide. The decision is binary, keep going or leave, and it gets made before a single full paragraph gets read.
This law comes first for a reason. Most of the quality problems we see on business sites are not design problems in the decorative sense. They are density problems: the right information, shipped in a form nobody will read.
How walls of text happen
Nobody sets out to build one. Walls of text arrive honestly: a migrated CMS dumps years of heading-and-paragraph runs onto a new page, a subject-matter expert writes down everything they know, a legal page has to say all of it. The copy is usually good. The container is wrong.
The tell from readers is consistent. Faced with a long unbroken run, they cannot decide whether to read it straight through like a book or jump around like a reference, so they do neither. Good words, unread, are indistinguishable from no words.
It shows up in our own drafts too. First drafts of anything, written by anyone, trend toward prose. Which is why this is a law with a test, not a preference. Preferences lose to deadlines.
Keep every word, restructure the container
Here is the part most teams get wrong: the fix is not cutting the copy. When the writing is good and the layout is failing, the writing stays. Every word survives. What changes is the container it lives in. Any prose run past about three paragraphs gets restructured into one of a small set of shapes:
- An accordion: the sections become expandable rows, the first one open so the page never looks empty
- Tabs, when the content is really two or three distinct views of one subject
- A labelled two-column checklist, when the prose is secretly a list wearing a paragraph costume
- A snapshot plus depth: a short decision-relevant summary up front, the full detail one click away
The accordion deserves special mention, because it has been the single biggest digestibility win in our catalog. Ours are native details elements: no JavaScript required, accessible by default, first section open, a plus icon that rotates to an x. A ten-section legal page becomes ten labelled rows a visitor can scan in seconds and read in any order.
Notice what the accordion does not do. It does not hide content from search engines, because the full markup is in the page. It does not need a heavy component library. It just converts an obligation to read everything into an invitation to read anything.
Where the rule came from
This is not taste in the abstract. Looking back across everything we have shipped, we keep a running catalog of design feedback and outcomes, 1,034 recorded decisions across the portfolio, and no failure pattern repeats more consistently than the wall of text. Restructuring one has never once made a page worse.
The rule extends to data. Dense technical specs are their own kind of wall, so they get the same treatment: a short spec snapshot first, the handful of values that drive a decision, then labelled key-value rows, with full depth behind one click and a proper downloadable document.
Running the scan test
The test is cheap enough to run on every section you ship. Scroll to the section cold, count three seconds, look away. Then answer two questions: what was that section about, and what would you do next? If either answer is fuzzy, the section fails.
Run it on a phone too. A section that scans fine on a wide desktop screen can still collapse into an unbroken column of gray on a 390-pixel viewport, and for most businesses the phone is where first impressions happen.
What survives the test is remarkably consistent: a specific labelled heading, a one-line lede that states the idea, and content broken into blocks the eye can enter anywhere. That is why every section we ship is framed the same way, label, then heading, then lede. No section starts cold.
The discipline compounds. A page of sections that each survive the scan becomes a page a visitor can navigate like a map instead of a tunnel. They read more, not less, because every piece invites them in. Visitors describe well-structured dense pages as short, because perceived length is a function of effort, not word count.
So the law holds on every build: prose over three paragraphs becomes an accordion, tabs, or a checklist. Keep every word. Restructure the container. The wall goes; the words stay.
