Why Do I Read So Slowly? 6 Causes (and What Fixes Each)

If you feel like you read slowly, check the benchmark first: the average adult reads non-fiction at about 238 words per minute, per Brysbaert's 2019 meta-analysis of 190 studies. A large share of people who call themselves slow readers turn out, when measured, to be average. Among the genuinely slow, the cause is almost always one of six specific habits — and which one you have determines which fix actually works.

That's the whole article in three sentences: measure first, then match the fix to the cause. Generic advice — read more, use your finger, silence your inner voice — fails because it treats six different problems as one. Four of the causes below respond to mechanical training. One responds only to time spent in a subject. And one isn't a problem at all.

The measuring part takes two minutes on our free reading speed test, which scores comprehension alongside speed — because a WPM number without a comprehension check is a skimming score wearing a lab coat.

Measure before you diagnose — free 2-minute test →

First: are you actually slow?

Brysbaert's meta-analysis — the most careful estimate available — puts adult silent reading at about 238 WPM for non-fiction and about 260 WPM for fiction, with technical material slower still. Those numbers surprise people in both directions. Readers who feel slow often turn out to be at or just below that average when they actually measure — they were comparing themselves against figures from speed-reading marketing that never had a comprehension check behind them. We unpack where the inflated numbers come from in the average reading speed piece.

And feelings are a terrible instrument here. Reading speed feels like effort, so hard material makes you feel slow even when your pace on ordinary text is perfectly normal. The only way to know is to time yourself on a standard passage and answer questions about it afterward.

To make the stakes concrete, an illustration: a 10,000-word chapter takes about 67 minutes at 150 WPM and about 42 minutes at 238 WPM. That 25-minute gap, repeated across everything you read for the rest of your life, is why this question deserves an honest answer instead of a comforting one.

So: get a number with a comprehension score attached, then find your cause below. Most people recognize theirs within a paragraph.

Cause 1: your eyes keep jumping back

The symptom: you finish a sentence and your eyes snap back to the previous line — not because you missed anything, but because it feels safer to check. Eye-movement research puts these backward jumps, called regressions, at roughly 10-15% of all eye movements during normal reading (Rayner and colleagues' 2016 review). Some regressions are legitimate: a sentence that led you down the wrong parsing path deserves a second look. The habitual kind is different — insurance you keep paying on a claim you never file. You understood the line the first time. You go back anyway.

The fix: a pacer. A finger, a pen, or a cursor moving steadily forward under the line turns regression into a deliberate act instead of a reflex — you have to consciously abandon the pacer to jump back, and mostly you won't. The lower-tech alternative is an index card held above the line you just read (above, not below — the point is to block the return path, not to preview what's coming). Of everything in this article, this fix has the best effort-to-payoff ratio.

Cause 2: the voice in your head sets the speed limit

The symptom: you hear every word as you read, and your silent pace sits suspiciously close to the pace you'd read aloud. That's subvocalization — the inner voice most adults carry over from being taught to read out loud — and as long as it insists on fully pronouncing every word, it caps your reading near speaking pace.

The fix: gentle overspeed. Use a pacer set slightly faster than comfortable, so the voice can't finish every word. It drops the small stuff first — articles, word endings — while visual recognition carries the meaning. Done in short daily doses, the ceiling lifts.

The honest caveat: subvocalization cannot be fully eliminated, and you shouldn't want it gone. Inner speech does real comprehension work, especially on difficult text — it's a feature that's overactive, not a bug. The goal is to quiet it on easy material, not to silence it everywhere. We cover why the eliminate-your-inner-voice pitch is one of speed reading's oldest myths in the science piece.

Cause 3: the words themselves are new to you

The symptom: you're fine with novels and news, but a statistics textbook or a legal filing reduces you to a crawl. This isn't an eye problem; it's a vocabulary problem. Reading speed is gated by word recognition — a word you've met a thousand times is recognized at a glance, while a term you've met twice needs effortful decoding, every single time, until enough exposure makes it automatic.

