Use this guide when the Spacebar Clicker Test reports an unexpected score. Start with the counting and timing rules before blaming the keyboard or buying hardware. The examples below are arithmetic illustrations, not measured hardware benchmarks.
Holding Space only counts once
The test counts deliberate Space keydown events and ignores browser repeat events. Press and release for each new count. Holding the key down produces repeated browser events, but those do not become extra presses. This prevents operating-system repeat settings from deciding the score.
If Space appears unresponsive, click the test area and check focus. Input fields and other interactive controls handle their own keys. On touch devices, use the test's on-screen control and compare those runs separately from physical-keyboard results.
Check the mode before comparing CPS
For a completed timed run, average CPS equals accepted presses divided by the selected active duration. For example, 42 presses in a 10-second test gives 4.2 CPS. The average interval display is 1000 / 4.2, approximately 238.1 milliseconds; it is derived from CPS, not a measurement of keyboard latency.
The 100-click sprint ends at the target press count and divides by elapsed active time. A hypothetical 100 presses over 20 seconds gives 5 CPS. The first press starts the clock and is counted, so very short runs are sensitive to the start convention. Compare like modes and durations.
Peak CPS and average CPS answer different questions
Peak CPS is the largest rolling one-second count observed during the run. Average CPS covers the complete active run. A short burst can produce a high peak while pauses reduce the average. Neither number is a population percentile or a universal ranking.
For a consistent comparison, select one mode, use one input method, keep the page visible and repeat a small set of runs with rests between them. Record every result rather than selecting only the highest. Fatigue and technique can change the result even on the same device.
Switching tabs pauses this test
When the document is hidden, the test pauses its clock and resumes when visible again. Time spent in another tab therefore should not be treated as active test time. A phone stopwatch that includes a background break will disagree with the test by design.
Use an uninterrupted visible run when checking timing. Avoid treating scores gathered with different pause patterns as a controlled comparison.
Why a best score or history entry disappears
Personal bests are stored per mode in the current browser. Recent history retains the latest ten completed runs. Changing the duration selects a different best-score record; changing browser, using private browsing or clearing site storage can remove access to old results. There is no account-based synchronization.
Before changing devices, use the result-copy or download controls if you need to keep a record. A screenshot should include the mode, accepted presses, active elapsed time, average CPS and input method so another result can be compared fairly.
When to check the device
If a complete press-and-release cycle still fails to count, first test the same key in a plain text field, then repeat a short run in another browser. Check whether the problem follows the device or only the page. These checks isolate a symptom; they do not prove a switch type is faster.
For an untimed tally, use Spacebar Counter. For upgrades and automatic points, use Spacebar Clicker; that game's point total is not a raw CPS test result.