How to Calculate Reading Time for Your Content (And Why It Matter)?

You've seen it everywhere — Medium shows '5 min read' at the top of every article. LinkedIn previews reading time before you click. Email subject lines sometimes include '2-minute read' to boost open rates.

Reading time has become a fundamental piece of content metadata. But how is it calculated, what does it actually mean for your content strategy, and how can you use it to improve your writing? Let's dig in.

What Is Reading Time?

Reading time is an estimate of how long it will take an average person to read a piece of content from start to finish. It's typically displayed as '5 min read' or '8-minute read'.

The standard assumption is an average reading speed of 200–250 words per minute (WPM) for adults reading for comprehension. Some tools use 200 WPM to be conservative; others use 238 WPM (the oft-cited research average). Medium uses 265 WPM. The exact number varies by source, but 200–250 WPM is the safe range for general audiences.

The Simple Formula Behind Reading Time

The basic calculation is straightforward:

 1Reading Time (minutes) = Total Word Count ÷ Reading Speed (WPM)
 2
 3Example:
 4  1,200 words ÷ 200 WPM = 6 minutes
 5  1,200 words ÷ 238 WPM = ~5 minutes

Most implementations round up to the nearest minute so you never show '0 min read' for short content. A post with 150 words at 200 WPM = 45 seconds, which rounds up to '1 min read'.

Why Reading Time Matters

1. Sets Reader Expectations

When you tell readers upfront how long an article takes, they can decide whether they have time to read it now or save it for later. Articles without reading time estimates have higher abandonment rates — readers feel deceived when a '5 paragraph post' turns into a 20-minute deep dive.

2. Affects SEO Engagement Signals

Google indirectly uses engagement signals like time-on-page and scroll depth. When a 4-minute article actually takes 4 minutes to read, readers who intend to read the full piece are more likely to stay. Mismatched reading time expectations = short sessions = worse rankings.

3. Email Marketing Open Rates

Emails with '2-minute read' in the subject line or preview text can see 10–30% higher open rates in some segments. Readers are more likely to open something they know fits into a commute or coffee break.

4. Platform Optimization

Different platforms reward different content lengths:

• LinkedIn: 1,500–2,000 words (~7–10 min) performs best for thought leadership
• Medium: 7 minutes is the optimal length for maximum reads (per Medium's own data)
• Blog posts targeting informational keywords: 1,500–2,500 words
• News articles and updates: 300–600 words
• Tutorials and guides: 2,000–5,000 words

How to Calculate Reading Time for Different Content Types

Standard Blog Post

 1Words: 1,500
 2Reading speed: 200 WPM
 3Reading time: 1,500 ÷ 200 = 7.5 → round up = 8 min read

Content With Code Blocks

Code blocks slow readers down significantly. A reader spending time understanding a code example is not reading at 200 WPM — they might process 30–50 lines per minute. Advanced reading time calculators add extra time for code. A common approximation: add 30 seconds per code block, or count each line of code as 5 words.

Content With Images

Images add an estimated 12 seconds each to reading time. An article with 8 images would add about 1.5 minutes. Most simple reading time tools ignore images; more sophisticated ones account for them.

How to Add Reading Time to Your Website

JavaScript (Vanilla)

 1function getReadingTime(text, wpm = 200) {
 2  const words = text.trim().split(/\s+/).length;
 3  const minutes = Math.ceil(words / wpm);
 4  return `${minutes} min read`;
 5}
 6
 7// Usage
 8const articleText = document.querySelector('article').innerText;
 9const readingTime = getReadingTime(articleText);
10document.getElementById('reading-time').textContent = readingTime;

React / Next.js

 1// utils/readingTime.ts
 2export function getReadingTime(content: string, wpm = 200): string {
 3  // Strip HTML tags if content is HTML
 4  const text = content.replace(/<[^>]+>/g, ' ');
 5  const words = text.trim().split(/\s+/).filter(Boolean).length;
 6  const minutes = Math.ceil(words / wpm);
 7  return `${minutes} min read`;
 8}
 9
10// In your blog post component:
11const readingTime = getReadingTime(post.body); // or post.wordCount / 200

Python

 1import re
 2import math
 3
 4def get_reading_time(text: str, wpm: int = 200) -> str:
 5    # Strip HTML if needed
 6    clean = re.sub(r'<[^>]+>', ' ', text)
 7    word_count = len(clean.split())
 8    minutes = math.ceil(word_count / wpm)
 9    return f"{minutes} min read"
10
11# Usage
12with open("article.txt") as f:
13    print(get_reading_time(f.read()))  # e.g. "6 min read"

WordPress

Use the built-in reading time feature (available in the block editor/Gutenberg via Post Settings sidebar), or install a plugin like 'Reading Time WP'. You can also add custom code to your theme's functions.php if you want full control over the WPM setting.

What Reading Speed Should You Use?

The choice of WPM affects your estimate significantly:

• 200 WPM — conservative, good for technical or dense content (developer documentation, legal text)
• 238 WPM — research average for adults reading for comprehension
• 265 WPM — used by Medium, good for general blog content
• 300 WPM — optimistic, better for skimmable listicles

For most blog content, 200–238 WPM is the safest choice. If your content is highly technical (lots of code, data, or jargon), use a lower WPM.

Interpreting Reading Time — What's Too Short or Too Long?

• Under 1 min — Too short for a blog post. Expand it or reconsider the format (maybe it's a tweet, not a post).
• 1–3 min — Good for news updates, announcements, short tutorials.
• 4–7 min — The sweet spot for most blog posts. Long enough to be substantive, short enough to finish.
• 8–15 min — Comprehensive guides, comparisons, tutorials. Good for SEO if depth is warranted.
• 15+ min — Long-form cornerstone content, whitepapers, deep dives. Only use when the topic genuinely requires it.

Frequently Asked Questions

Does reading time affect Google rankings?

Not directly — Google doesn't have a 'reading time' ranking factor. But it affects engagement signals like time-on-page, scroll depth, and bounce rate, which Google does use indirectly. Long, low-quality content will hurt you. Long, high-quality content that matches user intent will help.

Should I aim for a specific word count?

Word count by itself doesn't determine rankings. What matters is covering the topic comprehensively for the target keyword. For competitive informational keywords, longer content (1,500–2,500 words) tends to rank better because it covers more angles. For navigational or transactional queries, shorter is often better.

How do I count words in different content formats?

For HTML pages, strip tags first then count. For Markdown, remove syntax characters. For PDFs, copy-paste to a text editor. Or — easiest of all — use the online tool below which handles all formats automatically.

Is there a difference between reading time and speaking time?

Yes — significantly. Average reading speed is 200–250 WPM, but average speaking speed for a presentation is 130–150 WPM. So a 1,500-word blog post takes about 7 minutes to read but 10–12 minutes to deliver as a talk. If you're converting a blog post into a video script or presentation, factor in the difference.

Wrapping Up

Reading time is a small detail that makes a real difference. It sets clear expectations, improves engagement, signals content depth, and helps readers decide when and whether to read. Calculating it correctly takes 10 seconds with the right tool.