Speed means little if every third word needs fixing. This test measures the error rate your fingers actually produce — with scoring that corrections can't game.
Take the Accuracy TestMost typing tests quietly forgive corrections: backspace over a mistake, retype it, and the error disappears from your percentage. That produces flattering numbers and hides the habits slowing you down.
TypeSprint uses first-strike scoring: every character position in the passage is scored exactly once, on the first keystroke that reaches it. What each input event does to your counters:
| Event | Characters | Correct | Errors |
|---|---|---|---|
| First keystroke at a new position, matches the text | +1 | +1 | — |
| First keystroke at a new position, wrong character | +1 | — | +1 |
| Typing past the end of the passage | +1 | — | +1 |
| Backspace / deletion | — | — | — |
| Retyping an already-scored position | — | — | — |
Accuracy is simply correct ÷ scored positions. Corrections cost you the error you made; they can't retroactively erase it — and a type-delete-retype loop adds nothing, so the percentage can't be farmed.
Every error costs you at least three keystrokes: the wrong character, the backspace, and the retype — plus the moment it takes to notice. A 70 WPM typist at 90% accuracy usually finishes real work slower than a 60 WPM typist at 98%.
That's why the test reports Net WPM (correct characters only) next to Raw WPM (everything typed). A large gap between them is an accuracy problem wearing a speed costume. The typing speed test page explains all four reported metrics.
Three things in the app are built for exactly this: