Because the page asks too much before it gives anything. Long lines, cramped text, a popup at the four second mark, and no visible structure all push people out. Most readers decide within seconds whether a page looks worth the effort, and design makes that call for them.
The writing usually is not the problem. We are handed plenty of blogs with genuinely good articles that nobody finishes. The words are fine. The page around them is working against them.
A blog post page is one of the few designs where the job is almost entirely restraint. Everything you add competes with the thing people came for, which is the text.
A comfortable line length, generous line spacing, clear heading hierarchy, and enough contrast to read without strain. Get those four right and almost everything else is optional. Get them wrong and no amount of illustration or styling rescues the page.
Reading on screen is harder than reading on paper, so the design has to do more work. Every decision either reduces friction or adds it, and there is very little that is neutral.
The Nielsen Norman Group's classic 1997 research on web reading found that 79 percent of test users always scanned any new page they came across, while only 16 percent read word by word. That behaviour has shaped how we lay out long-form content ever since.
The same research found that writing which was concise, scannable, and objective improved measured usability by 124 percent. That is a large return for changes that cost nothing but discipline.
Narrow enough that the eye can find the next line without hunting. In practice that means roughly 60 to 75 characters per line for body text. Full width text on a large monitor is the single most common readability mistake we fix.
The reason is mechanical. At the end of every line your eye has to travel back to the start of the next one. The longer the line, the more often that return lands on the wrong row, and the more tiring the page becomes.
The opposite failure exists too. Columns that are too narrow break sentences into fragments and force constant line returns, which is equally tiring. There is a comfortable band, and most blogs sit outside it in one direction or the other.
Set the measure once as a constraint and let everything else respect it. Pull quotes, images, and code blocks can break out wider, but the running text should hold its width all the way down.
Body text should be comfortably large, around 18 to 20 pixels on desktop, with line height set to about 1.5 times the font size. That spacing figure is not a matter of taste. It matches the minimum in the W3C's WCAG 2.2 text spacing criterion.
WCAG 2.2 success criterion 1.4.12 requires that content stay usable when readers set line height to at least 1.5 times the font size, spacing after paragraphs to at least 2 times, letter spacing to at least 0.12 times, and word spacing to at least 0.16 times.
The practical lesson is to design at those values rather than merely survive them. If your layout only holds together at tight spacing, it will break for the readers who need it loosest.
Test resizing too. WCAG 2.2 criterion 1.4.4 requires text to be resizable up to 200 percent without losing content or functionality. Blog templates fail this surprisingly often, usually because of fixed-height containers.
We go further into the type decisions themselves in our guide to choosing the right fonts for a website. For a blog, legibility beats personality every time.
They help when they carry information and hurt when they are decoration. A diagram that explains a process earns its place. A stock photograph of people pointing at a laptop interrupts reading and slows the page down for nothing.
Our test is simple. If removing the image loses meaning, keep it. If removing it loses nothing, remove it. Most blog imagery fails that test.
Placement matters as much as choice. An image belongs immediately after the paragraph it illustrates, not floated beside text where it fights the reading line. Breaking the column with a full width image is a strong signal, so use it where a genuine section change happens.
White space does much of the work people expect images to do, which we argued in our post on how much white space a website actually needs. Room to breathe reads as quality.
One H1 for the article title, then H2s for each major section, in order, with no levels skipped. Headings should describe what the section actually says rather than being clever. Scanning readers use them as a table of contents whether you provide one or not.
This is where design and accessibility overlap exactly. Screen reader users navigate by heading, so a correct hierarchy is a navigation system, not styling. Choosing a heading level because of how big it looks is the most common way that breaks.
Make headings visually distinct enough to find while scrolling quickly. Weight and spacing do more here than size alone. A heading that is merely slightly larger disappears at speed.
Descriptive headings also help machines. A section titled with the question it answers is far easier for a search engine or an AI assistant to match to a query than one titled with a pun.
Usually not. Sidebars were built for an era of blogrolls and archive widgets. On a modern blog they steal width from the text column and fill it with things nobody clicks. A single centred column outperforms a sidebar layout on most sites we build.
What people genuinely use is a table of contents on long articles, and a small set of related links at the end. Both can live in the flow of the page rather than in a permanent second column.
If you keep a sidebar, give it one job. A single relevant call to action is fine. Six widgets competing for attention is how a sidebar becomes wallpaper.
The end of the article is the valuable position everyone underuses. Someone who finishes a post is the most engaged reader you will get that day, and a thoughtful next step there beats anything in a sidebar.
More than most designers expect. The HTTP Archive's 2025 Web Almanac found the median home page loading 139 KB of fonts on desktop and 122 KB on mobile. Every extra weight and style you load is another file between the reader and the words.
Two families is almost always enough, and often one is better. Each additional weight is a separate download, so a design using four weights of two families is loading eight files before a word appears.
The failure mode is worse than slow. If text is hidden while fonts load, readers stare at a blank column on a page whose entire purpose is text. Showing a fallback immediately is nearly always the right trade.
Across our own builds the average PageSpeed score is 98, and font discipline is a meaningful part of that. Fewer files, subset properly, displayed early.
Directly. Readable pages hold attention longer, and clean structure makes content easier for search engines and AI assistants to parse. A well-structured article with clear headings and real answers is far more likely to be quoted than a wall of undifferentiated text.
The mechanism is unglamorous. Machines read your markup. Proper heading levels, real paragraphs, and text that exists in the HTML rather than appearing after a script runs are what make a page quotable at all.
Layout also affects whether a human stays long enough to convert, which is the point of the exercise. Blogging still earns its place for exactly that reason, as we argued in our piece on whether you should still blog for SEO.
Narrow your text column to a comfortable measure and raise your line height to at least 1.5. Those two changes take an hour, cost nothing, and improve every article you have already published as well as every one you write next.
After that, remove things. The share widgets nobody uses, the related-posts grid halfway down, the popup that fires before anyone has read a sentence. Subtraction improves blog pages more reliably than addition.
Then read one of your own posts on a phone, in daylight, all the way to the end. Most readability problems announce themselves within thirty seconds of doing that honestly.
If your articles are good and nobody finishes them, we are happy to look at the page around them and tell you what is getting in the way. Reach out through phoenix.studio and we will come back to you within 48 hours.
Tell us where you want to go. We'll tell you how we'd get you there.