Last updated: September 7, 2026
Two different questions, not two names for the same thing
Typing consistency vs accuracy trips people up because both sound like they're measuring "how good" a run was — but they answer completely different questions. Accuracy asks how many characters you got right. Consistency asks how steady your pace was while you were typing them. A run can be highly accurate and still wildly inconsistent, or fairly consistent while making occasional mistakes. They're independent metrics on purpose.
What "inconsistent" actually looks like
The bursty line above spikes past 100 WPM, crashes into the 30s, then recovers — that's a classic burst-then-fade pattern, often from typing a familiar word fast and then hesitating on the next one. The steady line never gets as fast at its peak, but it also never falls apart. Ascendancy's consistency score rewards the second pattern, even though its top speed is lower.
It's measured against your own average, not a fixed pace
A common misconception is that consistency means capping your speed to avoid variance — it doesn't. The score measures how steady your pace is relative to your own average during that run. A sustained 90 WPM the whole way through scores just as well as a sustained 40 WPM. The goal isn't typing slowly on purpose; it's avoiding the burst-then-crash pattern regardless of what pace you're bursting from.
Why it's a separate gate, not folded into accuracy
If consistency were just averaged into accuracy, a burst-then-crash run could still post a decent composite score by getting the crashed-through words right eventually. Keeping consistency as its own independent threshold on every hero classification closes that gap — a hero tier means you can sustain the pace, not just eventually get there.
What causes inconsistency in practice
The most common cause is hitting an unfamiliar word or punctuation mark mid-flow and hesitating before continuing — the hands know most of the passage but stall on the part they don't. The fix isn't slowing down everywhere; it's specifically drilling the patterns that cause the stall, so the hesitation stops happening rather than just becoming less frequent.
Check your own pattern
Your simulation history on your Ascendant Console shows your consistency score alongside WPM and accuracy for every run. If your WPM looks strong but consistency lags behind it, that's usually the clearest sign you're bursting rather than sustaining — worth a few practice runs focused purely on steady pace before pushing top speed again.
Worked example: two runs, same average, different scores
Picture two runs that both average out to roughly 60 WPM overall. Run A — the steady line in the chart above — holds between roughly 57 and 62 WPM the entire time, barely moving. Run B — the bursty line — spikes past 100 WPM for a few seconds, crashes into the 30s, recovers, and repeats that pattern several times over the run. Both runs can post nearly the same average WPM, but Run A scores meaningfully higher on consistency, because the score measures deviation from your own average pace during that run, not the average itself. This is also exactly why a fast-but-bursty run underperforms its apparent potential once it's checked against a fixed consistency threshold — the peak speed never mattered as much as it looked like it did.
Frequently Asked Questions
Can I have high consistency and low accuracy at the same time?
Yes — they're independent metrics. A run can hold a rock-steady pace while still making occasional mistakes; steadiness and correctness aren't the same thing. See "Two different questions, not two names for the same thing" above.
Does typing a genuinely difficult passage lower my consistency score unfairly?
Not inherently — the score is relative to your own average during that specific run, so a generally harder passage that slows your average down evenly doesn't necessarily hurt consistency. What hurts consistency specifically is sudden hesitation on individual words or characters mid-run, not an overall slower pace.
How much does consistency actually matter compared to WPM?
Enough that it's a separate, independent gate on every hero classification rather than something folded into a composite score. A high-WPM run that fails the consistency threshold doesn't get partial credit for the speed.
If my WPM and accuracy are both strong, why is my classification still low?
Consistency is very likely the answer — check your Ascendant Console to confirm, since it shows all three metrics side by side for every run. It's easy to overlook because WPM and accuracy get most of the attention, but it's an equally hard gate.
Does slowing down my whole run improve consistency?
No — see "It's measured against your own average, not a fixed pace" above. A sustained 40 WPM scores exactly as well on consistency as a sustained 90 WPM. What actually improves it is eliminating the burst-then-crash pattern, which is a separate problem from overall pace — the same drilling approach covered in improving your typing speed applies here too.