How to Test Your Keyboard Online: Check Dead Keys, Ghosting, Chatter, and Latency
Updated
Open keyboardtest.io in a modern browser and press each physical key while watching the on-screen layout. That single pass tells you whether any key is dead or unresponsive. From there, the same page lets you check multi-key rollover (ghosting), switch chatter (double-clicking), and input latency — no drivers or software installation required, and all testing runs locally in your browser.
Before You Start
- Use a Chromium-based browser or a current Firefox/Safari build so the high-precision timing APIs the tool relies on are available.
- Close apps that grab global hotkeys (screen recorders, macro utilities, game overlays) so they don't swallow your keypresses before the page sees them.
- If you're testing a laptop, decide whether you want the built-in keyboard or an external one — test only one at a time.
Step 1: Basic Function Test (Dead Keys)
- Look at the virtual keyboard on the page. Every key starts in an "Untested" state.
- Press each physical key once, one at a time.
- Watch the corresponding on-screen key. It should change to "Tested," and flash "Pressed" while you hold it.
Expected result: every key you press lights up and stays marked as tested.
If a key doesn't light up:
- Try it a second time — a single missed press can be a timing fluke.
- Test the same key on another device or with another keyboard to confirm whether the fault is the switch or the connection.
- On a mechanical board, a key that never registers usually means a failing switch or a broken trace; on a membrane board it often points to worn contact pads.
Step 2: Rollover and Ghosting Test (NKRO)
N-Key Rollover means the keyboard registers every key you press simultaneously. Cheaper or older keyboards may only handle 6KRO, and some drop keys entirely under complex input — that's ghosting.
- Press and hold a realistic gaming cluster, e.g. W + A + S + D + Space.
- Add more keys (Shift, Ctrl, another letter) while holding the first set.
- Watch which keys light up on the virtual board.
Expected result: all held keys stay lit at once. The page supports both 6KRO and NKRO testing.
If some keys don't light up: your keyboard is hitting its rollover limit or blocking combinations. This matters most for games that need many simultaneous inputs; for typing it rarely causes problems.
Step 3: Chatter / Double-Click Detection
Chatter is when a single physical press registers as two or more inputs — a common sign of an aging or dirty switch.
- Open the Chatter Test.
- Type normally on the keys you suspect (often the most-used letters or your spacebar).
- Let the high-sensitivity detection algorithm flag any abnormal secondary triggers.
Expected result: one press = one registered input.
If the tool flags repeated triggers: the switch is double-clicking. On a mechanical keyboard this usually means the switch is near end of life or needs cleaning/resoldering; on a hot-swap board you can simply replace the switch.
Step 4: Input Latency Test
Latency here measures the delay from the system event to the browser, based on event timestamps — useful if you're chasing input lag for gaming.
- Open the Latency Test.
- Press keys repeatedly as instructed and read the reported latency figures.
Expected result: consistent, low numbers with little variation. Large or erratic spikes suggest something in the chain — USB polling, background load, or the browser — is adding delay.
Note that this measures system-to-browser latency, not the full end-to-end latency of a game. Use it to compare configurations (different ports, polling settings, background apps) rather than as an absolute figure.
What the Specs Mean
| Term | What it tells you |
|---|---|
| NKRO / 6KRO | How many keys can be registered at once |
| Ghosting | Keys that fail to register under simultaneous presses |
| Chatter | One press registering as multiple inputs |
| Polling rate | How often the keyboard reports to the PC |
| Input latency | Delay between your press and the system/browser registering it |
Troubleshooting
- Nothing lights up at all: click inside the page first so it has focus, then check the browser isn't blocking the page.
- A key works elsewhere but not here: another app may be capturing that key as a shortcut.
- Inconsistent results: retest with background apps closed; timing APIs are sensitive to system load.
- Privacy: all tests run locally in your browser — the tool states it does not record your key content or upload input data.
Run the four steps in order — function, rollover, chatter, latency — and you'll have a complete picture of whether your keyboard has dead keys, ghosting, switch chatter, or lag before you decide to repair or replace it.