Estimate reading time by dividing the word count by 200 words per minute, then round up. A 900-word article becomes about 4.5 minutes, so the label should read 5 min read.
That formula is enough for most blog posts. Adjust it only when the page contains code, diagrams, forms, or dense instructions that slow the reader down.
The Word Counter calculates reading time from pasted text, so you can check the label after every edit.
The basic formula
Use this calculation:
reading time = word count / words per minuteA common web-writing baseline is 200 words per minute. It is not exact for every reader, but it gives a consistent label that is clear to readers.
Examples:
| Word count | Estimate at 200 wpm | Display label |
|---|---|---|
| 400 | 2 minutes | 2 min read |
| 750 | 3.75 minutes | 4 min read |
| 1,200 | 6 minutes | 6 min read |
| 1,900 | 9.5 minutes | 10 min read |
Round to the nearest minute or round up. Rounding up is safer when the page has examples, screenshots, or steps the reader may pause over.
Pick a words-per-minute value
The right divisor depends on the kind of page.
| Content type | Suggested baseline |
|---|---|
| General blog post | 200 wpm |
| Light newsletter or announcement | 225 wpm |
| Technical guide with code | 160-180 wpm |
| Dense legal or policy text | 150-180 wpm |
| Transcript or speech script | 130-160 wpm spoken aloud |
Do not change the baseline from post to post without a reason. Readers learn what your labels mean. A site-wide rule keeps the estimate predictable.
Add time for things that are not plain text
Word count misses anything the reader has to inspect.
Add a small buffer for:
- Code blocks the reader may copy or compare.
- Charts, tables, screenshots, and diagrams.
- Step-by-step instructions.
- Embedded demos or forms.
- Equations or configuration examples.
For a normal article with 2 screenshots, rounding up may be enough. For a tutorial with 8 code blocks, a lower words-per-minute value is more honest.
Example: calculate a post label
Suppose a draft has:
1,340words- 3 screenshots
- 1 short code block
At 200 wpm:
1340 / 200 = 6.7 minutesRound that to 7 min read. The screenshots and code block already make rounding up sensible. If the code block were long or central to the task, use 180 wpm instead:
1340 / 180 = 7.4 minutesThat would still display as 7 min read or 8 min read, depending on how cautious you want the label to be.
Where to show reading time
Put the label near the title, date, or author line. Readers look there before deciding whether to start.
Use short labels:
4 min readAbout 6 minutesReading time: 5 min
Avoid long explanations in the metadata row. If the method matters, document it in your editorial system, not beside every article.
Update the label after editing
Reading time changes when you cut sections, add examples, or rewrite an introduction. Check it after the final edit, not only when the draft is first written.
This matters in static sites because reading time can live in frontmatter:
readTime: "6 min"If the field is stale, the page gives readers the wrong expectation before they begin.
Reading time is a planning tool
Reading time does not measure quality. A 3-minute post can be thin, and a 10-minute guide can be worth finishing.
Use the number to set expectations. If a page claims 3 min read, the answer should arrive quickly. If it claims 12 min read, the structure should give readers enough headings, examples, and checkpoints to stay oriented.
Estimate the time, round honestly, then make the page earn the attention it asks for.
