'%20stroke-width='24'%20opacity='0.3'/%3e%3c!--%20Inner%20crosshair%20ring%20--%3e%3ccircle%20cx='256'%20cy='256'%20r='90'%20fill='none'%20stroke='url(%23bg)'%20stroke-width='20'%20opacity='0.6'/%3e%3c!--%20Center%20dot%20--%3e%3ccircle%20cx='256'%20cy='256'%20r='28'%20fill='url(%23bg)'/%3e%3c!--%20Crosshair%20lines%20--%3e%3cline%20x1='256'%20y1='56'%20x2='256'%20y2='156'%20stroke='%237c3aed'%20stroke-width='20'%20stroke-linecap='round'/%3e%3cline%20x1='256'%20y1='356'%20x2='256'%20y2='456'%20stroke='%2306b6d4'%20stroke-width='20'%20stroke-linecap='round'/%3e%3cline%20x1='56'%20y1='256'%20x2='156'%20y2='256'%20stroke='%237c3aed'%20stroke-width='20'%20stroke-linecap='round'/%3e%3cline%20x1='356'%20y1='256'%20x2='456'%20y2='256'%20stroke='%2306b6d4'%20stroke-width='20'%20stroke-linecap='round'/%3e%3c/svg%3e)
Free Online Keyboard Tests
Keyboards fail in ways that are not always obvious. A single key may drop inputs only occasionally, the spacebar may start repeating presses, or the fault may not be one key at all but a combination: you hold three keys to strafe diagonally while jumping and one of them simply never arrives. The tests in this section cover those cases, from checking each key individually to spotting ghosting, examining spacebar behaviour and measuring how fast you press in keys per second.
The common mistake is blaming the game when the limit is in the hardware. Plenty of membrane keyboards only register a few simultaneous presses in certain areas of the layout, which is why the failure always shows up with the same key combination and never with others. Start with the ghosting test before rebinding blindly: once you know where the ceiling is, moving one action to a different key fixes the problem in seconds. For speed, measure several times across different sessions, because hand fatigue shifts your score far more than any keyboard setting will.
What order to run these tests in
The order runs from the binary to the measurable. First confirm the keyboard registers what you press, then that it handles simultaneous presses, and only then does measuring your speed make sense. Testing KPS with a dead key gives you a personal number that actually describes the keyboard.
- 01 Check every key Work through the whole board, including keys you never use in game. A key that fails to register is usually dirt under the keycap, and spotting it saves you blaming yourself.
- 02 Run the ghosting test Press three or more keys at once, like strafing and jumping while you reload. That is exactly where membrane keyboards start dropping inputs without any warning.
- 03 Measure your KPS Once the board is fault-free, measure how many keypresses per second you reach. Repeat the run a few times: the first attempt is almost always worse because your hands are cold.
- 04 Test the spacebar If you play platformers or rhythm games, test the spacebar on its own. It is the largest key and the one most likely to sit crooked, failing at the edges while the centre works.
Reference values
These figures tell you whether the keyboard is healthy and where your speed sits. The first two rows are binary and allow no margin. The KPS rows vary a lot depending on the game and the switch type.
| Parameter | Usual value | Notes |
|---|---|---|
| Unresponsive keys | 0 | A single dead key already shapes how you have to bind your controls |
| Ghosting on 3 keys | None with NKRO | Membrane boards usually fail here; mechanical ones with NKRO do not |
| Average KPS | 5-7 | Normal range for someone who types fast but does not train for it |
| Regular gamer KPS | 8-12 | Reached through practice, not by owning an expensive keyboard |
| Keyboard polling rate | 1000 Hz | Below that you barely notice it when typing, but you do in rhythm games |
Frequently asked questions
What is the difference between ghosting and rollover?
Rollover is how many simultaneous keys your board can report. Ghosting is the symptom when you exceed that limit and a press goes missing, or a key you never touched registers instead.
Do these tests reveal hardware faults or only software ones?
They show what reaches the operating system. If a key never appears in the test, the cause is usually physical or firmware related. If it appears but fails in game, check your bindings and layers.
Do they work the same on mechanical and membrane keyboards?
Yes, though the results differ. Mechanical boards usually handle more simultaneous presses, while membrane models tend to show ghosting sooner and on very specific key combinations.