100 Second Spacebar Test

One hundred seconds is one minute and forty seconds, so this duration includes substantially more sustained input than a quick baseline. Start when ready with the first valid input. The window has a fixed endpoint and includes your quiet time as well as active pressing. It is a specific comparison interval, not a promise of improved performance or a universal endurance threshold.

Final average CPS divides the total by one hundred. A total of 420 accepted presses means 4.20 CPS, and one additional event changes the average by 0.01 CPS. That arithmetic makes the result easy to read, but does not give it greater physical accuracy. Browser delivery and scheduling still influence the events observed inside the window.

An early burst forms only a small portion of this attempt. Several later pauses can reduce the final average even when the peak one-second metric remains high. Use the result to describe the total delivered input, not to infer why the pace changed. A complete pacing chart is available on the endurance tool with its supported durations if you need segment-level observations.

Do not rank a hundred-second total directly against a minute or two-minute count. Their windows contain different amounts of time. Repeat the same duration, keyboard, browser, and input approach for a personal comparison. If you switch to sixty or one hundred twenty seconds, include that duration in your notes so the difference in observation conditions remains visible.

Keep the window visible and active, and release Space between presses. Auto-repeat is excluded from independent input. Focus loss interrupts the run, so reset rather than presenting a partial attempt as a completed hundred seconds. Pad attempts are labeled separately and cannot be submitted as physical-keyboard leaderboard runs. Copying or explicitly submitting a finished result is optional; a local total alone is not an accepted record.