Click Counter screenshot

Click Counter

Count clicks with a running clicks-per-second rate and the gap between the last two presses, kept in the tab and never written to storage.

Privacy First
0 Runs
Updated 2026-11-22
Runs in your browser
Nothing stored
No sign-up

Click Counter

Count clicks with a running clicks-per-second rate and the gap between the last two presses, kept in the tab and never written to storage.

What the page does

The counter is a variable in this tab. Pressing the pad increments it, records the moment with performance.now() and recomputes the rate as clicks divided by elapsed seconds since the first press.

The last-gap line is the time between the two most recent presses, which is the number to watch when the rate plateaus: a steady gap is sustained speed, while alternating short and long gaps is a burst.

The page runs entirely in this browser tab; nothing is uploaded.

The pad above counts every press. Beside the count the page shows the average clicks per second since your first press, and the gap between the last two presses in milliseconds.

There is no storage and no account, so the number is a session fact: reload the page and it is gone. That is deliberate — a counter that wrote to the browser would leave a trace you did not ask for.

How to use Click Counter

Click the pad. The first press starts the clock; every press after it increments the count and updates the rate.

Press Reset counter to return to zero. The panel clears its readings, and the next press starts a new clock.

What the rate and the gap each tell you

The rate is a long-run average: total clicks divided by total seconds since the first press. It answers "how fast have I been clicking overall", and it falls slowly after a fast burst because the whole session is in the denominator.

The gap is the instantaneous reading: the distance between the last two presses. A rate of six per second and a gap of 160 ms describe the same rhythm, but the gap is what changes first when your hand tires. Both are computed from the same event timestamps, so they cannot disagree about when a press happened.

What to Expect

Best for

  • Counting repetitions in a short session
  • Watching a click rate settle
  • A stress-free way to test a new mouse button

Not ideal for

  • Keeping a count across reloads, which this page deliberately does not do
  • Measuring double-click detection
  • Recording a long study session

What this tool keeps

  • The exact count and the timestamps of the first and last press

What may need cleanup

  • Nothing: resetting is the only cleanup

Common errors

  • Reloading the page clears the count, by design
  • A double-click counts as two clicks, because the browser delivers two events

Example use cases

  • Count twenty repetitions of an exercise
  • Compare a left and a right mouse button
  • Watch the rate settle over a minute of clicking

Sample input

Forty presses in 8.000 seconds

Sample output

40 clicks, 5.00 clicks per second, last gap 187 ms

Who this is for

  • Anyone counting presses
  • Readers testing a mouse button

Frequently asked questions

Will the count survive a reload?

No. The count is a JavaScript variable in this tab, and the page writes no storage. A reload is a new session, which is the honest behaviour for a counter with no account.

Does a double-click count twice?

Yes. The browser delivers two click events, and the page counts events, not gestures. It does not try to merge them, because that would undercount a genuine fast rhythm.

Is the rate an average or an instant reading?

An average: total clicks divided by seconds since the first press. The last-gap line beside it is the instantaneous reading between the last two presses.

Developer program

Build custom tools for your store

Join the SDK program to create useful ecommerce utilities for your store.