ツール ガイド
productivity 無料 サインアップ不要

タイピングスピードテスト

ライブ精度追跡と難易度レベル付きでWPM単位のタイピング速度を測定します。

ツールを読み込み中…

このツールについて

イージー、ミディアム、またはハードの難易度を選択し、約50語のランダムな文章を入力してください。タイマーは最初のキー入力で開始し、正しく入力された文字は緑でハイライト表示され、エラーは赤で表示されます。ライブ統計が継続的に更新されます:1分あたりの単語数、1分あたりの文字数、精度のパーセンテージ。終了すると、最終WPM、精度、合計時間、エラー数を示す結果画面が表示されます。「もう一度試す」をクリックして新しいランダムな文章を表示できます。

使い方

  1. 1 上部のボタンを使用して難易度レベルを選択してください — イージー、ミディアム、またはハード。
  2. 2 表示された文章を読んでから、下のテキストエリアで入力を始めてください。タイマーは最初のキー入力で開始します。
  3. 3 入力しながらライブのWPM、CPM、精度統計が更新されるのを確認してください。正しい文字は緑に輝き、エラーは赤になります。
  4. 4 文章の入力が終わると結果画面が表示されます。「もう一度試す」をクリックして新しいランダムな文章を始めてください。

How typing speed is actually measured

Typing speed is reported in words per minute (WPM), but a "word" in this context is not a real English word — it is a unit of typed text. The two figures this test shows make the distinction clear. WPM counts the actual whitespace-separated words you typed and divides by the elapsed minutes. CPM (characters per minute) counts every character you typed over the same time. Because the test counts the words you produced rather than a fixed five-character convention, a passage full of short words can read slightly higher than one full of long technical terms — which is exactly why the difficulty level you choose matters.

The clock starts the instant you press your first key, not when the page loads, so thinking time before you begin is not counted against you. The test ends automatically once you have typed as many characters as the target passage contains.

Accuracy, and why it is the number to watch

As you type, the tool compares your input to the target passage character by character. Each position you get right is highlighted green; each wrong character is highlighted red; a cursor marks where you are. Accuracy is the percentage of characters that match the target. The final score also reports an error count, where any character you got wrong — and any character you simply didn't reach — counts as an error.

This matters because raw speed is meaningless without accuracy. A "100 WPM" run riddled with mistakes produces text someone else has to fix, which is slower overall than a clean 70 WPM. A useful target is to keep accuracy at 95% or above and let speed grow underneath that ceiling, rather than chasing a big WPM number with sloppy keystrokes.

The three difficulty levels

LevelContentTests
EasyShort everyday sentences, common wordsRaw finger speed on familiar text
MediumLonger informational paragraphsSustained rhythm, varied vocabulary
HardTechnical passages with symbols and jargonPunctuation, capitals, and unfamiliar words

Each level draws a random passage from a pool, so retaking a test gives you new text rather than letting you memorize one paragraph. The hard set deliberately includes code-like punctuation and capitalized terms, because those are where most typists slow down the most — reaching for the shift key and symbol row breaks the home-row rhythm.

A worked example

Suppose you finish a medium passage of 42 words in 30 seconds with three wrong characters. WPM is words ÷ minutes = 42 ÷ 0.5 = 84 WPM. If the passage was 280 characters, accuracy is roughly (277 correct ÷ 280) × 100 ≈ 99%. Now imagine the same 84 WPM but with 25 errors: accuracy drops near 91%, and the green/red highlighting shows you a cluster of red right where you rushed a hard word. The lesson the test makes visible is that the WPM headline alone hides whether the run was actually usable.

Practical tips to get faster

  • Look at the screen, not the keyboard. Touch typing — keeping your fingers on the home row and your eyes on the passage — is the single biggest speed gain. The green/red feedback lets you catch errors without glancing down.
  • Prioritize accuracy first. Speed follows accuracy, not the other way around. Slow down until you are above 95%, then gradually push the pace.
  • Don't pause to fix every typo. The test scores the characters you produce; constant backspacing can cost more time than a small accuracy hit. Build a smooth forward rhythm.
  • Practice the hard level for punctuation. If your everyday writing involves code or formal text, drill the hard passages so capitals and symbols stop breaking your flow.
  • Warm up. Your first run of a session is usually your slowest. Do an easy passage to loosen up before testing yourself for a real score.

Common mistakes when reading your score

  • Comparing WPM across difficulties. A score on the easy set is not comparable to one on the hard set. Track each level separately over time.
  • Ignoring accuracy. A high WPM with low accuracy is not a real-world result. Treat the two numbers as a pair.
  • Chasing a one-off best. Speed varies run to run with fatigue and unfamiliar passages. Your typical score across several attempts is a truer measure than a single lucky peak.

The whole test runs in your browser — passages, timing, and scoring are all computed locally, so nothing about your typing is uploaded anywhere.

よくある質問

{# Alpine.js — self-hosted. (The previous jsdelivr CDN tag had a stale SRI integrity hash, so the browser refused to run it and window.Alpine was never defined — silently breaking every FAQ accordion and Alpine tool.) #}