Check the connection and selected device, then repeat the failed check: holding space changes the score.
Part of the CPS test. Run the full cps test first for a complete device check.
Holding Space changes the score The page scrolls during a run Presses are missing
Spacebar CPS test
Run the CPS clock from physical Space key presses while ignoring browser key-repeat events.
Also known as: spacebar cps test, space bar speed test, spacebar speed test, spacebar counter, space bar test. Free, online, and no download required.
No permission neededNothing uploaded
Press Space once to start the selected timer.
01
What the spacebar CPS test checks
| Check | How it is measured | Fails when |
|---|---|---|
| Physical presses | Space keydown counts only when repeat is false. | Holding the key inflates the total. |
| Timer | The first valid press starts performance.now. | Page load time enters the result. |
| Rate summary | Total, peak one-second window and bucket spread are calculated. | Fewer than three presses arrive. |
If something failed
Check the connection and selected device, then repeat the failed check: the page scrolls during a run.
Check the connection and selected device, then repeat the failed check: presses are missing.
02
How to read the result
How the spacebar cps test works
The spacebar mode uses event.code equal to Space and rejects repeat events. While the pad is focused, the handler prevents page scrolling and forwards each valid physical press to the same ref-based CPS accumulator. History and share data retain the input mode so mouse and spacebar runs cannot be confused.
What the result can establish
Focus the pad before starting, release the key between presses and compare only runs with the same duration and keyboard.
Measurement limits
Operating-system keyboard processing and browser focus affect which presses arrive. The score is a speed task and does not establish switch quality.
03
Spacebar CPS test questions
Does holding the key raise the score in a space bar speed test?
No. Keydown events with repeat set to true are rejected outright, so only real physical presses count. Holding the spacebar produces a stream of repeat events that the counter ignores completely.
Why does the page not scroll during the spacebar test?
While the pad has focus, the handler prevents the default scroll that Space normally triggers. Move focus away from the pad and Space scrolls the page again, so the suppression never leaks into the rest of the site.
Is this spacebar counter comparable to a mouse CPS run?
Only loosely. The clock and duration options are shared, but a keyboard switch, its travel and its actuation point behave differently from a mouse button. Every stored run records its input mode so the two can never be confused in your history.