By the CPS Test site operator team. This is an operator-authored teaching activity, not an independent recommendation. All example results are invented for illustration; they are not claims about typical pupils or skill levels.
A short clicks-per-second exercise can introduce rates, denominators and experimental design. It does not need to become a public leaderboard. The most useful lesson is often that a number needs context, not that one participant is faster than another.
This activity is intended as an optional, low-stakes demonstration. Offer a non-clicking role from the beginning. Nobody needs to explain why they prefer to observe, calculate or discuss instead of operating a mouse.
Decide what the lesson is about
Write one question on the board: “How do we turn a count taken over a time window into a rate?” Keep that objective visible. Avoid attaching labels such as smart, talented, slow or gamer to a result. The measurement describes what was recorded during a particular task; it is not a general assessment of a person.
For a purely mathematical lesson, you can skip live testing entirely and use the invented data below. A demonstration is useful only when it helps learners understand the count and the time window. Repeated attempts aimed at breaking records are not necessary.
Prepare the device without overpromising privacy
Use a shared demonstration device if that fits your setting. Close unrelated documents and notifications so a projected screen does not expose names or messages. Do not ask participants to sign in to a browser, share an account, install an extension or provide an email address just to demonstrate a rate.
Our CPS Test browser counter is one possible example of a timed counting interface. Review the site's current privacy information and any external requests before using it under your institution's rules. “No account required” is not the same as “no network activity,” and this guide does not promise that any public website is approved for a school or collects no technical data.
If the local rules do not permit the site, use a teacher-controlled offline counter or the supplied fictional examples. The arithmetic lesson remains the same.
Demonstrate once, then explain the denominator
Choose a short, fixed window and a comfortable ordinary input method. Show where the count appears and what duration is being used. Do not require unfamiliar techniques or maximum effort. Stop the practical activity if the participant wants to stop; an unfinished run can be discussed without recording a score.
Then switch to these fictional observations:
Observation A: 30 registered clicks / 5 seconds = 6 clicks/second.
Observation B: 54 registered clicks / 10 seconds = 5.4 clicks/second.
Observation C: 18 registered clicks / 3 seconds = 6 clicks/second.
Ask why observation B has the largest count but not the largest rate. Have learners write the units in the calculation: clicks divided by seconds. Next ask why A and C have the same average rate despite different counts. These questions do not depend on anybody's identity or actual score.
If you compare a live display with hand arithmetic, acknowledge that boundary rules and rounding can differ. Record the visible count and chosen duration rather than inventing precision the interface does not provide.
Keep an observation separate from an explanation
Ask learners to name factors a fair comparison would need to hold steady: duration, device, input method and instructions. Let them propose possible reasons for a different result, but label those reasons as hypotheses. A single session cannot tell you whether a difference came from practice, equipment, counting rules or chance variation.
This is also a useful moment to explain what the activity does not measure. A self-started series of clicks does not establish how quickly someone noticed an unexpected signal. A total over several seconds does not establish physical mouse latency. Neither result should be used to diagnose a health issue or assign a general ability label.
Collect less, and define an ending
The default can be no saved participant results at all. Keep the fictional worksheet, not a roster of scores. If you genuinely need classroom observations, decide in advance what is necessary, who can access it and when it will be deleted under your institution's rules. Avoid public screenshots, faces, full names and class identifiers.
Do not assume that a nickname makes a result anonymous: a small group may still know who operated the device. Do not publish the fastest result on behalf of the group without the relevant permission. A helpful discussion does not require a public data trail.
End with an interpretation, not a winner
Ask each learner to complete two sentences: “This rate tells us…” and “This rate does not tell us…”. A good answer identifies the observed count, the time window and at least one limitation. Another useful exit question is what additional observation would be needed to investigate a different question.
The successful outcome is a clearer understanding of measurement. Everyone can contribute to that outcome, whether they clicked, calculated, checked units or pointed out a limitation.