The science of reading speed
Reading speed research has consistently placed the average adult’s silent reading rate between 200 and 400 words per minute. The landmark 2019 meta-analysis by Rayner, Schotter, Masson, Potter, and Treiman synthesised data from 190 studies and found a median silent reading speed of approximately 238 words per minute for adult readers of English prose — which is why many reading time tools, including the Reading Time Estimator, default to exactly that figure.
That 238 wpm figure is a median, not a ceiling. A slow reader working through dense academic text might manage 100–150 wpm. An experienced professional skimming a familiar topic can process 400–600 wpm. Speed readers using techniques like chunking — reading groups of words rather than individual words — can reach 700 wpm or more, though research suggests comprehension drops sharply past 400 wpm.
Several factors affect individual reading speed:
- Familiarity with the subject. Readers move faster through content they know well.
- Text complexity. Long sentences, rare vocabulary, and nested clauses all slow readers down.
- Font, layout, and line length. Well-typeset content with comfortable line lengths (50–75 characters) reads faster than walls of small text.
- Reading environment. Distraction, fatigue, and reading from a backlit screen all reduce speed.
For practical purposes, 238 wpm is an excellent default for blog content aimed at general audiences. For academic papers, use 150–180 wpm. For skimmable listicles, 300–350 wpm is reasonable.
How platforms calculate read time
Every major publishing platform has settled on its own convention:
Medium is the most cited example. Medium uses 265 wpm as their reading speed baseline, then adds image time: 12 seconds per image for the first three images, and 3 seconds per additional image. They round up to the nearest minute. So a 530-word article with two images would be: (530 ÷ 265) × 60 = 120 seconds + 24 seconds = 144 seconds → 3 min read. Medium’s formula became the industry benchmark and is why “3 min read” is now a near-universal publishing convention.
Substack uses approximately 200 wpm for most newsletters. Their system also accounts for whether images are present, but the details are not publicly documented.
Dev.to uses 275 wpm and adds extra time for code blocks — roughly 30 seconds per code block on the assumption that readers pause to study code more carefully than prose.
Ghost (the blogging platform) also uses 275 wpm by default, which is configurable per publication.
The takeaway: if you want your estimated read time to match a specific platform, you can dial in that platform’s WPM in the custom WPM field of the Reading Time Estimator.
Why reading time badges increase engagement
Research by Chartbeat — a content analytics firm that monitors reading behaviour across thousands of publications — found that articles with a prominently displayed reading time estimate have significantly higher scroll depth and time-on-page. Readers who know what they are committing to before they start are more likely to finish.
The psychology is straightforward: uncertainty is cognitively costly. A reader looking at an unmarked article does not know if they are starting a 2-minute skim or a 20-minute commitment. Faced with that uncertainty, many bounce. A “6 min read” label resolves the uncertainty and lets readers decide — often in favour of reading.
For newsletters, the effect is even more pronounced. Email open rates alone do not capture value. A reader who opens a 1,500-word newsletter and reads 10% of it is less engaged than one who reads a 600-word newsletter end to end. Knowing your read time lets you calibrate newsletter length to your audience’s attention budget.
WPM varies by content type
Not all text is read at the same speed. Here is a practical WPM reference by content type:
| Content type | Recommended WPM to use |
|---|---|
| Literary fiction, narrative non-fiction | 250–280 |
| General blog post or article | 230–260 |
| Technical documentation | 180–220 |
| Academic paper or textbook | 150–180 |
| Legal or regulatory text | 120–160 |
| Skimmable listicle or FAQ | 300–350 |
| Email newsletter | 220–250 |
| Screenplay or stage script | 180–210 |
When in doubt, use 238 wpm for general prose. Use 130 wpm for speaking time estimates — that is the comfortable, clear pace used by professional presenters and is close to the average TED talk delivery of 130–160 wpm.
Readability grades: Flesch-Kincaid and how to use them
The Flesch-Kincaid Grade Level formula estimates the US school grade at which a reader should be able to understand a text. The formula is:
FK Grade Level = 0.39 × (words/sentences) + 11.8 × (syllables/words) − 15.59
The two inputs — average sentence length (words per sentence) and average word complexity (syllables per word) — capture the two main drivers of text difficulty. Long sentences and polysyllabic words both raise the grade level.
Grade level bands and what they mean in practice:
- Elementary (below Grade 5): Very simple, short sentences, common vocabulary. Good for children’s content, plain-language government notices, or crisis communication.
- Middle School (Grade 5–8): Accessible to most adult readers. This is the target for popular blogs, marketing copy, and consumer journalism.
- High School (Grade 8–12): Some complexity. Suitable for professional audiences, quality journalism, and non-fiction books.
- College (Grade 12–16): Dense writing requiring sustained attention. Academic journals, legal documents, technical reports.
- Graduate / Academic: Highly complex. Philosophy papers, advanced scientific literature.
The complementary Flesch Reading Ease score runs in the opposite direction: higher is easier. Scores of 60–70 are “standard” for general audiences; 70–80 is “fairly easy”; below 30 is “very difficult.” Popular news sites typically score 50–60.
For readability grades to be meaningful, the text needs to be primarily prose. Code-heavy or URL-heavy content will show artificially high grade levels because long tokens inflate the syllable count.
Speaking time for video scripts and podcasts
When writing for audio — a podcast script, a YouTube video, a conference talk, a webinar — word count translates directly to running time at the pace you speak. The Reading Time Estimator uses 130 wpm for speaking time, which is the mid-point of the 120–150 wpm range recommended by presentation coaches.
Some reference points:
- TED talks: 130–160 wpm average across the TED corpus. The strict 18-minute format at 130 wpm works out to approximately 2,340 words.
- Podcasts: Conversational podcasts run 140–180 wpm. Scripted narrative podcasts are typically 130–150 wpm.
- Audiobooks: Professional narrators usually target 150–160 wpm.
- YouTube explainers: 120–150 wpm for clear comprehension; faster for high-energy content.
If you write at 130 wpm but speak faster, measure a 60-second sample of your own delivery using the estimator: paste what you read aloud in 60 seconds and check the word count. That is your actual speaking WPM.
Using the Reading Time Estimator in your workflow
Here is a practical workflow for content teams:
- Draft in your usual tool (Google Docs, Notion, your CMS).
- Paste the draft into the Reading Time Estimator.
- Check the average speed (238 wpm) against your content length target. Most blog posts aim for 5–10 minutes; most newsletters aim for under 4 minutes.
- Check the readability grade. If it shows College or Graduate for a general audience post, simplify sentences and replace jargon.
- Use the custom WPM if your audience skews technical (raise WPM) or non-native English speakers (lower WPM).
- Copy the “X min read” label to paste into your CMS or blog header.
For presentations, repeat step 2 with your script and check the speaking time at 130 wpm instead of the reading time.
Content length for SEO
Backlinko’s analysis of 11.8 million Google search results found that the average first-page result is 1,447 words. Their subsequent research found that long-form content (3,000+ words) gets significantly more backlinks than shorter articles. However, content length is a proxy for comprehensiveness — not a ranking signal in itself.
Practical guidance by content type:
- Blog post (informational): 1,500–2,500 words (6–10 min read)
- Product/service page: 700–1,200 words (3–5 min read)
- Pillar page / ultimate guide: 3,000–5,000 words (12–20 min read)
- Email newsletter: 300–600 words (under 3 min read)
- Social media caption: Under 300 characters (under 30 sec read)
Pair the Reading Time Estimator with the Word Counter to track word count against SEO targets. For assignments and essays with hard word limits, the Essay Word Target Tracker shows progress toward a specific target. For more on the difference between counting words and counting characters, see Word Count vs Character Count.