Spacebar Counter

How to use the spacebar counter

A spacebar counter is a small speed test: you press the space bar as many times as you can before the time runs out, and it counts every press. This one also works out your presses per second, draws a chart of each second, and remembers your best score for every time limit.

1. Pick a time limit: 5, 10, 30 or 60 seconds, a custom time, or Untimed. Ten seconds is the default.
2. Rest a thumb or finger on the space bar while the counter is on screen. On a touchscreen, get ready to tap the big box instead.
3. Press and release Space as fast as you can. Your first press starts the timer and counts; holding the key down counts only once.
4. When the time is up, read your total, your presses per second and the per-second chart. A timed run also updates your personal best.

While a run is going, Space belongs to the counter: the page does not scroll and no other button reacts. Before a run, Space starts counting when the big box has focus or when nothing else on the page has focus and the box is in view, so you can still scroll this article with the space bar once the counter is off screen. Esc or the Stop button ends a run early. A timed run you stop early is not saved; an untimed run is saved when you stop it.

Which time limit to pick

Each time limit tests something a little different. Short runs measure your top speed; long runs measure how well you keep it up.

How presses are counted

A spacebar counter is only as good as its counting rules. These are the ones this counter uses, and why:

• A press is the key going down. The counter listens for the moment the space bar is pressed, not released, so a press counts the instant you make it.
• Holding the key counts once. If you hold a key, your computer starts repeating it automatically. Browsers mark those extra events as repeats, and the counter ignores them. It also checks for itself that the key came back up since the last press, in case a browser or remote connection forgets the mark. Ignored repeats are shown in the results as held-key repeats ignored.
• Shortcuts are left alone. Space with Ctrl, Alt or Cmd is a shortcut for your system, not a press, so it is not counted. Enter does not count either.
• Every press is stamped with its own time. Browsers record when each key or touch event happened on a high-resolution clock. The counter uses that stamp, so a moment of slowness on the page cannot push a press past the end of the run.
• The first press starts the clock. It counts as press number one. A press counts if it lands before the time limit; the first press at or after the limit does not count and ends the run.
• One second of rest after a run. Presses are ignored for 1 second after a run ends, so the tail of your burst does not start a new run by accident.
• Leaving the page stops the run. If you switch windows or tabs, key presses can no longer reach the page, so a timed run is stopped and not saved rather than recorded with a wrong count.
• Space and taps are kept apart. A run counts the input that started it. Taps during a Space run, or Space during a tap run, are ignored, and each input has its own personal bests.

The box changes color only when a run starts and when it ends. Each press moves a small key drawing and changes the number, with no flashing, however fast you go.

Presses per second: the math

Your total depends on the time limit, so the counter also gives a rate that you can compare across limits:

presses per second = presses ÷ seconds

timed run:   seconds = the time limit
untimed run: seconds = from your first press to Stop

During a run the same division uses the time so far, and it appears after the first full second, since a single press divided by a few milliseconds would read as hundreds per second. The table works through some example runs. They are made-up numbers to show the arithmetic, not averages or targets:

The results also show your fastest second, the busiest one-second slice of the run, and 2nd half vs 1st, how your pace in the second half compares with the first. If the 10-second run above had 34 presses in the first five seconds and 28 in the last five, the second half was 18% slower: 28 ÷ 34 − 1 ≈ −0.18. Runs longer than a minute are charted in wider slices (2, 5, 10 seconds or more) so the chart never has more than 60 bars, and each bar still shows presses per second.

The same pace gives very different totals at each time limit:

Real long runs usually come in below these straight-line totals, because almost nobody holds their 5-second pace for a whole minute.

What is a good spacebar score?

Honestly, there is no official answer. No standards body defines a spacebar test, and we could not find an official, verified world record. The “average” and “record” numbers you see quoted online are self-reported scores from different websites, each with its own counting rules, on keyboards nobody measured. Some count held-key repeats; some start the timer on a countdown instead of your first press. Those numbers cannot be compared fairly with each other or with this counter, so this page does not quote them.

What you can compare fairly:

• Your own personal bests for the same time limit, on the same keyboard. The Personal bests table above keeps one for each time limit and input.
• Presses per second, to compare a 10-second run with a 30-second run, keeping in mind that longer runs give lower rates.
• Friends on the same device. Taking turns on one keyboard removes the hardware difference.

