⌨ Keyboard Tester

Spacebar Test: Counter and Presses Per Second

The tool opens in Spacebar mode with the space key highlighted. Every press increments the counter and updates your presses-per-second rate; the page will not scroll while you do it. Tap the bar in different spots — left corner, centre, right corner — to find dead zones a normal typing test would never expose.

Presses: 0Elapsed: 0.0sRate: 0 presses/sTimer runs from your first press to your latest press.

Tab, Space, the arrows and the F-keys are captured here so you can test them. Keyboard-only users: press Tab twice in a row — the second press goes through and moves focus to the controls and links as usual.

Spacebar counter

Tap the spacebar as fast as you can. Rate = (presses − 1) ÷ seconds between your first and latest press, so it needs at least two presses to show a number. Chatter on the spacebar shows up here as an impossibly high rate — cross-check with the Chatter tab.

0
presses
0.0s
elapsed
0
presses/s

Why the spacebar deserves its own test

The spacebar absorbs more presses than any other key on the board, and it does so with the most fragile mechanism. The reason is simple arithmetic: if an average English word runs about five characters, then one space follows roughly every five keystrokes — around 17% of everything you type, more than the letter E and more than any other single key. Both thumbs hit it, usually harder than they hit letters, and the cap is six or seven units wide, so it needs a stabiliser bar to stay level. Heaviest use plus the most mechanical parts is why spacebars go bad first.

A general key test only asks "did this key ever register?" — and a failing spacebar answers yes, because it still works when you hit the sweet spot in the middle. The two failure modes that actually annoy people are positional (one end of the bar does nothing) and intermittent (one press produces two spaces). Neither shows up as a dead key. Both show up here, in the counter.

Reading the presses-per-second number

The rate is plain arithmetic, labelled so you can check it: rate = (presses − 1) ÷ seconds between the first and latest press. The useful trick is converting that rate back into a millisecond gap, because milliseconds are the language switch faults speak.

Average gap = 1000 ÷ rate (arithmetic conversion, not a benchmark or a score table). The reading column is interpretation guidance, not measured population data.
Rate shownAverage gap between pressesHow to read it
2 / s500 msRelaxed, deliberate tapping — the right pace for a reliability check
5 / s200 msFast single-finger tapping; still comfortably above any chatter window
8 / s125 msHard to sustain with one finger; fine, but the gaps are getting short
12 / s83 msRealistically needs two fingers alternating — a single thumb rarely gets here
20 / s50 msUnder the 80 ms chatter threshold: verify in the Chatter tab before believing the number

That last row is the whole point of pairing a counter with a gap threshold. A doubling switch inflates your rate for free, so an unexpectedly impressive score is evidence of a fault at least as often as it is evidence of fast fingers.

Worked example: 20 taps that counted as 41

A user complains about stray double spaces in documents — "hello  world" with no obvious cause. Procedure: tap the spacebar exactly 20 times, counting out loud, at a relaxed pace of about two per second. Result on screen: 41 presses, 9.8 s elapsed, 4.1 presses/s. Running the formula backwards, (41 − 1) ÷ 9.8 = 4.1 — the maths is right, so the browser really did receive 41 keydown events for 20 physical taps. Switching to the Chatter tab and repeating the run flagged Space at gaps of 19, 24 and 31 ms. Diagnosis: contact bounce escaping the firmware's debounce window, not a typing habit. The full method and the fix list are on the keyboard chatter test.

Worked example: the dead left corner

A different complaint: spaces "sometimes" get missed while typing, but the key feels normal. Procedure: three runs of 30 presses each, hitting a different part of the bar each time, resetting between runs. Result: centre 30 of 30, right corner 29 of 30, far-left corner 11 of 30. A switch that registers 100% of centre presses is not electrically dead, so the problem is transmission — the stabiliser is not carrying an off-centre press down to the switch. On a mechanical keyboard, popping the cap and reseating (and lightly lubricating) the stabiliser wire usually restores it; on a laptop or membrane board, the scissor clip under one end has typically broken, which means a keyboard replacement. Laptop-specific triage lives on the laptop keyboard test.

How to run a spacebar test that means something

  1. Reset first. The counter is cumulative; a clean run starts from zero.
  2. Count your own taps. The number in your head is the control group — without it, the counter has nothing to disagree with.
  3. Test three positions. Left end, centre, right end, 30 presses each. Positional faults hide from any single-position test.
  4. Tap slowly for reliability, quickly for chatter. Slow taps expose missed presses; fast taps expose doubled ones.
  5. Cross-check anything odd in the Chatter tab, where the actual millisecond gaps are listed instead of an averaged rate.

If other keys behave strangely too, test the whole board on the main keyboard tester before blaming the spacebar — and if spaces drop out only while you are holding movement keys in a game, that is a rollover limit rather than a spacebar fault, which the key rollover test will confirm in about ten seconds.

Frequently asked questions

Why does the rate stay at 0 after my first press?

Because a rate needs an interval, and one press has none. The timer starts on your first press, so the counter shows presses and elapsed time immediately but the rate only appears from the second press onward. The formula is (presses − 1) ÷ seconds — measuring the gaps between presses rather than dividing by a fixed clock, so you can start whenever you like without a countdown penalising you.

Does the page scroll while I hammer the spacebar?

No. Space normally scrolls a web page, so the tester calls preventDefault() on it (and on the arrow keys) while you are not typing in a form field and not focused on a button or link. The press is still counted first and only the browser's scrolling reaction is suppressed, which is why the counter keeps climbing while the page stays still. Tab works the same way with one exception: pressing it twice in a row releases it, so keyboard users can always move focus off the tester.

My spacebar works in the middle but not at the edges. Is that a real fault?

Yes, and it is one of the most common spacebar complaints. A spacebar is a long keycap balanced on a stabiliser bar so that an off-centre press still pushes the single switch underneath. When a stabiliser wire pops out of its clip, gets bent, or loses its lubrication, one end of the cap tilts instead of transmitting the press. The switch is usually fine; the mechanism holding the cap is not.

Can this page measure my typing speed?

No — it counts spacebar presses only, not words per minute. The two are related (a space follows nearly every word) but a WPM test measures accurate character entry, while this measures how fast and how reliably one key registers. Use this to judge the key; use a typing test to judge your typing.

Is a high presses-per-second number good?

Not by itself. Above roughly 12 presses per second the gaps between presses drop under about 80 ms, which is the same territory the chatter detector treats as suspicious. If a number looks impossible for what your finger actually did, that is the signal to check for a doubling switch rather than to celebrate a score.