Key name, keyCode, code, hold time, combos and interval spread - all appear the moment you press. Then time your reaction and check shortcut detection. The whole board runs in your browser.
Everything stays in this browser on your device. Nothing is uploaded and there's no account. Switching browsers or clearing site data will lose it; use Clear my data in the footer to delete it for good.
Pressed keys glow amber; on a narrow screen, swipe sideways to see the whole board.
Each press records the gap since the last one and drops it into a bucket. Type a short burst to see where your rhythm lands.
| Detection | Any keydown / keyup the browser receives: key name, numeric keyCode, physical code and modifier state |
|---|---|
| Combo rule | Two presses less than 350 ms apart count as a fast combo; consecutive fast presses build a streak |
| Histogram | Six buckets: <100 / 100–200 / 200–300 / 300–500 / 500–1000 / >1000 ms |
| Processing | Computed entirely in the browser; stats written to this device's localStorage, never uploaded, no account |
| Limits | The report keeps the latest 60 key events; histogram and counters live only on this device and vanish if site data is cleared |
| Known edges | Combinations claimed by the OS or browser (Ctrl+W, Cmd+Tab) cannot be seen; some IMEs report keyCode 229 during composition; key repeat records only the first press |
Click anywhere on the page first so the window has focus. If focus sits in an input, keys go to that field instead. Shortcuts such as Ctrl+W or Cmd+Tab are claimed by the browser or OS and cannot be captured - try an ordinary key instead.
keyCode is a legacy number that varies across browsers and input methods, and MDN marks it deprecated. code identifies the physical key: KeyA is always the A key on the home row, regardless of layout or IME. Use code for shortcuts and keyCode only for old code.
Two presses less than 350 milliseconds apart count as one fast combo, and consecutive fast presses build a streak. The interval histogram uses 100/200/300/500/1000 ms buckets. The reaction test names a random key and times how long it takes you to press it; your personal best is saved locally.
No. Every statistic is computed in your browser and stored only in this device's localStorage. No requests are sent and there is no account. Switching browsers or clearing site data removes it; use Clear my data in the footer to delete it deliberately.