Timed tests3 min readBy Ian Rennie

Typing Speed Benchmarks for Timed Tests, By Exam

Different timed written exams make different typing demands. A Casper response needs you to produce 180 to 240 words in five minutes; an LSAT Writing Sample needs 450 to 600 words in 35. 'Fast enough' is a different number for each test. This post is a reference you can bookmark: the minimum, comfortable target, and ideal typing speeds for each major timed written assessment, along with the reasoning behind each number.

At a glance

FactorExamTarget WPM
Casper5 min × 180-240 words55-65 WPM
Kira Talent3-4 min × 160-200 words50-60 WPM
GRE AWA30 min × 500-600 words50 WPM
LSAT Writing35 min × 450-600 words45-55 WPM
Duet rationale1-2 min × 110-180 words55-65 WPM
Coding assessments45-90 min × 2-4 problems50+ WPM on real code

How These Benchmarks Were Derived

Each benchmark is a practical target, not an official one. It is derived by taking the typical word-count expectation for a strong response and working backward through realistic thinking pauses, planning time, and a safety margin for re-reading the opening. None of the testing bodies publish official typing-speed targets, and most candidates do better to aim for a specific number than to train without a target at all.

The 'minimum' is the speed below which you will frequently run out of time. The 'comfortable target' is where typing stops being the bottleneck. The 'ideal' is where typing is effectively invisible and you are limited only by how fast you can think.

Stopwatch representing the time pressure that determines typing speed requirements across timed written exams
Every timed test has a distinct relationship between typing speed and word output. These benchmarks make that relationship explicit.

Casper Test Benchmarks

Casper gives you about five minutes per written response with an expected word count of 180 to 240 words. Working backward: 25 seconds planning, 4 minutes 35 seconds typing. At 40 WPM effective speed (net of thinking pauses) you get 160 words; at 55 WPM you get 220; at 70 WPM you get 280.

Minimum: 40 WPM. Target: 55 to 65 WPM. Ideal: 70+ WPM. See the Casper Test Typing Prep track and the full post on Casper typing speed targets.

Kira Talent Benchmarks

Kira written responses typically run three to five minutes. For a four-minute window with 30 seconds of planning, the useful typing time is about 3 minutes 30 seconds. A response of 160 to 200 words is strong. That translates to an effective typing speed of about 45 to 55 WPM.

Minimum: 40 WPM. Target: 50 to 60 WPM. Ideal: 65+ WPM. See the Kira Talent typing prep track.

GRE AWA Benchmarks

The GRE Analytical Writing essay gives you 30 minutes for one essay of 500 to 600 words. Planning plus polishing eats about 8 minutes, leaving 22 minutes of typing. 550 words in 22 minutes is 25 WPM of useful output, which translates to about 35 to 40 WPM raw.

Minimum: 35 WPM. Target: 50 WPM. Ideal: 65+ WPM. See the GRE AWA typing prep track.

LSAT Writing Sample Benchmarks

The LSAT Writing Sample gives you 35 minutes for an argumentative essay of typically 450 to 600 words. The time pressure is moderate but the endurance requirement is real. 500 words in 25 minutes of useful typing is 20 WPM of effective output, or about 30 to 35 WPM raw.

Minimum: 35 WPM. Target: 45 to 55 WPM. Ideal: 60+ WPM. See the LSAT Writing typing prep track and the guide on training typing stamina for long written exams.

Duet Benchmarks

Duet rationale windows are tight — typically one to two minutes per item for 110 to 180 words. That is a higher typing-speed requirement per minute than any other test on this list. At 40 WPM you get around 70 to 80 words; at 60 WPM you get 115 to 125; at 70 WPM you get 135 to 145.

Minimum: 45 WPM. Target: 55 to 65 WPM. Ideal: 70+ WPM. See the Duet typing prep track.

Coding Assessment Benchmarks

Coding assessments are different from written tests — the word-count-per-minute target is not the right metric. What matters is how fluent you are with the specific code patterns the language uses. For Python, 50+ WPM on real code is comfortable. For Rust or C++, aim for 40+ on real code because the symbol density is higher.

See the coding assessment typing prep track and the post on why programmers should practice typing code, not prose.

About the author

Ian Rennie

CEO & Lead Developer at Broctic Inc

Ian is the co-founder and CEO of Broctic Inc, the company behind SureTyping. He designed the platform's lesson system and adaptive training engine, drawing on years of experience building educational software. When he's not coding, he's testing new keyboard layouts — currently splitting time between Colemak-DH and Graphite.