Output
Held keys; transitions; repeat intervals
UserBenchmark / All Tools / Rapid Trigger Test
Keyboard
Rapid Trigger Test
Measure time between release and retrigger of a key.
Free to useNo downloadNo sign-up
Rapid Trigger Test · At a glance
Quick answer: Measure time between release and retrigger of a key. The browser records state transitions, not the physical distance of a Hall-effect switch.
Rapid Trigger Test
The test loads when you open it. Device access is requested only after you choose to start.
Detailed guide
How to use this tool
- Press, release and press the same key again.
- Inspect the observed interval between release and retrigger.
Input
Focused physical key presses
Browser requirement
KeyboardEvent.code; keydown and keyup
Processing
Runs on your device; no tool-result upload
How it works and what the result means
The tester records browser key-down and key-up events, tracks held keys, and separates operating-system repeats from fresh presses. Short intervals are clues to investigate, not proof of a defective switch.
Reading the result
The browser records state transitions, not the physical distance of a Hall-effect switch. A short interval does not reveal actuation depth.
What to check next
Use deliberate separate movements first. Keyboard firmware may change when transitions are reported.
System shortcuts and some special keys are intercepted before a web page receives them. USB polling frequency, analog actuation distance and physical rapid-trigger settings cannot be read from keyboard events.
Frequently asked questions
Can it measure rapid-trigger distance in millimeters?
No. Browser key events contain no analog travel measurement. Use the manufacturer tool or a physical instrument for distance settings.
How do I start the Rapid Trigger Test?
Click the test area to focus it, then press and release the keys you want to inspect. Try simultaneous combinations for a ghosting check.
Does this tool require a download or an account?
No. Open the interactive tool above in a modern browser. The instructions and explanations are available even with JavaScript disabled; running a test needs JavaScript.
Why can two attempts give different results?
Power settings, background tasks, browser scheduling, operating-system input processing and device settings affect measurements. Compare repeated attempts with identical settings rather than the single highest score.