The Student Knows the Code, So Why Are They Still Reading So Slowly?

It can be tricky to know what to do next when a student seems to know the code but reading is still slow and effortful. They can decode. They can apply phonics knowledge. They can often work out unfamiliar words accurately, yet reading is still painfully slow.

They sound out words you feel they should know by now. Their reading remains effortful. They may lose their place, miss small words or struggle to hold onto meaning across a sentence because so much cognitive effort is being directed towards getting the words off the page.

When this happens, our first instinct can be to teach more code. Sometimes that is exactly what the student needs. But sometimes the issue is not primarily whether they can decode. It is how efficiently and automatically they can access that information.

This is where rapid automatised naming, automaticity and reading fluency become important pieces of the dyslexia profile.

Accurate reading and fluent reading are not the same thing

We often talk about decoding as though a student either can or cannot do it. In practice, there is a huge difference between a student who can decode a word after several seconds of deliberate effort and one who can recognise and process that same word quickly and efficiently within connected text.

A student may have learnt that:

● ai can represent /ae/

● igh can represent /ie/

● tion often represents /shən/

They may be able to segment and blend those patterns correctly when asked. But if every encounter still requires conscious effort, reading remains cognitively exhausting.

For fluent readers, word recognition becomes highly automatic. We are still processing the relationship between print and sound, but we do it so efficiently that very little conscious attention is required.

That frees cognitive capacity for everything else reading requires - understanding vocabulary, making inferences, integrating ideas, monitoring comprehension and thinking about the meaning of the text.

For some students with dyslexia, getting to that level of automaticity takes much longer.

Where does RAN fit?

Rapid automatised naming, or RAN, measures how quickly a person can retrieve and verbalise the names of highly familiar visual stimuli such as letters, numbers, colours or objects. It is not simply a test of whether the student knows the names. They usually do.

The question is how efficiently they can repeatedly access those labels from long-term memory. That distinction matters for reading.

A student may know all their letter names and sounds but still take longer than expected to retrieve and integrate that information when reading.

In practice, students with significant RAN weaknesses are often the ones who make us say:

“They know this. Why are they still having to work it out every time?”

They may have received good phonics instruction. They may show reasonable phonological awareness. They may even decode accurately in untimed tasks.

But reading remains slow, effortful and lacking automaticity.

What might a weak automaticity profile look like?

Not every student with slow reading has a RAN weakness, so I would never infer it from reading rate alone.

But some patterns should make us look more closely.

You might see a student who:

● Reads accurately but very slowly

● Continues to sound out familiar words

● Has much stronger untimed decoding than timed word-reading performance

● Seems to recognise a word one day and decode it again the next

● Makes increasing errors when reading longer passages

● Skips small words or loses their place

● Becomes visibly fatigued by reading

● Has poor reading fluency despite considerable phonics instruction

● Struggles to develop quick recognition of high-frequency or irregular words

● Can decode individual words but has difficulty maintaining meaning across connected text.

If the student knows the code but reading is still slow and effortful, the next thing to consider is how efficiently they can access and use that knowledge when reading.

Why more phonics may not solve the problem

Phonics instruction remains essential. If a student has gaps in code knowledge, we need to teach those gaps explicitly. But if the student already has reasonable code knowledge and the major difficulty is automaticity, repeating more and more phonics content without addressing fluency may lead to a lot of therapy without enough functional change.

This is one of the reasons I think it is so important not to equate a literacy program with an intervention plan. A structured phonics program may be an important part of intervention, but it doesn’t tell us everything we need to know about an individual student. The assessment profile can.

If two students both have dyslexia but one has significant phonological awareness difficulties and the other has relatively strong phonological awareness with marked RAN and fluency weaknesses, I would not expect their therapy to look identical. The underlying profile matters.

So what changes in intervention?

The goal is not to “train RAN” by repeatedly asking a student to name colours or numbers faster. The RAN result helps us understand why automaticity may be difficult and why the student may require more deliberate work to build efficient word reading. For these students, I tend to think carefully about several areas.

Repeated exposure

Students with automaticity difficulties may need substantially more successful encounters with a word or pattern before it becomes efficient. That means repetition is important, but it needs to be purposeful.

We want students repeatedly reading material that is accessible enough for them to achieve success while still providing enough challenge to promote learning.

