title: "Why Words-Per-Minute Is a Terrible Metric (And What to Track Instead)"

slug: why-wpm-is-terrible-metric

meta_description: "WPM ignores the only thing that matters — whether you understood what you read. Here's the case for Effective Reading Rate and why it changes everything."

primary_keyword: words per minute reading metric

secondary_keywords: effective reading rate, reading comprehension speed, speed reading metrics

Why Words-Per-Minute Is a Terrible Metric (And What to Track Instead)

Here's a question nobody in the speed reading industry wants you to ask: what did you actually remember?

Every speed reading app, course, and YouTube guru leads with the same number — words per minute. "Read 800 WPM!" "Double your WPM in 30 days!" It's the universal scoreboard. And it's deeply misleading.

WPM tells you how fast your eyes moved across text. It tells you nothing about whether your brain did anything useful with the information. And in any context where reading actually matters — work, study, research, professional development — the brain part is the whole point.

The WPM Illusion

Imagine two people read the same 3,000-word report.

Reader A finishes in 6 minutes at 500 WPM. When asked about the three key recommendations in the report, she can name one and vaguely recalls another. Comprehension: roughly 40%.

Reader B finishes in 10 minutes at 300 WPM. She can summarize all three recommendations, explain the supporting data, and identify a flaw in the methodology. Comprehension: roughly 90%.

By the WPM scoreboard, Reader A "wins." In reality, Reader A will need to re-read the report — probably more than once — before she can act on it. Reader B is already done.

This isn't a hypothetical edge case. It's the normal outcome when you optimize for speed without measuring comprehension. Research by Rayner et al. (2016) documented this trade-off extensively: as reading speed increases beyond a reader's effective range, comprehension drops — sometimes precipitously. The relationship isn't linear. You don't lose 10% comprehension for every 10% speed gain. At a certain threshold, comprehension falls off a cliff.

Why the Industry Loves WPM Anyway

WPM persists because it's simple, it's impressive, and it's trivial to game.

It's simple. One number. Straightforward to measure, compare, and put on a marketing page. "You went from 250 to 600 WPM!" feels concrete and satisfying.

It's impressive. High WPM numbers trigger the same psychology as any leaderboard. People want to see their number go up. Speed reading apps know this — many are essentially gamified WPM trackers.

It's trivial to game. Most WPM measurements don't include comprehension testing. The ones that do often use trivial recall questions (multiple choice with obvious wrong answers) that can be passed with surface-level skimming. A reader who processed 30% of the text can often pass these "comprehension checks" at 80%+.

The result: people genuinely believe they're reading faster and understanding what they read, because the metrics told them so. The metrics were just measuring the wrong thing.

The Comprehension Tax

Here's what WPM-obsessed reading actually costs you in practice.

Re-reading time. If you read a report at 600 WPM and retain 35%, you're going to read parts of it again. Maybe the whole thing. That re-reading time often exceeds what you "saved" by going fast the first time.

Shallow processing. Speed without comprehension means information enters working memory and exits without consolidating into long-term memory. You read it, you "knew" it for 90 seconds, and it's gone. For anyone reading to learn or to make decisions, this is the core failure mode.

False confidence. You finished the article. You feel informed. You're not. This is arguably worse than not reading it at all, because at least then you'd know you didn't have the information.

Decision quality. Knowledge workers don't read for entertainment (well, not during work hours). They read to inform decisions. Comprehension isn't a nice-to-have — it's the entire value proposition of reading. A metric that ignores it is like evaluating a surgeon by how fast they operate.

Effective Reading Rate: The Metric That Actually Matters

The fix is straightforward. Multiply speed by comprehension.

Effective Reading Rate (ERR) = WPM × Comprehension %

This single adjustment transforms how you think about reading performance.

Consider our two readers again:

• Reader A: 500 WPM × 0.40 = ERR of 200
• Reader B: 300 WPM × 0.90 = ERR of 270

Reader B isn't just "better at comprehension." She's measurably more efficient overall. She extracts more usable information per minute of reading time.

ERR also reveals something counterintuitive: slowing down can improve your score. If dropping from 400 WPM to 350 WPM raises your comprehension from 60% to 85%, your ERR jumps from 240 to 297. You're reading "slower" and performing significantly better.

This is the insight that most speed reading programs either miss or deliberately ignore, because "read a bit slower and understand more" doesn't sell courses.

What Changes When You Track ERR

You find your real speed ceiling

Everyone has a speed at which comprehension starts to degrade significantly. This varies by person, by material difficulty, and by familiarity with the topic. ERR helps you find that ceiling empirically rather than guessing. Your optimal reading speed is the one that maximizes ERR — not the fastest speed you can technically achieve.

You match technique to material

Not everything should be read at the same speed. An email newsletter and a technical specification require different approaches. ERR tracking across different content types reveals where you can afford to skim and where careful reading pays for itself.

When you're reading a familiar blog post in your field, skimming at 600 WPM with 50% comprehension (ERR: 300) might be perfectly appropriate — you're catching what's new and skipping what you already know. When you're reading a contract or a research methodology, slowing to 200 WPM with 95% comprehension (ERR: 190) is the right call, even though the number looks "worse."

ERR gives you permission to be strategic instead of trying to go fast all the time.

You stop chasing vanity numbers

Once you're tracking ERR, the temptation to inflate your WPM disappears. You can't cheat the metric without actually getting better at processing text, because comprehension is baked into the score. This shifts your training from "go faster" to "get more efficient" — which is what you actually wanted in the first place.

You measure real improvement over time

ERR trends over weeks and months show genuine skill development. A reader whose ERR climbs from 200 to 280 has meaningfully improved their reading ability. A reader whose WPM climbed from 300 to 500 might have improved, or might have just learned to move their eyes faster while absorbing less. Without comprehension in the equation, you can't tell.

How to Measure Comprehension (Without It Being Annoying)

The practical objection to ERR is fair: measuring comprehension adds friction. Nobody wants to take a quiz after every article.

Good comprehension measurement doesn't require a formal test every time. There are several approaches that work:

Periodic calibration. Test comprehension in structured practice sessions — say, three times a week — and use those sessions to establish your speed-comprehension curve. Apply those findings to your regular reading.

Active recall checks. After reading, spend 30 seconds trying to articulate the main points without looking back. If you can, your comprehension was adequate. If you can't, you were going too fast.

Purpose-based assessment. Define what you need from the text before you read it. After reading, check whether you got it. This is how comprehension works in practice — you're not trying to memorize every sentence; you're trying to extract specific value.

Adaptive tracking. This is where software helps. An app can present comprehension questions at intervals, calibrate difficulty to your level, and calculate ERR automatically — turning what would be tedious manual tracking into a background process.

What We Built at Lumen

Lumen tracks ERR as its primary performance metric. Every practice session measures both speed and comprehension, and your dashboard shows ERR trends over time, not just a WPM number.

We built it this way because the alternative — another WPM leaderboard — would have made a product that feels good to use but doesn't actually help you read better. That trade-off wasn't worth making.

The app also adapts to context. When you practice with RSVP or Chunking exercises, Lumen adjusts difficulty based on your ERR at that technique, not your raw speed. When your comprehension drops below a threshold, the app slows down. When it's consistently high, it pushes you faster. The goal is always to expand your efficient reading range — not to inflate a number.

Your reading speed matters less than your reading efficiency. Lumen measures both. [Start tracking your real reading performance at lumenspeeds.com](https://lumenspeeds.com).

Related reads