Why Reading Time Matters for Blog UX (And How to Calculate It)

Why Reading Time Matters for Blog UX (And How to Calculate It)

Reading-time labels — those small "7 min read" badges next to article titles — have become a default element of modern blog UX. Medium made them famous. Substack uses them. LinkedIn uses them. Most well-designed publisher sites use them. They look like a small UX detail, but the data behind them is more interesting than most writers realize.

A reading-time label is doing two jobs at once. It's a UX affordance that helps readers decide whether to start reading now or save for later. And it's a content-quality signal that frames reader expectations. Get it right and you reduce bounce rate. Get it wrong and you either over-promise (reader sees "3 min" and abandons a dense 8-minute piece halfway) or under-promise (reader sees "12 min" and never starts a piece they'd have finished).

This article covers what the research actually says about reading speed, why the "200 wpm" standard exists, where it breaks down, and how to calculate reading time accurately for different types of content.

The 200 WPM Standard: Where It Comes From

The most common reading-time calculation in use today is:

Reading time (minutes) = Word count ÷ 200

This 200-words-per-minute standard has been around for decades. It traces back to research summarized in The Psychology of Reading (Just & Carpenter, 1987) and to the broader literature on silent reading rate reviewed by Keith Rayner and colleagues. The 200 wpm figure sits roughly in the middle of the range reported for adult silent reading of moderately complex prose.

But 200 wpm is a population average, not a constant. Real reading rates vary by:

• Reader age and skill. Adults reading their native language average 200–300 wpm for general prose; college-educated adults often exceed 300 wpm. Children average much slower (around 100–150 wpm for upper-elementary grades).
• Text difficulty. Reading rate slows with text complexity. A reader who covers 350 wpm on a blog post might drop to 150 wpm on a research paper and 80 wpm on a legal contract.
• Reading purpose. Skimming (400–700 wpm) and scanning (600+ wpm) are different modes from reading for comprehension.
• Domain familiarity. A reader deeply familiar with a topic reads 30–50% faster on it than on unfamiliar material.

So 200 wpm is a conservative middle-of-the-road estimate. It's slightly slow for an average adult reading easy prose and slightly fast for a difficult text — which is why it works as a general-purpose standard. It errs on the side of overestimating time, which is the safer direction.

What the Research Actually Says

The two most-cited modern sources on silent reading rate:

1. Marc Brysbaert's 2019 paper (Quarterly Journal of Experimental Psychology), "How Many Words Do We Read per Minute? A Review and Meta-analysis of Reading Rate." Brysbaert analyzed 190 studies and concluded that the average silent reading rate for adult native speakers reading non-technical text is 238 wpm, with a range of roughly 175–300 wpm across studies.
2. The earlier review by Keith Rayner and colleagues (cited in his 1998 Psychological Bulletin paper "Eye movements in reading and information processing: 20 years of research") consistently reported 200–250 wpm for adult silent reading of standard prose.

The Brysbaert number — 238 wpm — is the most rigorous modern estimate we have. So why do most platforms still use 200?

Because 200 wpm is a deliberate under-estimate. Platforms like Medium and Substack use it because:

• It accounts for slower readers. Half the population reads slower than the mean. Using a conservative figure keeps the label accurate for more readers.
• It accounts for skimming behavior. Readers don't read every word on a page; they pause on headings, skim lists, skip examples. The effective reading rate is slower than the per-word rate suggests.
• It accounts for non-text content. Most blog posts include images, code blocks, tables, and pull quotes that consume reading time but aren't counted in word count. The slower rate compensates.

A "7 min read" estimate at 200 wpm is, in practice, a "5–9 minute" reading experience depending on the reader and the content. The 200 wpm figure averages out to a number that most readers find roughly accurate.

The Three Reading Rates That Actually Matter

If you're building a reading-time calculator, three different rates apply:

1. Silent reading rate (general prose)

This is the Brysbaert number: 238 wpm for adult native speakers reading non-technical text. Use 200–250 wpm as your range. The median WordPress plugin and most publishing platforms default to ~200–265 wpm.

2. Speaking rate

When you're calculating the duration of a podcast, video script, or audiobook, the relevant rate is the spoken-word rate, which is much slower than silent reading. The industry standard for audiobooks is 150 wpm (Audible's recommended rate). For conversational speech, the range is typically 130–180 wpm. TED talks average around 140–160 wpm.