The fix: more reading in that domain, and nothing else. No pacer drill will ever speed up recognizing "heteroscedasticity." This is also why a single reading speed is a slightly fictional idea: the same brain reads different materials at wildly different rates, which is exactly what Brysbaert's data shows — fiction faster than non-fiction, technical material slower than both. Your speed in a domain is mostly a measure of your mileage in it.

Cause 4: your mind wanders and you reread in loops

The symptom: you reach the bottom of the page and realize nothing came aboard. So you go back to the top, and halfway down it happens again. This one masquerades as a reading problem, but your eyes did their job — it's attention that left the building. The rereading loop then doubles the time you spend on every page, which is what actually makes you slow.

The fix: structural, not ocular. Shorter timed sessions — ten or fifteen minutes with a visible end point — keep attention inside the window far better than open-ended marathons. A pacer helps here too, for a different reason than in cause 1: a moving target gives a wandering mind something physical to track. And if the deeper problem is that even attentive reading doesn't stick, that's a retention issue rather than a speed issue — we've written up what actually works in how to remember what you read.

Get your baseline before picking a fix — free test →

Cause 5: the material is genuinely hard — and slow is correct

Dense mathematical proofs. Contracts. Philosophy that spends a page defining its terms. If this is what you're reading slowly, congratulations: your reading speed is working as intended. Comprehension declines as speed is pushed — that's the central finding of the Rayner review — and the practical ceiling for true reading with comprehension sits around 400-500 WPM even on easy material. On hard material the sustainable rate is far lower, and pushing past it just means arriving at the end with less.

Speed is a dial, not a constant. Skilled readers turn it constantly — up for a familiar summary paragraph, down hard for the one sentence carrying the argument. If your slowness only shows up on genuinely dense text, the fix is to stop treating it as a defect. The trade-off between pace and understanding is real and measurable, and we've gone deep on it in reading comprehension and speed.

Cause 6: you only ever read fragments on screens

The symptom: you're fluent in feeds, emails, and threads, but a book chapter feels like wading through wet sand, and you keep checking how many pages are left. Screen reading trains a specific behavior — sample, extract, bail — that the Rayner review would classify as skimming, which is a different act from reading, not a faster version of it. Do it all day, every day, and it becomes your default gear. Books punish that gear.

The fix: rebuild deep-reading stamina, which trains like any endurance. Start with ten uninterrupted minutes a day on a physical book or a full-screen reader with notifications off, and extend gradually. The first week feels genuinely uncomfortable. It's not a moral failing and it's not permanent — the capacity comes back with unglamorous consistency. If the bigger obstacle is finding the time at all, that's its own problem with its own fixes.

When is slow reading worth a professional look?

Everything above assumes habits — patterns any adult can retrain. One pattern is different, and it deserves a plain paragraph rather than a sales pitch.

How much faster can you realistically get?

For the mechanical causes — regressions, subvocalization, attention loops, fragmented-screen habits — short daily practice typically produces roughly 30-60% improvement over about six weeks. That range is consistent with the published training literature, and it's a typical outcome, not a promise. A reader starting at 200 WPM lands somewhere around 260 to 320. For that reader, a 10,000-word chapter drops from 50 minutes to somewhere between about 31 and 38. Check the arithmetic yourself — it holds.

What you will not do is triple your speed, because past roughly 400-500 WPM comprehension falls away and you're skimming with extra steps. The vocabulary cause improves on the timescale of months of reading in the domain, not weeks of drills. And the hard-material cause shouldn't improve at all — slow there is the point. If you want the actual training plan for the trainable causes, it's in how to read faster, drills and schedule included.

Slow compared to what?

Most people who type "why do I read so slow" into a search box are within shouting distance of average and comparing themselves to a number someone invented to sell a course. Some have one fixable habit quietly taxing every page they read. A few are reading hard things at exactly the right speed and feeling bad about it for no reason.

You can't tell which one you are by feel. Measure, name the cause, apply the matching fix — and let the dense stuff be slow. That last part isn't a consolation prize. It's how reading is supposed to work.