Reading Time Calculator for Blog Posts: Formula and JavaScript

A reading time calculator for blog posts uses one simple formula: word count divided by reading speed in words per minute. Medium uses 265 WPM, Google's own reference standard is 200 WPM, and most implementations land somewhere in the 200-250 range for general web content.

Displaying reading time isn't just a nice-to-have. Research shows it can increase engagement by 30%, since readers can decide whether they have time to commit before they start.

Here's the exact formula, real working JavaScript, and the adjustments that make an estimate meaningfully more accurate than a bare word-count division.

01The Reading Time Formula

The base formula behind every reading time calculator is straightforward: Reading Time = Word Count ÷ Words Per Minute. A 1,000-word article at 200 WPM comes out to 5 minutes.

The WPM value you pick matters more than it seems. Medium uses 265 WPM, general web standards range from 200-250, and Google's own reference point is 200 WPM. Technical or dense content should use a slower estimate, since research shows comprehension drops significantly above 300 WPM.

02Basic Working JavaScript

Here's the simplest working version: grab the article text, split it into words, divide by WPM, and round up so a reader is never disappointed by an underestimate.

function calculateReadingTime(text, wpm = 238) {
  const words = text.trim().split(/\s+/).length;
  const minutes = Math.ceil(words / wpm);
  return minutes;
}

// Usage
const articleText = document.querySelector('.article-content').innerText;
const readTime = calculateReadingTime(articleText);
document.getElementById('reading-time').innerText = `${readTime} min read`;

03Accounting for Images: The Part Most Calculators Skip

Word count alone understates total engagement time for heavily illustrated content. Each image adds roughly 12-20 seconds of viewing time, decreasing slightly for each additional image as readers skim faster through a gallery. Complex tables or figures can add 30-60+ seconds for real comprehension.

function calculateReadingTimeWithImages(text, imageCount, wpm = 265) {
  const words = text.trim().split(/\s+/).length;
  const wordMinutes = words / wpm;

  // First image adds 12s, decreasing by 1s per image down to a 3s floor
  let imageSeconds = 0;
  for (let i = 0; i < imageCount; i++) {
    imageSeconds += Math.max(12 - i, 3);
  }

  const totalMinutes = wordMinutes + (imageSeconds / 60);
  return Math.ceil(totalMinutes);
}

// Example: 1,500 words, 5 images, 265 WPM ≈ 6-7 min read
const readTime = calculateReadingTimeWithImages(articleText, 5);

04Auto-Detecting Word Count and Images From the DOM

Rather than hardcoding values, scan the actual rendered article container so the estimate updates automatically whenever content changes, no manual recalculation required.

function autoReadingTime(containerSelector, wpm = 238) {
  const container = document.querySelector(containerSelector);
  if (!container) return null;

  const text = container.innerText || container.textContent;
  const words = text.trim().split(/\s+/).filter(Boolean).length;
  const images = container.querySelectorAll('img').length;

  const wordMinutes = words / wpm;
  let imageSeconds = 0;
  for (let i = 0; i < images; i++) {
    imageSeconds += Math.max(12 - i, 3);
  }

  const totalMinutes = Math.ceil(wordMinutes + imageSeconds / 60);

  return {
    minutes: totalMinutes,
    words: words,
    images: images,
    label: totalMinutes < 1 ? 'Less than a minute' : `${totalMinutes} min read`
  };
}

const result = autoReadingTime('.article-content');
document.getElementById('reading-time').innerText = result.label;

05Reading Speed Reference by Content Type

Different content types genuinely need different WPM assumptions for an accurate estimate.

06Try It: Reading Time Estimator

Enter a word count and pick a reading speed to see the estimate update live.

07Implementation Best Practices

A short list for getting reading time estimates right.

08Common Questions