Measure the clicks your browser registers while practicing a drag-click motion.
A drag motion slides a relaxed fingertip along the mouse button, using friction to create repeated button presses. A normal tap lifts and presses the finger for each intended click. The browser counts received clicks from either action; it does not recognise which physical technique produced them. Keep the mouse stable, try one short glide, and compare the registered count with a normal tap before starting a full run.
Arithmetic example, not a recorded user run: ten one-second buckets of 12, 10, 8, 8, 7, 7, 6, 5, 4 and 3 contain 70 clicks. The result is 70 ÷ 10 = 7.00 average CPS. The declining bars tell you that event density fell during this test; they do not identify whether friction, technique or registration caused it.
The rolling peak is a separate calculation. Six clicks between 0.90–0.99s and six between 1.01–1.10s produce a 12-click rolling peak even though each fixed second contains only six of those clicks. The peak can therefore exceed the tallest fixed-second bucket.
Result guide
This test counts click events that reach the browser while you perform a drag-click motion. Compare repeated attempts on the same mouse, surface and browser instead of treating one burst as a universal hardware score.
For Geometry Dash input practice, drag clicking is best treated as a separate high-density technique. Compare its registered input rate with your normal CPS, then use the wave trainer to check whether that extra input density is actually controllable.
Browser results can be affected by mouse debounce behavior, operating-system input handling and browser event delivery. The page cannot certify switch health, hardware polling rate or whether a technique is allowed by a community challenge list.
