Words Per Minute — Average Reading Speed by Age, Content Type, and Skill
Average adult reading speed is 200–250 words per minute, but it varies dramatically by content type, reader skill, and context. Here's the research and what it means for...
The commonly cited average adult reading speed is 200–250 words per minute (WPM). But that number is meaningless without context: reading a thriller novel is faster than reading a technical manual. Silent reading is faster than reading aloud. Expert readers process familiar domain content much faster than novices.
The Word Counter uses 225 WPM to calculate reading time — the median of commonly cited ranges for general web content.
Average reading speeds by category
By age and experience
| Age / Stage | Average WPM |
|---|---|
| Grade 1 (6–7 years) | 53–111 |
| Grade 2 (7–8 years) | 89–149 |
| Grade 3 (8–9 years) | 107–162 |
| Grade 4 (9–10 years) | 123–180 |
| Grade 6 (11–12 years) | 150–204 |
| High school student | 200–300 |
| College student | 200–300 |
| Average adult | 200–250 |
| Proficient adult reader | 300–400 |
| Speed reader | 400–700+ |
Source: Hasbrouck & Tindal (2017) oral reading fluency norms; Rayner et al. (2016) meta-analysis.
By content type
| Content type | Typical WPM |
|---|---|
| Pleasure reading (fiction) | 250–400 |
| General web content | 200–250 |
| Business/professional writing | 200–240 |
| Study reading (academic) | 100–200 |
| Technical documentation | 100–150 |
| Dense code/technical examples | 80–120 |
| Legal documents | 50–100 |
| Proofreading | 100–200 |
| Reading aloud | 100–160 |
The large variation by content type explains why a word-count-based reading time estimate is approximate. A 1,500-word article that’s 30% code blocks takes longer to read than a 1,500-word narrative.
Scan vs read: how people actually consume web content
Jakob Nielsen’s famous eye-tracking study (1997, updated multiple times) found that web users read at most 28% of words on a web page — typically scanning in an F-pattern: across the top, across a subheading, then down the left margin.
This doesn’t mean web articles should be short — longer articles rank for more keywords and demonstrate depth. But it means the structure of the article (headings, bullets, bold key phrases) affects “reading time” in practice. A well-structured 2,000-word article may take 4 minutes to skim the key points and 8 minutes to read fully. The displayed “9 min read” reflects the full reading time; many users will scan it in under 2 minutes.
Speed reading: what the research says
Speed reading courses and apps claim to triple or quadruple reading speed. The research is skeptical.
A 2016 review in Psychological Science in the Public Interest (Rayner et al.) concluded:
- Eye movement efficiency: professional speed reading courses may improve eye movement patterns slightly, but the gains are modest (10–30%)
- Peripheral text processing: humans cannot effectively process text in peripheral vision — claims that RSVP (Rapid Serial Visual Presentation) techniques allow faster reading with equal comprehension are not supported
- Comprehension-speed tradeoff: measured comprehension tests reliably show that reading speed above ~500 WPM comes with significant comprehension loss for most readers and most material
The exception: domain experts reading familiar material. A cardiologist reading a cardiology paper may read at 400+ WPM with full comprehension because they’re not encountering unfamiliar concepts — they’re mainly scanning for new data points within a known framework.
What affects individual reading speed
Vocabulary and domain knowledge
Encountering an unfamiliar word requires a pause. Encountering an unfamiliar concept requires a longer pause. This is why experts read their domain’s literature significantly faster than novices.
For content creators, this means your reading time estimate should account for your audience’s expertise level. A developer tutorial for beginners takes longer to read than the WPM estimate predicts; a quick-tips article for experts takes less time.
Subvocalization
Subvocalization is the habit of “hearing” words in your inner voice as you read. Most people do this. It caps reading speed at roughly speaking speed (~150 WPM) for readers who subvocalize every word.
Skilled readers subvocalize less — they recognize words and phrases as visual patterns rather than sound sequences. This is one genuinely trainable skill that improves reading speed without sacrificing comprehension.
Screen reading vs print
Research comparing screen and print reading finds screen reading is 20–30% slower on average, with lower comprehension scores for complex material. Proposed causes:
- Screen luminosity causes more eye strain
- Scrolling disrupts spatial memory (print readers know “where on the page” information was)
- Digital reading contexts trigger scanning behavior
For web content, readers are in “screen mode” — they’re scanning, not studying. This reinforces the value of structure (headings, bullets) over dense paragraphs.
WPM in content planning
Calculating reading time from word count
Reading time (minutes) = word count ÷ 225
Round up for technical content or content with code examples:
Adjusted reading time = (word count ÷ 225) × 1.3 // for code-heavy content
Target word counts for specific reading times
| Target time | Word count @ 225 WPM |
|---|---|
| 1 min | ~225 words |
| 3 min | ~675 words |
| 5 min | ~1,125 words |
| 7 min | ~1,575 words |
| 10 min | ~2,250 words |
| 15 min | ~3,375 words |
| 20 min | ~4,500 words |
For AdSense approval (the 20–30 article minimum of 1,500+ words each), aim for 7-minute reads — substantial enough to rank and demonstrate expertise, readable without being overwhelming.
WPM and podcast/video equivalents
When repurposing written content as audio/video:
| Format | WPM | 1,500 words = |
|---|---|---|
| Podcast (average speech) | 130–150 | ~10 minutes |
| Audiobook narration | 150–160 | ~10 minutes |
| YouTube (engaging presenter) | 140–160 | ~10 minutes |
| Video tutorial (deliberate pace) | 100–120 | ~13 minutes |
A 1,500-word blog post → ~10 minutes of audio content. This is the rough conversion rate for repurposing.
Practical use: the Word Counter on Xerobit
The Word Counter shows reading time in the metadata panel as you type. It updates in real time — you don’t need to count words manually or calculate reading time separately. Aim for the reading time matching your target (7 min for a standard blog post) rather than targeting a specific word count.
Related tools
- Word Counter — real-time word count and reading time
- Sentence Counter — optimize sentence length for readability
- Reading Time Calculator — how reading time estimates are calculated
Related posts
- Character Limits Cheatsheet: Every Limit That Matters for Developers — Meta titles, descriptions, Twitter, SMS, Open Graph, HTTP headers, SQL identifie…
- Character Counter — What It Counts and Why It Matters — Character count isn't just about Twitter limits. Email subject lines, SMS, SEO m…
- Letter Counter — Count Letters and Characters in Text — A letter counter tells you how many alphabetic characters are in your text, sepa…
- Reading Time Calculator — How Long Does It Take to Read Your Content? — Reading time calculators estimate how long it takes to read a piece of text. Her…
- Sentence Counter — How Sentence Length Affects Readability and SEO — Sentence counters do more than count. Learn how average sentence length, sentenc…
Related tool
Count words, characters, sentences, paragraphs, and lines. Reading time estimate, char-limit indicators for X, LinkedIn, meta titles, and more.
Written by Mian Ali Khalid. Part of the Dev Productivity pillar.