The typing test programmers actually need

Prose speed is a vanity number. Here is what your fingers do when the text is code — and why the gap is bigger than most developers expect.

0 wpm100% acc0/176

const active = items.filter((item) => item.active);
const ranked = active.sort((a, b) => b.votes - a.votes);
return ranked.slice(0, 10).map(({ id, votes }) => ({ id, votes }));

Why your prose score is misleading

A prose test cycles through twenty-six letters and a space. Code adds braces, brackets, angle brackets and semicolons, and most of them live on a shift-modified key. You are not typing faster letters; you are doing twice as many keypresses per visible character.

That is why the same developer can type English at 95 WPM and code at 45. The second number is not a worse version of the first — it is a different measurement.

What developers typically report

Numbers from a code typing test run lower and tighter than prose scores. The ranges below are what people land on after a few runs on the language they actually use, not their first attempt.

Text	Typical range (WPM)	What dominates the time
English prose	70 – 95	Letter rhythm and reading ahead
Python	45 – 65	Underscores, colons, quotes
JavaScript	40 – 60	Braces, arrows, backticks
HTML	40 – 55	Angle brackets and closing tags
SQL	35 – 55	Uppercase keywords and quotes

Rough orientation only. Code is typed in bursts between thinking pauses, so a lower number here does not mean slow work.

What actually slows you down

Shift reaches. Every brace and quote is two keys, and the pinky does most of it.
Symbol recovery. One misplaced bracket is worth five keystrokes to fix, and editors rarely catch it for you.
Rhythm breaks. Code is short lines with frequent stops; you never build the long unbroken flow that prose allows.
Thinking. Some of your "typing" time is actually reading and deciding, which no typing test can remove.

Practise the language you actually write

Questions

Should I practise code typing at all?

Modestly. Thinking dominates your working day, but symbol reaches you fumble are small interruptions that add up. Fifteen minutes a day for a few weeks closes most of the prose-to-code gap.

Why is my code speed less than half my prose speed?

Because roughly a third of the characters in typical code are shift-modified, and each one interrupts rhythm. A 50% drop is normal, not a sign that something is wrong.

Does this test use real code or generated text?

Real snippets — arrow functions, dict comprehensions, joins, markup with attributes. They are short because a code typing test measures bursts, not endurance.

Does editor autocomplete make this pointless?

Autocomplete removes some typing but not the symbol work, and it never helps with brackets that have to be balanced. If anything, it makes the remaining keystrokes more punctuation-dense.

Last updated 2026-11-12. Written by the GeekType team.