Skip to content
Testpartout

Human performance · Clicking

Click Speed Test

This click speed test measures how many times you can click in ten seconds, and converts that into clicks per second. It runs entirely in your browser: your first click starts the timer and counts as click one.

When the ten seconds are up the test reports your total clicks and your CPS, and keeps your best result on this browser so you can see whether you are actually improving.

  • 10-second session
  • Clicks per second
  • No permissions required

This measurement requires a mouse, touchscreen or pen: only pointer presses are counted, and keyboard keys deliberately produce no score. Right-click, middle-click and secondary contacts are ignored. The ten seconds start with your first accepted press, not when the page loads.

Session in progress

Not started
Clicks per second
—
Total clicks
0
Duration
10s
Input method
—

Set by your first pointer press

Personal best
—

Saved in this browser after your first completed session

Only your best clicks-per-second result, its click count and the pointer type it was measured with are stored in this browser. Nothing is uploaded.

Your result

What your result means

Clicks per second is simply your accepted clicks divided by the elapsed seconds of the session. Because the window is fixed at ten seconds, the number is dominated by how evenly you can sustain a rhythm rather than by a short burst at the start.

Click speed is a physical measurement of you plus your hardware. A mouse with a light switch, a trackpad, a touchscreen and a worn button all produce different results from the same hand, so the useful comparison is against your own previous sessions on the same device.

  • Ten seconds is long enough that pacing matters. Starting at maximum speed and fading usually scores lower than a steady rhythm.
  • Technique can change the rate: alternating fingers spreads the movement differently from single-finger tapping, and a touchscreen limits contact differently from a mouse switch.
  • A worn or double-clicking mouse button can register extra clicks. If your CPS suddenly jumps, run the mouse test before believing it.
  • Testpartout shows no percentile and no global average, because no real aggregated data exists yet. When it does, it will come from measured results — never from estimates.

Procedure

How the test works

  1. 01

    Focus the click area

    The large panel above is the whole test surface. Nothing runs until you click it, so there is no countdown to catch.

  2. 02

    Click to start

    Your first accepted click starts the ten seconds and is counted as click one. There is no separate start button to waste time on.

  3. 03

    Keep clicking

    Click or tap as fast as you can sustain, with a mouse, a touchscreen or a pen. The live counter and the remaining time update frequently while the authoritative score remains timestamp-based.

  4. 04

    Ignore the wrong buttons

    Right-click, middle-click and secondary touch contacts are ignored rather than counted, so a context menu cannot inflate your score. Keyboard keys are a different kind of input and never count.

  5. 05

    Let the clock run out

    At ten seconds the session closes itself. A click that arrives at or after the deadline is not counted.

  6. 06

    Read your result

    Clicks per second, total clicks, the session length and the pointer type you used are shown together, along with your best CPS on this browser.

Methodology

How Testpartout measures this

The method below is exactly what the code on this page does — nothing is described that is not implemented.

What the implementation does

  • A session is a fixed ten seconds. It is never extended and never shortened.
  • Timing starts at the timestamp of your first accepted click, taken from the browser's monotonic clock (performance.now()), which does not jump if the system clock changes.
  • That first click counts as click one, so a session can never report zero clicks after it has started.
  • Clicks are read from pointerdown, not from the click event, so the press is timed rather than the release.
  • Only a primary press is accepted: the left mouse button, a single touch contact or a pen tip. Non-primary buttons, secondary contacts and modifier-held presses are ignored.
  • Only pointer presses are measured. Space, Enter and any other key produce no score, because keyboard activation is a different physical input from a click. The rest of the page stays keyboard navigable.
  • The pointer type of your first accepted press — mouse, touch or pen — becomes the input method of that session. A press from a different pointer type is then ignored, so two kinds of hardware are never mixed into one result.
  • CPS = accepted clicks / elapsed seconds. On a completed session the divisor is the full ten seconds.
  • The deadline is authoritative. A click at or after ten seconds closes the session instead of being counted.
  • If the page becomes hidden the session is cancelled and produces no result, because a background tab cannot be timed honestly.

