A typing speed test measures how quickly and accurately you type, reported in words per minute (WPM). The industry-standard formula counts every five correct characters as one word, so results are directly comparable across typing-test sites and apps.
Most typing tests use prose. This one adds a Code Mode that tests you on real JavaScript and Python snippets — including indentation, brackets, semicolons, and template literals. If you write code for a living, prose WPM doesn't reflect your real-world typing speed.
Everything runs in your browser. Choose 15, 30, or 60 seconds, click into the test area, and start typing. Your best score this session is saved locally so you have something to beat.
What you'll learn while taking the test
WPM is calculated as (correct characters ÷ 5) ÷ minutes. That's why a typo costs you twice — you lose the correct character and you spend time fixing it.
Accuracy matters more than raw speed past a certain point. Most working programmers benefit more from going from 92% to 98% accuracy than from going from 60 to 70 WPM.
Code typing has different muscle memory than prose. The brackets, underscores, and equals signs that come up constantly in code are physically slower keystrokes for most keyboards.
How to take a typing test
1
Pick a mode
Words for everyday prose. JavaScript or Python for code typing. The Code Modes use real snippets, not random characters.
2
Pick a duration
15 seconds for a quick warmup, 30 for the standard benchmark, 60 for a more reliable read on sustained speed.
3
Click into the test area
The timer starts on your first keystroke, not when you click — so you don't lose time clicking through.
4
Type the visible text
Correct characters turn dark, mistakes turn red. The text doesn't scroll — finish what you see, or run out of time.
5
Check your score
WPM, accuracy, and error count appear when the timer ends. Press Restart to try a fresh sample.
WPM benchmarks
Rough ranges for prose typing on a full-size keyboard.
WPM
Level
What it means
0–20
Beginner
Two-finger or hunt-and-peck — still learning the keyboard
20–40
Hobbyist
Comfortable typing — common for casual computer use
40–60
Average
Most office workers and students fall here
60–80
Above average
Touch-typing with good muscle memory
80–100
Proficient
Common for writers, journalists, and senior developers
100–120
Fast
Top decile — typing rarely bottlenecks your work
120+
Expert
Competitive level — often involves practice on Monkeytype or similar
Tips to push your WPM higher
Don't look at the keyboard
Touch typing — knowing where each key is by feel — is the single biggest unlock for typing speed. If you still glance down, cover the keys with a cloth for a week and force the habit.
The bottleneck for most typists isn't finger speed — it's the round-trip between screen and keyboard. Touch typing removes that round-trip entirely.
Prioritize accuracy over speed
Counterintuitively, slowing down to hit 100% accuracy in practice raises your test-day WPM faster than pushing speed and ignoring typos.
Every typo costs roughly two keystrokes — the bad character plus the correction. At low accuracy, you spend more time fixing than typing.
Take the test daily, briefly
A single 30-second test every morning beats one long session per week. Typing improvement is a daily-touch skill, like a musical instrument.
Muscle memory consolidates during sleep. Daily exposure — even briefly — pays compound interest. Weekly practice plateaus quickly.
Common typing-test mistakes
Comparing scores from different sites without checking what they count as a "word". Some sites count whole words; others use the standard five-characters-per-word formula. Always check the methodology before celebrating or worrying.
Testing on a mechanical keyboard at home and assuming the same WPM at the office on a flat membrane keyboard. Different actuation force = different effective speed.
Holding your breath while typing fast. Sounds silly, but it's a real performance limiter — slow, steady breathing improves sustained accuracy.
Typing Speed Test FAQ
How is WPM calculated?
Every five correct characters count as one word. Your final WPM is (correct characters ÷ 5) ÷ minutes elapsed. Typos do not count toward the correct-character total, so they hurt your score twice — once for the wrong character and once for the time spent fixing it.
What's a good WPM for a programmer?
60–80 WPM is plenty — programming is rarely typing-bound. Past 80 WPM, additional speed has diminishing returns. Code-mode WPM tends to be 20-30% lower than prose WPM because of indentation, brackets, and special characters.
What is Code Mode?
Code Mode swaps the standard English word list for real JavaScript or Python snippets — const, arrow functions, def, list comprehensions, template literals. It measures speed and accuracy on the kind of text you actually type at work, not on Shakespeare.
Is the test fair? Same words for everyone?
Each test pulls from a shared pool but shuffles the order, so two tests in a row never look identical. The vocabulary is the same — only the sequence differs.
Is my score saved?
Your best score for this session is held in memory so the next test gives you a number to beat. Refresh the page and it resets. We don't send anything to a server.
How can I improve my typing speed?
Touch-type without looking. Practice short daily sessions. Prioritize accuracy over raw speed. And don't switch keyboard layouts mid-improvement — pick QWERTY, Dvorak, or Colemak and commit for at least a month before evaluating.