Word-level efficiency

Sometimes connected-text reading is so demanding that the student cannot yet practise fluency effectively within passages. Timed measures such as efficient sight-word and non-word reading can help us understand whether the bottleneck begins at word level.

We can then work on increasing accuracy and efficiency with previously taught patterns and words before expecting fluent connected-text reading.

Connected-text fluency

Ultimately, reading exists in connected text. Repeated reading of appropriate passages is important, particularly when the aim is not simply “read faster” but to develop smoother phrasing, fewer hesitations and more efficient word recognition.

I am much more interested in whether reading is becoming easier and more fluent than whether a student can simply beat their previous time.

Orthographic learning

If words are not becoming firmly established despite repeated exposure, I would also want to look at orthographic processing.

Can the student build accurate representations of written words?

Are they remembering the specific spelling patterns within words?

Are irregular words remaining unfamiliar despite repeated teaching?

RAN is often only one piece of the puzzle.

Morphology and larger word units

For older students, automaticity doesn’t only come from recognising individual grapheme-phoneme correspondences. Students also need to recognise larger meaningful and orthographic units efficiently. Prefixes, suffixes, roots, syllables and common letter patterns can reduce the amount of information they need to process one sound at a time.

A student reading disagreement should not need to approach it as a completely novel sequence of individual sounds. The more efficiently they recognise familiar units within words, the less effortful reading becomes.

Fluency is not just reading faster

I think this is an important distinction. When we talk about fluency, it can easily become a discussion about words per minute. Reading rate does matter, but fluent reading is broader than speed.

I am also listening for:

● Accuracy

● Automatic word recognition

● Appropriate phrasing

● Reduced hesitation

● Expression

● Whether the student can maintain meaning while reading.

A student who reads quickly but inaccurately is not fluent. Neither is a student who reads every word correctly but so slowly and laboriously that comprehension collapses. The goal is efficient reading that supports meaning.

Sometimes comprehension difficulties are actually fluency difficulties

This is another area where the profile matters. A student may answer comprehension questions poorly after reading a passage. It can be tempting to conclude that they have a reading comprehension problem. But sometimes the student understands language well when information is presented orally.

The difficulty emerges because reading itself is consuming so much cognitive capacity that there is little left for comprehension. If the student is spending several seconds decoding individual words, holding the meaning of an entire sentence in mind becomes extremely difficult.

That changes our intervention priorities.

We may still work on vocabulary and comprehension strategies, but improving the efficiency of word reading may be one of the most important things we can do to improve comprehension.

The assessment needs to tell us more than “this child has dyslexia”

A diagnosis is important, but clinically, I want to know more.

I want to know:

Where is the reading difficulty coming from?

Is phonological awareness weak?

Is rapid naming significantly slow?

Is orthographic learning difficult?

Is decoding accurate but inefficient?

Is there a coexisting language difficulty?

How does the student’s performance change between isolated words and connected text?

What happens when time pressure is introduced?

And how is all of this affecting their ability to participate in learning?

Those questions tell us far more about intervention than the diagnostic label alone.

The key shift

When a student has had substantial phonics instruction but reading is still slow, I don’t automatically assume they need more of the same.

I look again at the profile. They may still have code gaps. But they may also be telling us:

“I know it. I just can’t access it quickly enough yet.”

That requires us to move beyond asking whether the student can decode and start considering how efficiently they are reading, how well written words are becoming established, and what is preventing reading from becoming automatic.

Because knowing the code is an essential step. But for successful reading, students also need to be able to use that knowledge quickly enough that they can stop thinking so hard about the words, and start thinking about what those words mean.

If you’re a speech pathologist working with students with dyslexia and you’re finding it difficult to work out what a particular profile means for intervention, you don’t have to try to piece it all together on your own.

I offer 1:1 supervision and mentoring for speech pathologists, where we can look closely at individual cases, assessment results, intervention planning and the clinical reasoning behind what to target next.

You can also watch my online webinar, From Literacy Intervention to Dyslexia Support, which explores the broader factors speech pathologists need to consider when supporting students with dyslexia beyond simply teaching reading and spelling.

Both options are designed to help you feel clearer about the student in front of you and more confident about your next clinical step.