CPS test

Click speed, measured properly.
Even past 1,000 a second.

Click the pad yourself, or park your autoclicker's cursor on it and switch it on. Every press is counted with the time your browser recorded it, so the number stays right at any speed. Then see how the clicks were made.

Input waiting Run 10 s Input lag – Timer checking – fps --:--:--

clicks

Click here or press Space to start

Clicks per second over time

Clicks in each second

Starts with your first click.

Second	Clicks
No clicks yet.

Rhythm

Mean gap–

Gap variation–

Jitter–

Longest pause–

Authenticity

Double-clicks–

Bounce, under 50 ms–

Consistency–

Releases–

Rate and efficiency

Clicks per minute–

Burst vs sustained–

Press and release symmetry–

Median gap–

Gap between clicks

Waiting for clicks.

Where you clicked

Waiting for clicks.

Your runs

0 runs

Finish a run and it shows up here.

Why it keeps up past 1,000 CPS

Many click testers time each click when their own code gets around to it, and redraw the page on every press. Past a few hundred clicks a second they fall behind, the clicks pile up, and the reading flattens out around 600. This page keeps the timestamp your browser gave each click, does no drawing when a click arrives, and works out every number as clicks come in, so a minute at 2,000 CPS costs it no more per click than five seconds does.