Limits of a browser measurement

  • The timing is measured by your browser. Background load, battery-saver modes and frame-rate throttling all add noise.
  • A faulty mouse that double-fires a single press will be counted as two clicks. The test measures the events your system reports, not your intent.
  • Automated clicking, macros and hardware that generates multiple events per press are not detected. A local result that was not produced by hand is meaningless, but it is your own browser storage.
  • Touch input on small screens is limited by contact area and palm rejection, so touch results are not comparable to mouse results.

Privacy

What happens to your data

This section describes the behaviour of the code on this page, not an intention.

  • The test runs in this page. No click stream, pointer trace or timing log is sent anywhere.
  • No account, sign-in or permission is required to run the test.
  • Only your best result is written to this browser's local storage: clicks per second, that result's click count, its input method and a timestamp. No click stream and no press timestamps are stored.
  • Clearing your browser storage removes the personal best. There is no copy of it anywhere else.
  • Results are not uploaded, aggregated or ranked. If Testpartout ever offers aggregated comparisons, it will be explicit and based on real measured data.

Troubleshooting

If the test does not behave as expected

My clicks are not counting

Only a primary pointer press counts. Right and middle mouse buttons, modifier-held presses and keyboard keys are ignored on purpose, and after the first press only that same pointer type keeps counting.

A context menu keeps opening

The context menu is suppressed inside the click area, but some system-level gestures still fire. Use the left mouse button, or tap with one finger on a touchscreen.

The session was cancelled

Switching tabs or minimising the window hides the page, and a hidden page cannot be timed honestly. The session is discarded and your personal best is untouched.

My CPS looks impossibly high

Check the mouse for a failing switch: a worn button often reports two presses for one physical click. A mouse test will show whether single clicks are registering twice.

Nothing happens when I tap on mobile

Tap inside the large panel rather than on the surrounding text, and use one finger — additional contacts are treated as secondary and ignored.

The result did not save

Only a completed session that beats your stored best is saved. Private browsing and storage-blocking settings can also prevent writing to local storage.

Factors

Common factors that affect click speed results

Clicks per second is a measurement of your hand, your device and your browser together. These factors move the number without your ability changing.

Switch weight and travel

Switch weight and travel affect how quickly a button resets, so the same hand can produce different rates on different mice.

Technique

Single-finger tapping, alternating fingers and jitter techniques load the hand differently and can change the rate. None is more correct — be consistent between sessions.

Input device type

Mouse, trackpad, touchscreen and pen report presses through different mechanisms, including contact detection and palm rejection on touch. Results from different input methods are not directly comparable.

Pacing over ten seconds

A ten-second window rewards a sustainable rhythm. A two-second burst that collapses afterwards scores worse than steady clicking.

System load and frame rate

A busy machine delivers input events less smoothly. Closing heavy tabs before a session gives a cleaner measurement.

Fatigue and warm-up

Click rate is a small-muscle task, so warm-up and fatigue can both influence repeated results.

FAQ

Frequently asked questions

How is clicks per second calculated?
Your accepted clicks are divided by the elapsed seconds of the session. On a completed run the divisor is the full ten seconds, so a burst at the start cannot inflate the final figure.
Does the first click count?
Yes. The first accepted click both starts the ten-second timer and counts as click one, so you lose nothing by starting the test yourself.
Why are my right-clicks ignored?
Only a primary press counts: the left mouse button, a single touch contact or a pen tip. Non-primary buttons and secondary contacts are filtered out so accidental input cannot raise your score.
Can I use the keyboard instead of a mouse?
No. This measurement requires a mouse, touchscreen or pen, because a key press is a different physical input from a click and mixing the two would make the number meaningless. Every other control on the page remains keyboard operable.
Is my click data sent anywhere?
No. The whole test runs in this page and no click stream or timing log leaves your browser. Only your best CPS, its click count, its input method and a timestamp are stored locally.
What happens if I switch tabs mid-session?
The session is cancelled and no result is recorded, because a hidden page cannot be timed honestly. Your stored personal best is unaffected.
Why did my score drop on a different computer?
Click speed depends on the switch, the pointer device and how the browser delivers input events. Compare sessions on the same device and input method rather than across machines.
How does my result compare to other people?
Testpartout does not show that yet. Percentiles and averages will only appear when they can be built from real measured results, so no invented benchmark is displayed in the meantime.