Typing Speed Test

Typing speed is measured in words per minute, and the definition of a word is the first thing worth knowing.

A word is five characters

There is no attempt to count actual words, because words vary in length and that would make scores incomparable between texts.

WPM = (characters typed ÷ 5) ÷ minutes elapsed

Spaces count. Typing 300 characters in a minute is 60 WPM regardless of whether the text was "a a a a a" or "extraordinarily".

The five-character convention dates to research in the 1920s on average English word length including the following space, and it has been standard ever since. It is what makes a score from one test comparable with a score from another.

Gross against net

Gross WPM is the raw figure above, counting everything typed.

Net WPM subtracts errors:

Net WPM = Gross WPM − (uncorrected errors ÷ minutes)

Typing 60 gross WPM with 5 errors in a one-minute test gives 55 net.

Net is the only figure worth quoting. Gross speed with 15% errors describes someone who cannot type, and it is the number that low-quality tests report because it flatters.

Accuracy is separately reported as correct characters over total characters. Below 95%, speed is not the problem.

What the numbers mean

The recognised record for sustained typing is around 216 WPM, set on a manual typewriter by Barbara Blackburn using a Dvorak layout.

For context, speech runs at 130 to 160 WPM and handwriting at 20 to 30. Typing at 60 WPM is roughly twice as fast as writing by hand and less than half as fast as speaking, which is why dictation is faster for first drafts and typing is faster for anything requiring precision.

Why accuracy beats speed

An error is not one keystroke of cost. It is:

• Noticing it, which takes attention away from the text
• Reaching for backspace
• Deleting the wrong characters
• Retyping them
• Recovering the rhythm

Studies of correction cost put a single error at roughly the equivalent of five to ten keystrokes of lost time. An error rate of 5% therefore costs more than the 5% suggests, and at 10% the correction time exceeds the typing time.

The practical rule for improving: slow down until accuracy is above 97%, then let speed return. Practising fast with errors trains the errors, because the fingers learn the movement that was actually performed.

Touch typing

Touch typing means typing without looking at the keyboard, using all ten fingers with each assigned to specific keys.

The home row is ASDF for the left hand and JKL; for the right, with the index fingers resting on the raised bumps on F and J. Every other key is reached from there and the fingers return.

The reason it is faster is not the number of fingers. It is that the eyes stay on the screen, so errors are caught immediately and there is no cost to looking down and back up. A skilled two-finger typist can reach 60 WPM; they simply cannot proofread while doing it.

Learning it properly takes two to four weeks of daily practice and passes through a phase of typing slower than before, which is where most people abandon it. The dip is real and it ends.

Layouts

QWERTY was designed in the 1870s. The persistent story that it was arranged to slow typists down is a simplification — the arrangement separated commonly paired letters to reduce typebar jams, which had the effect of distributing work across both hands.

Dvorak, from 1936, places the most common letters on the home row and claims a substantial efficiency gain. Independent studies have found the real-world improvement to be modest — perhaps 5% to 10% — and far smaller than the difference between a trained and untrained typist on either layout.

Colemak changes only 17 keys from QWERTY, keeping most shortcuts in place, which makes it easier to adopt than Dvorak.

The honest assessment: switching layouts is rarely worth it. The transition costs weeks of reduced productivity, every shared computer becomes awkward, and the gain is small compared with simply practising. The exception is someone with a repetitive strain injury, where reduced finger travel genuinely helps.

Practising usefully

Practise accurately. 97% or better, always. Speed follows accuracy and does not lead it.

Practise real text, not random words. Common letter pairs and word endings build the muscle memory that transfers to actual work.

Practise the keys you get wrong. Most tests report a per-key error breakdown, and it is usually concentrated in a handful of reaches — typically the right-hand punctuation and the numbers.

Learn the numbers row properly. Most people who touch-type letters still look down for digits and symbols, which breaks the rhythm most in exactly the work where it matters.

Fifteen minutes a day beats two hours a week. Motor learning consolidates during sleep, so frequency matters more than duration.

Expect a plateau around 60 to 70 WPM. Getting past it needs deliberate work on weak keys rather than more of the same practice.

Ergonomics

Speed is worth nothing if typing hurts.

Wrists straight and floating, not resting on the desk while typing. A wrist rest is for the pauses.

Elbows at roughly 90 degrees, which usually means the keyboard is lower than most desks put it.

Screen at eye level, so the neck is neutral.

Light touch. Most people press far harder than necessary, and mechanical keyboards with a short actuation distance help.

Break every 30 to 45 minutes, briefly. This does more for long-term comfort than any equipment.

Repetitive strain injury develops slowly and is difficult to reverse. Pain, tingling or numbness in the hands or forearms is a reason to change something immediately rather than to type through it.

What a test does not measure

A typing test measures transcription — copying text that is already written. Most real typing is not that.

Composition is slower, because the fingers wait for the sentence. Someone who transcribes at 80 WPM typically composes prose at 30 to 40, and the gap is thinking rather than typing.

Code is slower again. It is dense with symbols, brackets and capitals, the error cost is high, and much of it involves navigating rather than typing. Editing existing code involves far more cursor movement than character entry.

Data entry involves the number pad, tab keys and constant switching between fields — a different skill from prose typing, and one that transcription tests do not exercise.

This is why raw WPM stops predicting productivity above about 60. Past that point, the constraint is what you are typing rather than how fast you can type it, and the returns on further speed practice fall sharply.

What to work on after 60 WPM

Keyboard shortcuts. Ctrl-arrow to move by word, Home and End, Shift to select, Ctrl-Backspace to delete a word. Reaching for the mouse is what actually costs time in most editing, and eliminating it is worth more than another 10 WPM.

Text expansion. A snippet tool that turns a few characters into a paragraph you type often — an address, a code block, a standard reply — beats typing it faster.

Learning your tools. A developer who knows their editor's multi-cursor and navigation commands is far quicker than one who types faster.

Dictation for first drafts. Speech runs at 130 to 160 WPM against typing at 60 to 80, and modern dictation is accurate enough for a rough draft that is then edited by hand.

The honest summary: typing speed matters up to a threshold and then stops mattering. Reaching 60 WPM accurately is worth the practice; going from 80 to 100 is a hobby.

What this tool assumes

• A word is five characters including spaces, which is the standard convention.
• Net WPM subtracts uncorrected errors; accuracy is reported separately.
• The timer starts on the first keystroke, not when the page loads.
• Results depend on the text, so a score on one passage is not exactly comparable with another.
• Everything runs in your browser. Nothing you type is sent anywhere.