120 Second Spacebar Test

The one hundred twenty-second counter covers two full minutes from your first accepted input. It gives later changes in rhythm and pauses much more influence over the average than a sprint. There is no need to chase the opening peak throughout the run. Make ordinary separate presses, and choose another duration when a shorter observation better fits your purpose.

At completion, divide the count by one hundred twenty to get average CPS. Six hundred accepted inputs means 5.00 CPS. Quiet time remains in that denominator. A high peak one-second metric can coexist with a lower two-minute average, and a larger total than a shorter attempt does not by itself mean a faster input rate.

This counter provides a long fixed total and the standard result workflow. The endurance page’s two-minute option adds an entire sequence of per-second buckets, including zero-input seconds, and opening-to-closing comparisons. Use those metrics when you need to locate pace changes. Neither tool can determine the physical reason for a pause or diagnose a user’s health from input timing.

Repeat with the same input device, browser, and duration. A hundred-second result stops twenty seconds earlier and should remain a separate group. A sixty-second test contains only half this observation time. Label duration in share text and compare public accepted records with the two-minute rules. The browser result is practical input evidence rather than a laboratory measurement.

Losing window focus or hiding the tab interrupts an active attempt. Reset before another run so the new total begins from zero. Space auto-repeat while held is not counted as independent pressing, and pad input does not become a physical-keyboard record. Inspect the completed result before an optional explicit submission. For release or repeated-event concerns, use the keyboard diagnostic pages instead of drawing conclusions from the long-run score.