WPM Test — Check Your Typing Speed

Take a WPM test to measure your real-time typing speed — understand the difference between gross and net WPM, how accuracy affects your score, and how regular WPM testing helps track progress from your current speed to your target.

How a WPM Test Works and What Your Score Means

Real-time WPM calculation: As you type each character, the test calculates your current pace in words per minute — this live counter updates continuously so you can see whether you are above or below your target speed throughout the passage.
Gross WPM versus net WPM: Gross WPM counts all characters typed (including errors) divided by 5, divided by minutes — net WPM subtracts a penalty for each uncorrected error. Employers and certification tests use net WPM, which is always lower than or equal to gross WPM.
The accuracy-speed trade-off: Above 95% accuracy is the target for most professional typing contexts — below 90% accuracy, the error penalty reduces net WPM enough to negate the speed advantage, making slow-and-accurate typing more efficient than fast-and-sloppy.
Text type affects your score: Common English words produce higher WPM scores than technical jargon, code, or random word lists — your "natural language WPM" and your "code typing WPM" may differ by 15–25 WPM for the same typist.
Monthly retesting reveals true progress: Day-to-day WPM scores fluctuate based on fatigue, stress, and familiarity with specific passages — tracking monthly averages over 3–4 tests reveals genuine improvement trends that single scores can't show.

Test My Typing Speed

How to Use the WPM Test

Click to start the test: The timer begins when you press the first key — read the full displayed passage briefly before starting so you are not surprised by punctuation or unusual words mid-test.
Type continuously without correcting: On most WPM tests, backspacing to fix errors costs more time than the error penalty — practice letting small errors pass and keeping forward momentum to maximize net WPM.
Monitor live WPM: Watch the live WPM counter to maintain a consistent pace — if your speed drops significantly mid-passage, you may be slowing down for difficult character combinations that you should practice separately.
Note your gross versus net score: A large gap between gross and net WPM signals an accuracy problem; a small gap with a low gross WPM signals a pure speed problem — each requires a different practice strategy.
Record your result: Log your gross WPM, net WPM, and accuracy percentage in a spreadsheet or notes app — tracking results over time reveals your improvement rate and whether your practice method is working.

Real-World Use Case

A programmer who began learning touch typing 3 months ago wants to track whether their investment in re-learning to type is paying off. They take a WPM test on the first day of each month and record gross WPM, net WPM, and accuracy in a simple spreadsheet. Month 1: 34 gross WPM, 29 net WPM, 91% accuracy — still in the regression phase of relearning. Month 2: 48 gross WPM, 44 net WPM, 94% accuracy — speed recovering as muscle memory builds. Month 3: 61 gross WPM, 58 net WPM, 97% accuracy — surpassing their original hunt-and-peck speed of 52 WPM. The monthly WPM test data makes the improvement visible and concrete, validating that the difficult transition period was worth the investment and motivating continued practice toward their 75 WPM goal.

Best Practices for WPM Testing

Test at the same time of day for consistent comparisons: Typing speed is measurably higher in the afternoon than first thing in the morning — testing at consistent times of day removes this variable and makes progress comparisons more meaningful.
Take 3 tests and average the results: A single WPM test is affected by how familiar you are with the specific passage, your current alertness, and random typing errors — averaging 3 tests on different passages gives a more representative score.
Use the same test duration when tracking progress: A 1-minute WPM score and a 5-minute WPM score are not directly comparable — most people sustain higher WPM for 1 minute than over 5 minutes, so comparing different durations distorts trend data.
Test on code passages if you are a programmer: Technical typing — variable names, brackets, underscores, camelCase — uses different finger patterns than prose — a WPM test on code-like content measures the skill you actually use at work.
Practice the day before, not the day of: Practicing immediately before a WPM assessment can cause fatigue and lower your measured score — light warm-up typing is fine, but intense practice sessions should be the day prior.

Performance & Limits

Net WPM formula: Net WPM = ((characters typed − error characters) ÷ 5) ÷ minutes — this is subtly different from gross minus errors and is the most accurate formula for professional assessment.
Accuracy threshold for meaningful net WPM: Below 85% accuracy, net WPM becomes a poor measure of useful typing speed — focus entirely on accuracy before measuring net WPM as a performance indicator.
Passage length and difficulty: Longer passages with varied vocabulary provide more stable WPM estimates — 250-word passages give more consistent results than 50-word passages where a single difficult word cluster can skew the score significantly.
Browser typing latency: Modern browsers process keystroke events within 1–5 milliseconds — this latency is negligible and does not materially affect WPM calculation accuracy compared to a native application.
Refresh-free retesting: Each new test generates a fresh passage — back-to-back testing on different passages gives a truer measure of general speed than repeated attempts on the same text.

