Speed reading gets talked about like a single number—words per minute (WPM). But in real life, reading faster only matters if you can still understand, remember, and apply what you read. The most effective way to improve is to treat speed reading as a skill you can measure: speed, comprehension, and focus, tracked consistently over time.
This guide shows a practical benchmarking system you can run on your iPhone or iPad (no special equipment required). You’ll learn which metrics matter, how to test yourself in 10 minutes, and how to build a routine that improves speed reading without sacrificing comprehension.
Why WPM alone is a weak measure of speed reading
WPM is useful, but it’s incomplete. Two people can both read at 450 WPM and have very different outcomes:
- One remembers the key ideas and can explain them.
- The other finishes quickly but misses nuance, arguments, and details.
For speed reading, the best benchmark is a balanced scorecard:
- Speed (WPM): how quickly you move through text.
- Comprehension (%): how well you understand immediately after reading.
- Retention (24-hour recall): what you can retrieve later without rereading.
- Focus (minutes without drifting): how stable your attention is.
Rule of thumb: If your WPM rises but comprehension drops below your acceptable threshold, you’re not improving—you're just accelerating past meaning.
Your core speed reading metrics (and simple targets)
Use these metrics as your baseline. Don’t worry about “perfect” numbers; what matters is trend.
1) Words per minute (WPM)
What it measures: raw reading speed.
How to track: time a passage and compute WPM.
2) Immediate comprehension score (%)
What it measures: what you understood right after reading.
How to track: answer a short set of questions (details + main idea + inference).
Practical target: many readers aim to keep comprehension at 70–85% while increasing speed, depending on the material.
3) Retention score (24-hour recall)
What it measures: whether speed reading is producing usable knowledge.
How to track: the next day, write 5 bullet points from memory: thesis, 2–3 key supports, and one actionable takeaway.
4) Focus stability (minutes)
What it measures: how long you can read before mind-wandering or checking your phone.
How to track: set a timer and mark the first time you notice drifting.
A 10-minute benchmark test you can repeat weekly
You can run this on iOS using any long-form article, PDF, or study text. Choose material that’s similar difficulty each week (ideally from the same source or domain) to keep comparisons fair.
- Pick a passage of ~800–1,200 words.
- Preview for 30 seconds: scan headings, first sentences, and any key terms.
- Read for 4 minutes at a pace that feels “challenging but controlled.”
- Stop at exactly 4 minutes and mark where you ended.
- Count words read (rough estimate is fine):
- If the text shows word count, use it.
- Otherwise, estimate: average words per line × lines read.
- Compute WPM (see formula below).
- Do a 2-minute comprehension check using the question templates below.
WPM formula
WPM = (words_read / minutes_spent)
Example: 1,000 words in 4 minutes = 250 WPM.
Comprehension questions (copy/paste templates)
Answer quickly from memory. Score 1 point each; convert to a percentage.
- Main idea: What is the author’s central claim in one sentence?
- Key support: Name two supporting points or examples.
- Definitions: Define one key term in your own words.
- Inference: What is implied but not stated directly?
- Application: How would you use this information in a real task?
How to set up a tracking log on iPhone or iPad
Use Notes, Numbers, Sheets, or a plain text file. Keep it simple so you actually maintain it.
Minimal log fields (recommended)
- Date
- Text type (article, textbook, PDF, report)
- Difficulty (Easy / Medium / Hard)
- Words read
- Minutes
- WPM
- Comprehension score (0–5)
- Focus drift time (minutes)
- One sentence: “What I learned”
Optional: a CSV template
If you like tracking in a spreadsheet later, paste this into a note and export:
Date,TextType,Difficulty,Words,Minutes,WPM,CompScore,FocusMinutes,Notes
Practice drills that improve speed reading (with measurable outcomes)
Not all drills fit every text. Use a small menu and rotate based on what you’re reading on iOS (articles vs. dense PDFs vs. research papers).
| Drill | Best for | Time | What to measure |
|---|---|---|---|
| Pointer pacing (finger/stylus) | Reducing regressions (backtracking) | 3–5 min | Higher WPM with stable comprehension |
| Chunking (2–4 words per fixation) | Most narrative and general nonfiction | 5 min | WPM + fewer “reread” moments |
| Preview → Read → Recall | Studying, technical content | 8–10 min | Comprehension + 24-hour retention |
| Controlled skimming (topic sentences) | Long articles, reports | 4–6 min | Main-idea accuracy |
| RSVP-style bursts (word-by-word) | Speed training and focus | 1–3 min | Peak WPM + focus stability |
Common measurement mistakes (and how to avoid them)
1) Testing on wildly different text difficulty
If Week 1 is a light blog post and Week 2 is a legal contract, your WPM comparison is meaningless. Use similar genres, or at least label difficulty and compare “like with like.”
2) Chasing peak WPM instead of sustainable WPM
A brief burst can produce exciting numbers, but your real benchmark is the pace you can sustain for 10–20 minutes with acceptable comprehension.
3) Ignoring comprehension drift
Many readers feel “fine” while losing understanding gradually. That’s why the short comprehension quiz matters. It catches hidden slippage.
4) Measuring while distracted
If notifications are on, your “reading speed” is partly “task switching speed.” For cleaner results, use Focus modes, silence alerts, and keep one reading session truly single-tasked.
iPhone and iPad setup for better speed reading sessions
Small environmental tweaks can improve focus stability and reduce visual fatigue—both of which improve speed reading outcomes.
- Use a consistent font size: too small increases strain; too large increases scrolling.
- Reduce glare: Night Shift/True Tone or a matte screen protector can help.
- Lock orientation if you’re frequently disrupted by rotation.
- Use split view intentionally (iPad): text on one side, notes on the other to support recall.
- Set a short timer: 8–12 minute reading blocks often beat “endless scrolling.”
What “good progress” looks like over 4 weeks
Progress in speed reading is usually stepwise: your brain adapts, then performance jumps. A realistic pattern:
- Week 1: establish baseline WPM and comprehension (no ego).
- Week 2: WPM rises slightly; comprehension may wobble.
- Week 3: comprehension recovers at the new speed; focus improves.
- Week 4: another small WPM increase while retention stays stable.
If your comprehension is falling week-to-week, slow the pace by 10–15% and emphasize Preview → Read → Recall for a week. The goal is a stable foundation, not a fragile high score.
How to choose the right speed reading mode for the task
Different reading goals require different strategies. Use this quick decision rule:
- Need deep understanding (study, contracts, research): moderate speed + frequent recall checkpoints.
- Need broad awareness (news, industry scans): faster skimming + main-idea testing.
- Need to extract facts (procedures, specs): selective reading + search + highlight key constraints.
Putting it all together: a weekly routine that sticks
Here’s a simple schedule that balances training and measurement without taking over your day:
- Once per week (10 minutes): run the benchmark test and log results.
- Three times per week (5–10 minutes): do one drill (pointer pacing, chunking, or RSVP-style bursts).
- Daily (optional, 2 minutes): write a one-sentence summary of what you read.
This works because you’re not relying on motivation; you’re relying on a small system. Over time, you’ll see which drills increase WPM without harming comprehension—and which texts require a slower, more deliberate pace.
Final note
If you prefer reading workflows that include timers, pacing modes, and distraction-reducing layouts on iOS, a speed reading app can make the tracking and practice loop easier—some readers use FocalRead for this—but the benchmarking method above works regardless of the tool you choose.
