Skip to content

Site info

About AimTests

AimTests is a browser-based collection of gaming skill tests and training tools. It currently covers click speed, visual reaction, mouse control and three forms of memory testing.

What AimTests is for

AimTests gives you a practical place to establish a baseline, repeat a measurement and review your own results over time. The site is designed for people who want a focused tool rather than an account, profile or long onboarding flow. Every current test starts in the browser, and the rules that determine its result are explained on the same page.

What you can do today

The CPS Test measures repeated click speed and links to jitter, butterfly, drag and Kohi formats, plus a physical-keyboard Spacebar Counter. The Reaction Time Test provides a fixed visual-response assessment, while its training tool organises warm-ups and scored sets. The Aim Test uses fixed flick and tracking tasks, and Aim Training adds configurable flick, precision and tracking practice. The memory section contains separate number, sequence and verbal recognition tests. These tools remain separate because their scores use different units and answer different questions.

Tests and training serve different jobs

A test uses fixed rules so that repeated attempts have a stable reference point. Training is for practice: it may use adjustable settings, warm-up rounds or grouped sessions. Aim and reaction currently have dedicated training flows, and their training histories stay separate from their fixed-test histories. A better training result is useful evidence about that exercise; it is not automatically a new assessment score.

How to read a result

Treat a browser result as a measurement made under a particular setup. Your display, mouse or keyboard, browser, input method, attention and test duration can all affect it. The most useful comparison is usually with your own earlier attempts under matching conditions. Several tools store the input and test settings with each result so their history views can keep unlike attempts apart. Scores from different tools should not be combined into one overall gaming rating.

How the tools are designed

Each tool owns its measurement rules. A reaction test needs random waits and a rule for responses that arrive before the signal; a click test must count distinct presses without imposing the same filter; an aim test must define its target, duration and accepted input. Cancelled or interrupted attempts are handled by the relevant test instead of being silently presented as normal results. When AimTests publishes external research data, the source, measurement context and limitations are identified on the reference page rather than turned into an unsupported universal rank.

What the results do not mean

AimTests does not use a browser score to certify professional ability, predict a game rank or promise an in-game outcome. The memory tools are not IQ tests, and no result on this site is a medical, psychological or diagnostic assessment. Browser timing is also not laboratory calibration: a precise software clock cannot remove unmeasured display and input delay.

Data & privacy

No account is required. The complete result histories used by the tools are stored in this browser on this device. AimTests also offers optional Google Analytics and Microsoft Clarity: neither loads until you accept analytics. If accepted, limited events can include the tool name, a rounded reading and whether a result was flagged; Clarity provides session replay and heatmaps. The Privacy Policy explains the current data flow, retention and controls; it will be updated when the site's data practices change.

How the project develops

Tools are revised one page at a time as their rules, result views and supporting explanations improve. New categories are added when there is a complete tool to publish, not as empty placeholders. Feedback helps identify unclear instructions, inconsistent measurements and useful additions, but it does not create a public roadmap or delivery promise.

Contact

To report a bug, question a rule or suggest a useful tool, write to [email protected]. For a test problem, include the page address, browser, device, input method and the steps that produced the issue when possible.