Common Mistakes to Avoid

Treating one WPM score as definitive: A single test score is a data point, not a verdict — if you score lower than expected, take two more tests before adjusting your practice plan, since daily variation of 5–10 WPM is completely normal.
Optimizing for the test rather than for real typing: Memorizing common test passages or using keyboard macros inflates test scores without improving actual typing ability — measure honestly to get practice feedback that genuinely helps.
Comparing scores across different platforms without considering their methodologies: Some WPM tests count actual word boundaries rather than the 5-character standard, some include error characters in the WPM calculation, and some use different penalty formulas — scores from different platforms are not directly comparable.
Neglecting the accuracy metric: Focusing only on WPM and ignoring accuracy percentage leads to reinforcing error-prone typing patterns — always review accuracy alongside WPM and treat any result below 94% as a signal that accuracy practice should precede speed practice.

Privacy & Security

In-browser-only keystroke capture: Keystrokes are captured within the test interface only — no system-level keyboard hook is involved and the tool cannot read typing in other applications or browser tabs.
No score transmission: Your gross WPM, net WPM, and accuracy results are computed locally in JavaScript and displayed in your browser — no test results are sent to a server or linked to any identifier.
Session-scoped only: Test data (passage text, your typed characters, elapsed time) exists only in browser memory for the duration of the test — navigating away clears everything with no persistence.
No fingerprinting via typing patterns: Research shows typing patterns (rhythm, digraph timings) can be used to identify individuals — this tool does not collect or analyze inter-keystroke timing data beyond what is needed for real-time WPM calculation.

Frequently Asked Questions

What is the difference between gross WPM and net WPM?

Gross WPM measures raw typing speed without accounting for errors — it counts every character typed (including incorrect ones), divides by 5, and divides by elapsed minutes. Net WPM (also called adjusted WPM) subtracts a penalty for errors, making it a measure of useful, accurate typing output. The most common net WPM formula: Net WPM = Gross WPM − (uncorrected errors ÷ time in minutes). Alternatively: Net WPM = ((total characters − error characters) ÷ 5) ÷ minutes. Example: 70 gross WPM with 5 uncorrected errors in 1 minute = 65 net WPM. The gap between gross and net WPM is directly proportional to your error rate — at 98% accuracy, gross and net WPM are nearly identical; at 85% accuracy, they diverge by 10+ WPM. Employers always care about net WPM because it measures what you actually produce, not what you attempt.

Why does my WPM score vary so much between tests?

WPM score variability is normal and expected — individual test scores reflect numerous factors beyond typing skill. Common causes of score variation: passage familiarity (text with common words scores higher than technical jargon); time of day (afternoon scores typically 5–10% higher than morning); cognitive fatigue (scores drop measurably after sustained concentration); specific difficult character combinations in a given passage (a passage with many capital letters or number-row characters will produce lower scores than one using only common lowercase letters); and environmental distractions. To get a representative WPM score, take at least 3 tests on different passages and average the results. For professional assessment purposes, use 3–5 minute tests rather than 1-minute tests — longer tests produce more stable, representative scores by smoothing out passage-specific variance.

How does typing code compare to typing regular text in terms of WPM?

Code typing WPM is typically 30–50% lower than prose typing WPM for the same person, due to several structural differences. Code uses the number row frequently (digits in variable names, version numbers, array indices) — number row keys require longer reach and are slower for most typists. Symbols like braces {}, brackets [], parentheses (), underscores _, and comparison operators require modifier keys (Shift) and non-home-row positions, adding latency per character. CamelCase and snake_case require frequent capitalization or underscore keystrokes that interrupt flow. Additionally, code often uses rare letter combinations (like "__init__", "nullptr", "querySelector") that the brain processes slower than common word bigrams. Programmers who regularly type code build separate speed for code-specific patterns — practicing code-specific passages in a WPM test provides a more useful benchmark for developer productivity than prose-based tests.

Should I aim for higher WPM or higher accuracy during practice?

The evidence-based answer: prioritize accuracy above 95% before pursuing speed. Here is why — when you type an error and correct it, you spend time on the error keystroke, the backspace, and the correction. At typical correction speeds, a single error costs 0.5–1.5 seconds. At 60 WPM, a 1-second error penalty is equivalent to dropping to 52 WPM for that word. Errors also reinforce incorrect motor patterns — your fingers learn the wrong sequence and must overcome that learning later. The correct practice approach: find the speed at which you maintain 97%+ accuracy, then gradually push speed while maintaining that accuracy threshold (known as the "maximum comfortable speed" method). Most typing coaches recommend slowing down by 10–20% below your max speed and increasing gradually, rather than typing at max speed and tolerating errors. Accuracy-first practice produces better long-term results despite feeling slower in the short term.