Estimating Reading Time Accurately
Paste your content and this tool estimates how long it takes to read, using a words-per-minute rate you can adjust. It also shows speaking time at a presentation pace, plus the underlying word and sentence counts.
The default of 200 words per minute reflects a common average for adults reading online content of ordinary difficulty. That average hides a lot of variation, which is worth understanding before you publish a number on your page.
What affects real reading speed
Reading speed varies enormously by material and reader. Casual prose is read faster than technical documentation; a specialist reads their own field faster than a newcomer; and almost everyone reads more slowly on a phone than on a desktop.
Content type matters more than most estimates account for. A page dense with code samples, tables or formulas is not read at prose speed — readers stop, parse, and often re-read. If your content is technical, a lower words-per-minute setting gives a more honest number.
Scanning behaviour complicates it further. Most people do not read web pages linearly; they scan headings, skip to the section they need, and read that. For those readers the full-article estimate is meaningless, which is an argument for good headings rather than for a different calculation.
- 150–180 wpm — technical documentation, academic writing, dense reference material.
- 200–250 wpm — general web content, blog posts, marketing copy.
- 250–300 wpm — light fiction and casual reading.
- 130 wpm — comfortable speaking pace for presentations and scripts.
Why show reading time at all
A reading time estimate sets expectations before someone commits. Readers who know a piece is a three-minute read are more likely to start it than readers facing an unlabelled wall of text, and readers who know it is a fifteen-minute read can decide to save it rather than abandoning it halfway.
There is a credibility angle too. An accurate estimate signals that the publisher thought about the reader's time. An estimate that is obviously wrong — a two-minute label on a piece that takes ten — has the opposite effect.
It is not an SEO signal. Google does not read your displayed reading time or use it in ranking. Any indirect benefit comes through engagement: readers who know what they are committing to are less likely to bounce immediately.
Speaking time for scripts
The speaking estimate uses 130 words per minute, which is a comfortable pace for a presentation or voiceover. Conversational speech runs faster, around 150 to 160, and deliberate narration slower, around 110 to 120.
Scripts need more slack than reading estimates. Pauses, emphasis, and the fact that almost everyone speaks faster when nervous mean a script timed exactly to a slot usually overruns in rehearsal and rushes in delivery. Writing to roughly 90% of your available time is the safer approach.
If you are writing to a hard time limit, the Word Counter gives you the raw word target to work backwards from — a five-minute segment at 130 wpm is about 650 words.
Reading time and content length decisions
The estimate is a useful sanity check on structure. A twelve-minute article is not too long in itself, but it does need headings, and probably a summary or contents list at the top. A two-minute article competing against ten-minute ones may simply be under-covering the topic.
Neither observation is about hitting a word count. Length should follow from the subject, and word count is not a ranking factor. What the estimate gives you is a reader's-eye view of the commitment you are asking for, which sometimes prompts a useful edit.
If the number feels higher than the content justifies, the Word Counter and its average-words-per-sentence figure will usually show why — long sentences and padding inflate both length and reading difficulty at once.
How the calculation works
Word count divided by your chosen words-per-minute rate, rounded to the nearest minute with a one-minute floor. Words are counted by splitting on whitespace, the same method most editors use.
It deliberately ignores images, videos and embedded elements. Some estimators add fixed seconds per image, but the right amount varies from zero for decoration to a minute for a chart someone actually studies, so a fixed adjustment adds noise rather than accuracy.
Everything runs in your browser. Nothing you paste is transmitted or stored.
Frequently asked questions
What words-per-minute rate should I use?
200 is a reasonable default for general web content. Drop to 150–180 for technical or reference material, and raise to 250 for light casual reading. Match the rate to how demanding your content actually is.
Does reading time affect SEO?
Not directly — Google does not read or rank on your displayed reading time. Any benefit is indirect, through readers who know what they are committing to being less likely to bounce immediately.
Should images count toward reading time?
This tool ignores them deliberately. Time spent on an image ranges from zero for decoration to a minute for a chart worth studying, so any fixed per-image adjustment adds inaccuracy rather than removing it.
Why is speaking time longer than reading time?
People read faster than they speak. The defaults here are 200 words per minute for reading and 130 for speaking, which is a comfortable presentation pace allowing for pauses and emphasis.
How accurate is the estimate?
It is a reasonable average, not a measurement. Actual time varies with reader familiarity, content difficulty, device and whether someone reads linearly or scans. Treat it as a rough expectation-setter.