How long does it take to read this?
Reading time is the most-asked question on every blog page now. Medium pioneered the "X min read" badge in 2014, and within five years it was on every CMS, newsletter, and SaaS landing page. The reason it spread is simple: readers decide whether to engage based on time cost, and showing the cost up front improves both engagement and post-read satisfaction.
But the math is less settled than the badge suggests. "Average reading speed" is a number everyone quotes and almost no one defends.
The 250 WPM number
The widely-cited 250 words per minute average comes from research on adult silent reading of moderately complex prose on screen. It's a real number from real studies, but it's an average across a wide range. Individual readers cluster anywhere from 175 to 350 WPM at the same skill level. Material complexity adds another layer: dense academic prose runs slower (180–220 WPM) and skim reading runs faster (300+ WPM).
Treat 250 WPM as a useful default, not a precise number. If you publish a "5 min read" badge based on 250 WPM, expect actual readers to land anywhere from 4 to 7 minutes.
Pick the pace your audience matches
The audience profiles on this tool are calibrated to research on real reader cohorts:
- Children (8 to 12): 150 WPM. Elementary-school silent reading studies.
- Casual reader: 200 WPM. Slow, deliberate prose reading. Use for non-native English speakers and unfamiliar topics.
- Adult average: 250 WPM. The standard "X min read" baseline.
- College or professional: 280 WPM. Trained on dense material.
- Skim reader: 350 WPM. Eye-jumping reading, low retention.
- Speed reader: 500 WPM. Trained speed-reading techniques. Comprehension drops sharply above this.
If you publish technical content, lean toward 200 WPM. If you publish for general audiences, 250 is right. If your readers are experts in your topic, 280 is closer.
Speaking is roughly half the speed of reading
When the same text is read aloud, words come out about half as fast as silent reading. Conversational pace runs around 130 words per minute. Podcast hosts and audiobook narrators average 150–160. Keynote speakers slow further to 100–110, because audiences need time to absorb new ideas without the ability to back up.
This is why a written speech of 1,500 words takes 6 minutes to read silently but 12 minutes to deliver. Politicians and TED speakers learn this fast. Read your draft out loud once before you commit to a runtime.
Skip code and quotes from the count
For technical content with code blocks, skip the code from the word count. Readers don't parse code at the same speed as prose. Code is scanned and the eye returns multiple times. Block quotes have a similar pattern: readers reread quoted passages more than the surrounding text.
Most CMS reading-time plugins skip code blocks automatically. If you're calculating manually, copy the prose only.
Why the estimate matters more than the number
The "X min read" badge isn't really about precision. It's about sorting. Readers use it to triage: short reads get clicks now, long reads get bookmarks for later. Getting the bucket right (1-min, 3-min, 7-min, 15-min) matters more than getting the exact minute right.
Round generously and stay honest. A 6-minute read labeled "5 min" feels like a small lie. A 6-minute read labeled "6 min" feels accurate. A 6-minute read labeled "7 min" actually performs better. Readers feel pleasantly surprised when it ends a minute early.