Net WPM vs Gross WPM: what a typo really costs you
Almost every typing test reports a speed with an error penalty baked in. Almost none of them show you the size of that penalty. So here is a real run, measured, with the arithmetic laid out — and the answer is bigger than most people expect.
One measured run
A 30-second English test, typed at a steady pace with a deliberate mistake in roughly every third word. Nothing was corrected — every word was submitted as typed, so the effect of the penalty is isolated from the effect of backspacing.
Ten wrong words. Twenty WPM gone — from 36 down to 16. The typing itself never slowed: the fingers produced the same amount of text they would have if every word had been right. More than half the score disappeared into ten mistakes.
Where the twenty went
Gross speed is the plain count: everything typed, five characters to a word, spread over the time taken. On this run that came to 36.
The penalty is then one word for every word submitted incorrectly, applied at the same per-minute rate as the speed itself. Ten wrong words in half a minute is twenty wrong words per minute — so twenty comes off, and 36 becomes 16.
The detail that surprises people is what the penalty does not depend on. Those ten words contained twenty wrong characters between them, two apiece. Had each contained four, or one, the speed score would have been identical. The unit of damage is the word.
Why accuracy read 78% and not 69%
Accuracy on the same run came out at 78%, which looks generous next to a speed score that lost more than half its value. The two metrics are counting different things on purpose. Accuracy is per character: of roughly ninety characters committed, twenty were wrong, which is 78% right. Net WPM is per word: ten of thirty-two words were spoiled. A mistake is a small fraction of a word's letters and the whole of the word — so accuracy stays high while speed falls, and both are telling the truth.
What this means for practice
A mistake costs a whole word, not a letter
On the run above, ten wrong words cost twenty WPM — the gap between 36 and 16. Whether a word had one wrong letter or four made no difference to the speed score: the penalty is one word either way. A typo is not a small tax on the character you got wrong. It writes off the word.
Accuracy and speed are the same problem
It is tempting to treat them as a trade-off — go faster, lose accuracy; slow down, gain it. But because errors are subtracted from the speed score, accuracy is already inside your WPM. A 78% run does not "have good speed and poor accuracy". It has poor speed, and the accuracy is why.
Corrections cost twice
Backspacing and retyping adds keystrokes to your gross count and time to the clock, without adding anything to what you committed. That is why the two numbers separate: gross rewards finger movement, net rewards finished, correct text. The wider your gap, the more of your effort went into undoing.
The gap is the number to watch
A single Net WPM figure tells you where you are. The distance between gross and net tells you what is holding you there — and it moves much faster than your headline score does when you change how you type.
None of this argues for typing timidly. It argues that "speed" and "accuracy" were never two dials you balance against each other — the second is already priced into the first, at a rate of one whole word per mistake. Which is also why the most reliable way to raise a speed score is usually to find the specific keys you keep missing, rather than to try harder.
Frequently asked questions
What is the difference between Net WPM and Gross WPM?
How much does one typo actually cost?
Why is my Net WPM so much lower than my Gross WPM?
Is it better to correct my mistakes or leave them?
Does a wrong letter ruin the whole word for accuracy too?
Which number should I try to improve?
Do other typing tests calculate Net WPM the same way?
See your own gap
Every TypingFix result shows Net and Gross side by side, plus a per-key breakdown of exactly which keys cost you the difference.
Written and tested by
Vishal Parvat
Founder & Developer of TypingFix
Vishal built TypingFix's multilingual typing engine and its scoring system — the same engine that produces the WPM, CPM, accuracy and consistency numbers described on this site. The figures above are from a single real 30-second run through the live engine, recorded as-is — not modelled, and not rounded to make the arithmetic tidier.
Published 2 September 2026