Short answer: pick the tool by the symptom. A mouse button that does nothing or does the wrong thing goes to the mouse test; one click that turns into two goes to the double-click test; a key that sticks, repeats or does not register goes to the keyboard test. The click-speed, reaction, aim and typing tools measure you, not a fault. Every tool reports what reaches your browser, and none of them certifies hardware.
If a mouse is misbehaving
- A button does nothing, or the wrong button fires. Use the mouse test to see which button events reach the page. Guides: test every mouse button and a button not registering clicks.
- One click becomes two. Use the double-click test. Guides: the 60-second check, intermittent chatter and how to fix a double-clicking mouse. If you may need a repair or a return, see proving chatter for a warranty or RMA claim.
- Items drop while you drag. Use the mouse drag test and read mouse drops items while dragging.
- The scroll wheel skips, stutters or goes the wrong way. Use the scroll wheel test. Guides: skipping or stuttering and scrolls the wrong way or jumps.
If a keyboard is misbehaving
- A key does not register, or you are not sure which key you pressed. Use the keyboard test. Guides: which key am I pressing and a dead or sticky key.
- A key types twice. Use the keyboard test and read a key that types twice.
- The spacebar double types or misses presses. Use the spacebar test and read spacebar double typing or missing presses.
If you want to measure yourself
These tools do not look for faults. They record how you perform on a timed task, and runs stay on your device.
- CPS test and clicks-per-minute test: click speed over a duration you choose. To improve, read how to increase click speed; to compare runs fairly, read how to track your click speed over time.
- To test right and middle button speed, read the right-click CPS guide.
- Keyboard counter: keys pressed in a timed run.
- Reaction time test: milliseconds between a signal and your click, including display and input latency.
- Aim test: hits, misses and accuracy over 30 seconds.
- Typing test: words per minute and accuracy.
If you are not sure where to start
For a new device, follow the ordered checklist in how to test a new mouse or keyboard before the return window closes. If a result looks odd, see why your input test got interrupted and same input, three browsers: what matched, since browser and system settings change what reaches the page. Your runs are kept in local History; see how to read and share your exported report.
What none of these tools can tell you
A browser sees the input events that reach the page. It does not measure the sensor, polling rate, DPI accuracy, click latency, wireless dropouts, battery life or build quality, and a clean run does not certify the hardware. On polling rate and DPI specifically, read what a browser reports about polling rate and what a DPI analyzer page really measures. The counting rules and limits are in how we test.
These tools record real events observed in your browser. Results differ by browser, operating system and connection type.