SReader Reading Notes
A Two-Week Self-Test for Any New Reading Method
A two-week protocol for testing any reading method on your own material: baseline week, matched texts, comprehension checks, and decision rules.
How to Test a Reading Technique: A Two-Week Self-Trial Protocol
Most readers who cycle through reading methods don't have a technique problem. They have an evidence problem. One month it's a rapid-serial-visual-presentation (RSVP) app, the next a focal-point mode, then guided highlighting. Each one gets adopted on the strength of a promise and quietly abandoned when the promise doesn't hold. The hopping itself is what wears you down: every restart costs momentum, and none of the attempts tells you anything reliable about what actually works for you.
The honest answer, including to the broader question of whether speed reading actually works, is to stop trusting claims and run a controlled two-week trial on your own material. Learning how to test a reading technique takes one short experiment, and the protocol below is technique-agnostic: it works identically for pacing, RSVP, focal-point reading, and guided highlighting, because it holds the reader and the conditions constant and lets the technique prove itself.
The structure is simple. Week one is a baseline of normal reading. Week two applies the new technique to matched texts. Simple self-checks measure focus, comprehension, and completion, and a decision rule at the end tells you to keep, adjust, or drop. If you want an instrument that keeps the trial quiet, SReader runs focal-point and pace-adjustable reading across EPUB, PDF, Markdown, text files, and saved web articles entirely on your device.
What normal reading speed actually is
Set expectations before you test anything, because the claims you'll be measuring against are often unrealistic. A meta-analysis of 190 studies with 18,573 participants concluded: "Based on the analysis of 190 studies (18,573 participants), we estimate that the average silent reading rate for adults in English is 238 words per minute (wpm) for non-fiction and 260 wpm for fiction." Most adults fall between 175 and 300 wpm for non-fiction and between 200 and 320 wpm for fiction.
Against those numbers, a method promising to double or triple your speed deserves scrutiny. The same research review finds a hard ceiling: "It is unlikely that readers will be able to double or triple their reading speeds (e.g., from around 250 to 500-750 words per minute) while still being able to understand the text as well as if they read at normal speed." The mechanisms behind the boldest claims are also weaker than advertised. A review of the speed-reading evidence reaches the blunt conclusion that speed-reading promises are too good to be true.
The evidence-backed route to faster reading with comprehension intact is less dramatic: more reading, which builds the vocabulary and language skill that genuinely raise speed. If you've already bounced off a few of these apps, the pattern will look familiar. For the trial, write 238 wpm and 260 wpm into your tracking sheet as reference lines. You are not trying to beat them, just comparing yourself against a documented average.
The two-week protocol at a glance
The whole experiment fits in one view:
- Week one, baseline. Read normally. No new tools, no new habits. Record focus, comprehension, and completion for every session.
- Week two, technique. Apply one technique in every session, on texts matched to week one, with the same total reading time and session count.
- Decision gate. Put the two sheets side by side and apply the keep, adjust, or drop rules.
Matched texts are the single most important control: same genre, similar length, similar difficulty in both weeks. The three outcomes are measurable, not impressionistic: focus, comprehension, and completion. And everything runs on material you actually read, whether that's EPUBs, PDFs, Markdown notes, or saved web articles.
Week one: measure your baseline
Read your usual material at your usual pace. The baseline must reflect real habits, not best behavior, or week two will look better than it is. After each session, log four focus numbers: minutes before the first distraction, count of self-interruptions, rereads per page, and a 1-to-5 overwhelm score. Together these turn the vague goal to improve reading focus into something you can count.
Track completion the same way: sessions finished versus abandoned, and pages or articles completed. Run the comprehension self-checks described below identically in both weeks, and optionally log rough words per minute so you can compare yourself against the 238 wpm average.
Week two: matched texts, timed sessions, one technique
The discipline in week two is matching. Choose texts in the same genre as your week-one material, with similar length and difficulty. Hold total reading time and session count identical to the baseline week. Apply the technique consistently in every session rather than mixing methods, because a blend of techniques tells you nothing about any of them.
Run the identical focus and comprehension checks after each session. SReader is a natural instrument for this week: focal-point and pace-adjustable reading across EPUB, PDF, Markdown, text, and web articles, local-first with no account, so your trial data never leaves your device. If you want the reasoning behind pacing controls, the research on pace-controlled reading and comprehension covers it in more depth.
The five-minute reading comprehension self-test
You don't need formal quizzes or an external assessment service. A lightweight reading comprehension self-test has three parts, each taking a couple of minutes:
- Immediate free recall. After each session, write down five things you remember from the text, without looking back.
- One-sentence main argument. Capture the piece's central claim in a single line. A vague summary is a red flag.
- 24-hour delayed recall. The next day, before rereading anything, list what stuck.
This borrows from learning research rather than inventing its own measurement. The immediate and delayed recall checks are small versions of two standard study techniques: retrieval right after the session, and a spaced check the next day. Scoring must be identical across both weeks, including the day-after timing, and everything stays on paper or in your notes. Nothing needs to be uploaded anywhere. The same retrieval-practice approach scales up if you read dense technical material.
The fill-in tracking sheet
Copy this structure for both weeks. Identical columns make the comparison mechanical instead of impressionistic.
Group | Columns to fill in |
|---|---|
Session | Date, text title, genre, minutes read, rough WPM |
Focus | Minutes to first distraction, self-interruptions, rereads per page, overwhelm score (1-5) |
Comprehension | Your three self-check scores, logged the same way in both weeks |
Completion | Finished, partially finished, or abandoned |
Keep the scoring rules simple and hold them constant: one point per item in free recall, yes or no on the main argument, and 0-to-5 on delayed recall. Keep the sheet analog or in your notes app. A no-account, no-cloud log suits a two-week trial, and it keeps the experiment as quiet as the reading.
Why feelings lie
Two biases can quietly corrupt a do-it-yourself reading experiment. The first is the placebo effect: novelty alone boosts focus, so a new app feels like progress for a week regardless of merit. The second is practice-curve bias: week-two gains may simply come from growing familiarity with the texts or with reading generally.
The matched-texts design, same genre, length, and difficulty, is the main defense against the second bias. Against the first, trust the recall scores over the vibe. If the results are borderline, run a short second trial with fresh matched texts before deciding. The sheet exists precisely so that numbers, not enthusiasm, carry the verdict.
The verdict: keep, adjust, or drop
Apply the rules to the data, not to your memory of the fortnight:
- Keep if comprehension holds or improves and at least one focus metric or completion clearly improves.
- Adjust if focus improves but comprehension drops.
- Drop if comprehension falls with no focus gain, or if the gains evaporate once the novelty wears off.
A worked example: a reader using pacing finishes every session faster and reports fewer distractions, but free recall falls from 4 out of 5 to 2 out of 5. The verdict is adjust, not keep. Slow the pace, pick two fresh matched texts, and rerun the checks before letting the technique into daily reading.
Whatever the verdict, the compounding path stays open. More reading builds the vocabulary and language skill that genuinely raise speed with comprehension intact, and a technique only earns its place if it helps you do more of that reading with your attention intact. Try SReader for your technique week: focal-point and pace-adjustable reading, local-first, with no ads, no feed, and no account in the way.