If your blog post includes an audio version, the listening time will be roughly 1.5× the reading time. A 7-minute read becomes a 10–11 minute listen.

3. Skimming rate

When readers skim, they read 400–700 wpm, picking out headings and key sentences. Most web readers default to a skim mode, especially on mobile. If your analytics show that visitors spend an average of 90 seconds on a 1,500-word page, they're skimming — not reading 1,500 words at 1,000 wpm.

This is the gap between "reading time" labels and "time on page" in your analytics. Reading time estimates the engaged-reading duration. Time on page measures what actually happens, which is often a mix of skimming, pausing, and abandonment.

Why Reading Time Labels Matter for UX

Reading-time labels affect reader behavior in measurable ways. Three findings from the UX research:

1. Reduced bounce on long content

When a long article has a clear reading-time label, readers are less likely to bounce. The label sets an expectation: "this is a 12-minute investment." Without the label, readers hit a wall of text and leave. Multiple A/B tests from publisher sites (Chartbeat has reported on this) show 5–15% reductions in bounce rate when reading time is shown for long-form content.

The mechanism is commitment framing. A reader who sees "12 min read" can decide whether they want to invest that time before they start. A reader who encounters unframed length bounces when they hit mental resistance at the halfway point.

2. Higher completion rate for short content

Counter-intuitively, reading-time labels also help short content. A "2 min read" label signals low investment, which encourages readers to start — and once started, completion rates go up. The label turns a vague commitment into a defined one.

3. Better save-for-later decisions

When readers see "18 min read" on their phone, many will save the article to Instapaper/Pocket rather than attempt it. This is good UX: it acknowledges that some content isn't right for the current context. Sites without reading-time labels lose these saves because readers don't have the data to make the call.

How to Calculate Reading Time Accurately

If you're building a reading-time calculator or just want to estimate manually, here's the actual method:

Basic formula

Reading time (minutes) = Word count ÷ Reading rate (wpm)