Why longer runs give lower rates is well studied for finger tapping. In a 2024 study of 194 young adults (18 to 30) and 176 adults aged 50 to 70 (Heimhofer and colleagues), people tapped a phone or tablet screen as fast as they could with one finger for 30 seconds at a time. Tapping speed fell steadily during every trial, in both age groups and for every finger, by about 17% on average from the fastest to the slowest part. That was tapping on a screen, not pressing a space bar, so treat it as a reason to expect a slowdown, not as a target. Your own 2nd half vs 1st figure shows how much you slow down.

Why results differ between keyboards and devices

A spacebar score measures you and your hardware together. The same person can score quite differently on two keyboards:

• The key itself. Space bars differ in how far they travel, how stiff the spring is and how the stabilizers under a long key behave. A shorter, lighter key is easier to press quickly.
• How the keyboard reports presses. A keyboard checks its keys at regular intervals and filters out the tiny electrical bounce of each switch. Two extremely fast presses can be merged into one, and a worn switch can occasionally report one press as two.
• Wireless connections. Wireless keyboards can delay key events or deliver them in bunches, especially with a weak signal or low battery.
• Touchscreens. Each tap needs your finger to lift fully before the next one, and screens differ in how quickly they sense a touch. That is one reason taps are counted separately.
• The browser and computer. Key events arrive in order, but a busy computer can deliver them late. The counter uses each event’s own timestamp, so late delivery does not move a press across the deadline, but closing heavy tabs still helps.

None of this makes a score wrong; it makes it yours, on that device. Note which keyboard you used when you compare, and treat a big jump after changing keyboards as the keyboard, not you.

How to press the space bar faster

• Press lightly and stay close. Push only as far as the key needs to register and let it spring back. Lifting high between presses wastes time.
• Relax. A tense hand and arm tire quickly. Keep your wrist loose and supported.
• Press near the middle of the bar. The ends of a long key can wobble or bind on some keyboards.
• Try two thumbs or two fingers. Alternating between two digits lets each one rest half the time. Agree with friends on the rules before you compare.
• Warm up, then rest. Do a short 5-second run first, and rest a minute between serious attempts.
• Pace long runs. In a 30 or 60-second run, start a little below your top speed; the chart shows whether you faded.

Take care of your hands. Hammering a key for long stretches can strain your fingers, wrist or forearm. Stop if it hurts, and keep long runs occasional. This counter is a game, not a fitness or medical test.

Tap and click mode, and CPS tests

On a phone or tablet there is no physical space bar, so you can tap the big box instead. With a mouse or trackpad, clicking the box works the same way, which turns the counter into a click speed test. Each finger that touches the screen counts, so you can alternate two fingers; with a mouse, only the main button counts.

Taps and clicks are counted as a separate Tap/click input, with their own row in the Personal bests table, because tapping glass and pressing a key are different tasks. The per-second number is the same idea as a CPS (clicks per second) score: presses divided by seconds. Screen readers can also activate the box like any button, and each activation counts as a tap.

Private by design

• Nothing is uploaded. The page’s Content-Security-Policy only allows connections back to this site, and the counter makes none. Open your browser’s Network panel and do a run: no request appears.
• Your results stay on your device. Settings, your last 50 runs and your personal bests are kept in your browser’s local storage under one key. Download them as a CSV file, or remove them with Clear saved results.
• No account and no cookies. Once the page has loaded the counter even works offline.

Sources

• W3C, UI Events (Working Draft, 21 February 2026): keydown, the repeat attribute for held keys, and canceling a key’s default action.
• W3C, Pointer Events: one pointerdown per finger, pen or mouse button press.
• W3C, High Resolution Time: the clock behind event timestamps.
• MDN Web Docs: KeyboardEvent.repeat, KeyboardEvent.code and Event.timeStamp.
• Heimhofer C, Neumann A, Odermatt I, Bächinger M, Wenderoth N (2024). Finger-specific effects of age on tapping speed and motor fatigability. Frontiers in Human Neuroscience 18:1427336 (full text on PubMed Central): the slowdown during 30-second tapping trials.
• W3C, Web Content Accessibility Guidelines (WCAG) 2.2: keyboard operation, target size and the three-flashes rule the counter follows.

Reviewed by microplugins · Last updated October 2026