How to Skim a Page Before You Read It

You Have Forty Pages and Three Hours

You've got a forty-page course reading, and the exam is the day after tomorrow. Or a long report someone wants on their desk by nine tomorrow morning.

You start properly, from the first line of the first page. By page twelve you realize everything you've read so far was introduction. You burned an hour on context.

The second option is sneakier. You read everything at the same speed, straight through to the end. You close the material and can't say what the three things that mattered actually were.

Both come from the same place. You treated every page the same way, because you didn't know which ones were different.

And something else is working against you. Your mind wanders. In a study cited by Brysbaert's 2019 meta-analysis, participants reported thoughts unrelated to the text in 42% of sentences, on difficult material.

When the mind wandered, time spent on that sentence went up by nearly a second. So it's not just that you read everything the same way. You read everything the same way, and for a good chunk of the time, you're not even there.

What Actually Happens When You Skim

Skimming isn't accelerated reading. It's a decision about where to spend your time, made before you spend it.

Keep in mind from the start that the same word covers two different things. Everything in this section is about the kind of skimming that latches onto the text's structure. I'll get to the other kind right after.

The difference shows up clearest in a 2009 experiment. Duggan and Payne put people under time pressure and gave them a choice: skim the whole text, or read exactly half of it carefully.

Skimming the entire text produced better memory for the important ideas than carefully reading half of it. Not for the details. Not for the inferences. Just the skeleton.

In the second experiment in the same paper, the advantage disappeared. When the alternative was reading the first half of every paragraph, skimming didn't beat anything.

Put the two experiments together and you get the answer. The gain doesn't come from going faster — it comes from touching the whole text instead of just a chunk of it.

Eye-tracking from the same study shows how a good skimmer behaves. They spend more time on the first paragraphs and the first pages, then speed up.

In other words, they build a map early on, then travel the rest of the text by that map. It's exactly what you do when you check the route before you set off, instead of reading every road sign one by one.

A second finding rounds out the picture. Hyönä, Lorch and Kaakinen measured, in 2002, where people looked and how accurate the summaries they wrote afterward were. The people who paid more attention to headings wrote the best summaries.

Headings aren't decoration. They're the map the author drew for you — the one almost nobody reads as a map.

Skimming also has a close relative it's often confused with: scanning. Scanning is searching for one specific piece of information, when you already know exactly what you're looking for.

It's the only mode of reading that Brysbaert's meta-analysis of 190 studies confirms as qualitatively different from reading. The eye's jumps are longer, the pauses shorter.

Scanning is Ctrl+F for your brain. Skimming is something else. You're not hunting for a word — you're hunting for structure.

What You've Been Told, and Why It's Wrong

The version sold on the market goes like this: you train your eye to move over the text faster, and your brain automatically catches what matters and drops the rest.

Sometimes it even comes with a drawn path. A zigzag down the middle of the page, an S shape down one page and up the next. The idea is that you skim over everything and the essence sticks.

That's been measured. In 1982, Masson ran four experiments with 330 students, ramping the pace from 225 to 600 words per minute.

Recognition of important information dropped. Nothing surprising there yet. The part that breaks the story is that it dropped by exactly as much as recognition of unimportant information.

In other words, the eye racing over the text doesn't select anything. It loses uniformly. What you think you caught is often just what you already knew.

A second set of experiments, run at Manchester, found the same pattern plus one more unpleasant effect. People who skimmed were more likely to believe a complicated statement had appeared in the text when it hadn't.

You don't just end up with gaps. You end up with false beliefs you have no way of catching.

And the drawn paths were tested directly. In the 1960s, Taylor measured graduates of the world's best-known speed-reading course, the ones trained to move in a zigzag down the center of the page.

On a true-or-false test, they scored around 50%. Exactly what you'd get flipping a coin.

The synthesis Rayner and colleagues published in 2016, the most authoritative one on the subject, is unambiguous. Zigzagging down the page is probably the least effective way to skim.

There's another cost, one that gets less airtime. Wilkinson, Reader and Payne showed in 2012 that people forced to skim choose less demanding texts. Skimming doesn't just change your speed — it changes what you're willing to read in the first place.

Now back to the two things sharing the same name, because this is where everything gets decided.

The first is structural skimming. You look at what the author flagged as important: the title, the subheadings, the first line of every paragraph, the bolded words, the conclusion. The selection is already made — you're just reading it.

The second is gist skimming. You run your eyes over the flowing text, faster, and hope your mind retains what matters. The selection is supposed to happen in real time, in your head, without actually reading.

The first works, and there's evidence behind it. The second is exactly what failed in Masson's study.

The question that separates them is simple: who's doing the selecting? If it's the author, you're on solid ground. If it's your eye in motion, you're not.

What Works Instead

The line that keeps the whole thing balanced is this: skimming doesn't replace reading — skimming decides what's worth reading in depth.

So skimming isn't a faster version of reading. It's the step before it, and it has exactly one output: a decision.

On a long piece of material, it looks something like this, and it takes under five minutes for twenty pages:

• The title and every subheading, in order. They give you the skeleton in ten seconds.
• The first paragraph, in full. That's where the author says what's coming.
• The first sentence of every paragraph. It usually carries the idea; the rest just supports it.
• Anything that visually breaks out of the page: bold text, tables, charts, callout boxes.
• The last paragraph, in full. That's where the author says what they said.

Then comes the part most people skip, even though it's the only part that matters. You split the material into three.

What you read carefully, because it's new and hard. What you read quickly, because you already know it or it's just an example. What you skip entirely, because it doesn't answer your question.

A good reader doesn't have one speed. They have a gearbox. They accelerate on the straights and slow down on the curves, exactly like driving.

And one more thing, so you don't fool yourself. After skimming, you don't know the text. You know its map.

The test takes ten seconds. Say out loud what the material is about and where the hard part is. If you can't, the skim didn't work, and there's no point moving on.

There's still the hard question: what do you do with material that has no structure? Course notes written up collectively, PDFs without subheadings, pages of dense unbroken text.

Structural skimming has nothing to latch onto there, and the honest answer is that there's no shortcut. What you can do is build the structure yourself, with a pencil: jot a one-word note in the margin for what each paragraph is about. The first pass gets slower, but the second one becomes possible.

The cost is real, and it's fair to know it. Compared with reading the whole text, skimming leaves you with less — equally less of what matters as of what doesn't. That's why skimming ends in a decision, not a conclusion.

How You Train This

Skimming has a practical problem. It's uncomfortable. Your eye wants to stop and read, because that's what it's done your whole life.

To move across a page in a few seconds without snagging on lines, you need a trained reflex separate from reading.

In Read Wizzard, the exercise that builds this is called Pattern Z. It forces a Z-shaped path across the page, at a pace you don't get to negotiate.

Pay attention to what it is and what it isn't. As a way to read an entire text, the Z-shaped path is contradicted, and you've seen why above. Fifty percent on a two-option test is chance level.

As a recognition step before reading, it's something else. It trains you to cross the page without freezing up, and that crossing is exactly the engine behind structural skimming.

The difference is up to you, in where your eye lands. If it stops on headings, first lines, and bold text, you've done structural skimming. If you're hoping to catch the gist from flowing text, you've done exactly what failed back in 1982.

The second part of the training is the check. After a reading session you get comprehension questions, so you see in black and white the difference between having the map and knowing the text.

Without that check, you're left with the Manchester problem: the feeling that you understood, with no proof that you did.

If you're a student and your reading load is growing faster than the time you have for it, see what training looks like over a real semester. The first decision isn't how fast you read — it's what you actually read.