For most web content, use 200 wpm to match what readers expect from Medium and Substack. For a more research-accurate number, use 238 wpm (Brysbaert's meta-analytic mean).

Worked example

Consider a 1,890-word blog post:

• At 200 wpm: 1,890 ÷ 200 = 9.45 minutes → 9 min read
• At 238 wpm: 1,890 ÷ 238 = 7.94 minutes → 8 min read
• At 265 wpm (faster adult readers): 1,890 ÷ 265 = 7.13 minutes → 7 min read

The choice of rate affects the displayed time by roughly 25% across the realistic range. Most platforms round to the nearest minute and use the lower rate (200 wpm), which produces the longer estimate. This is the safer choice — readers are more annoyed by an under-estimate ("3 min read" that takes 6 minutes) than by an over-estimate ("7 min read" that takes 5).

Advanced calculation: weighted by content type

A more accurate reading-time calculation accounts for the fact that not all words read at the same rate. The simplest weighted model:

| Content element | Effective rate |

|---|---|

| Body text (prose) | 200–250 wpm |

| Code blocks | 100–150 wpm (read more slowly) |

| Tables | 80–120 wpm (cell-by-cell scanning) |

| Image captions | 150 wpm |

| Bullet lists | 250–300 wpm (faster scanning) |

| Headings | 250 wpm |

Plus a fixed time per non-text element:

| Element | Add |

|---|---|

| Image (decorative) | 3 seconds |

| Image (informational) | 10 seconds |

| Embedded video | Video length × 0.3 (most readers skip) |

| Pull quote | 5 seconds |

| Chart/graph | 15–30 seconds |

So a 1,500-word post with 4 images, 1 chart, 1 code block, and 3 bullet lists might be calculated as:

• 1,500 words ÷ 225 wpm (blended average) = 6.67 min
• 4 images × 5 sec = 20 sec = 0.33 min
• 1 chart × 20 sec = 0.33 min
• Total: ~7.3 min → 7 min read

This is more work, but it produces estimates that track real reader behavior more closely. Most production reading-time tools skip the weighting and use the simple word-count ÷ rate formula because the marginal accuracy isn't worth the complexity.

The image tax

One adjustment every reading-time calculator should make: add time for images. A simple heuristic that produces noticeably better estimates:

Reading time = (Word count ÷ 200) + (Image count × 0.12 minutes)

That is, add ~7 seconds per image. This single change closes most of the gap between calculated reading time and measured time-on-page for image-heavy content.

Reading Time vs. Time on Page: Why They Differ

A common confusion: looking at Google Analytics and seeing "Average time on page: 1:24" for an article labeled "8 min read," and concluding the reading-time estimate is wrong.

The two numbers measure different things:

• Reading time = how long it would take to read every word, assuming the reader is engaged.
• Time on page = how long the reader actually stayed, including skimming, pausing, getting distracted, and abandoning.

Time on page is almost always shorter than reading time, because:

• Most readers skim, not read.
• Many readers abandon partway through.
• Mobile readers in particular skim and bounce.
• Some readers pause on a section, go elsewhere, and come back.

A realistic rule of thumb: engaged readers spend 40–70% of the calculated reading time on the page. If your reading-time label says "8 min" and your average time on page is 4–6 minutes, your content is performing well. If time on page is well under that range — say, 1:30 on a "8 min read" — your engagement is poor, regardless of what the label says.

Common Mistakes in Reading-Time Estimation

A few recurring errors in reading-time calculators:

Mistake 1: Using 250+ wpm

Some tools use 250 or 265 wpm, which makes reading times look shorter. This pleases the writer (the post seems quicker) but frustrates the reader (the post takes longer than promised). Stick with 200–225 wpm for general content.

Mistake 2: Not counting images

The simplest improvement you can make to any reading-time tool. Images take time to look at.

Mistake 3: Rounding up aggressively

A 1,050-word post at 200 wpm = 5.25 minutes. Round to 5, not 6. Rounding up makes the post feel longer than it is.

Mistake 4: Using different rates for different content types without disclosure

If your blog uses 200 wpm for blog posts and 150 wpm for newsletters, readers will be confused. Pick one rate and stick with it.

Mistake 5: Treating "1 min read" as a real estimate

Below about 200 words, reading-time labels lose meaning. A 90-word paragraph is "30 seconds," but readers experience it as "very short" rather than as a discrete time commitment. For very short content, label it "quick read" rather than "1 min read."

When Not to Show Reading Time

Reading-time labels aren't universally helpful. Skip them when:

• The content is interactive (calculators, tools, quizzes). Reading time is irrelevant.
• The content is reference material (glossaries, documentation). Readers will jump around, not read linearly.
• The content is news. News readers want recency, not time investment framing.
• The content is very short. Below ~200 words, a label adds noise.
• The content is primarily visual. Photo essays and infographics don't fit a word-count-based estimate.

The Bottom Line on Reading Time

Reading-time labels are a small UX detail with outsized effects. They reduce bounce, improve completion, and frame reader expectations. The 200 wpm standard that most platforms use is a conservative estimate that errs on the side of accuracy for the slower half of readers.

If you're building a reading-time feature or just estimating manually, the formula word count ÷ 200 is the right default. For more accuracy, add 7 seconds per image and weight code blocks and tables as slower-to-read elements. For audio version estimates, use 150 wpm (the audiobook standard).

The number you produce won't match every reader's actual time. That's fine — the label is an expectation-setter, not a stopwatch. As long as it's roughly right (within 1–2 minutes of actual time for an engaged reader), it does its job: helping readers decide whether to start, save, or skip.

Our reading time calculator gives you live reading and speaking time estimates using the standards above, plus character and word counts. Use it to label your drafts honestly before you publish — your readers (and your bounce rate) will thank you.