What it does
Useful, focused capabilities
- Target acquisition and moving tracking modes
- Mouse, pen, and touch support
- Adjustable duration and target size
- Optional pointer lock and fullscreen
- Local result history and JSON export
Skill & performance · browser-local
Aim trainer and tracking practice
Practice target acquisition or moving-target tracking locally with mouse, pen, or touch, adjustable duration and size, optional pointer lock, and private results.
Work happens in the current browser. The route does not require an account or a server-side processing job.
Interactive browser workspace
Aim trainer and tracking practice
The live tool is loaded in this browser only. This route does not need camera, microphone, or screen-capture permission for its main task.
Load the interactive workspace →Browser compatibility
Requirements and honest fallbacks
JavaScript and Canvas; optional Pointer Lock and Fullscreen support.
- JavaScript
- Canvas
- mouse, pen, or touch input
- Pointer Lock API
- Fullscreen API
- local storage
- download support
Questions people ask
Clear answers and limits
Does the trainer work on touch screens?
Yes. Target mode and tracking position work with touch or pen without requiring pointer lock.
What does pointer lock change?
It hides and confines the pointer while reporting relative movement, useful for desktop tracking. Browser and operating-system support varies.
Why does a hidden tab end the session?
Background throttling would make timing misleading, so the tool ends the attempt honestly.
Can results be compared across devices?
Only cautiously. Display refresh, scaling, pointer settings, hardware, and browser scheduling can all change results.
Is this a reaction-time medical test?
No. It is a practice game with local session metrics only.
What this tool checks
Practice target acquisition and moving-target tracking with mouse, pen, or touch. Choose target size and duration, optionally use pointer lock or fullscreen, and review local accuracy and timing metrics after a session. Hidden tabs end attempts because throttled rendering would distort timing. Display refresh, pointer settings, input hardware, and browser scheduling affect comparisons. Results are private practice measurements, not a medical reaction test, anti-cheat assessment, or universal ranking.
What to choose and what you get
What to choose
- mouse, pen, or touch pointer input on the practice canvas
Result
- an on-page target-practice result and downloadable JSON metrics
Supported use
- Target acquisition and moving-target tracking modes.
- Adjustable duration and target size with optional pointer lock and fullscreen.
Before you start
- It does not simulate a complete game, certify aim, or provide a competitive ranking.
Supported formats
- Accepted formats: keyboard, pointer, timing, browser state.
- Output formats: HTML report, JSON.
Browser support and permissions
- Modern browser with JavaScript; timing, scheduling, clipboard, and device behavior vary by browser.
- No camera, microphone, or screen permission is needed.
Choose the right settings
- Choose this route for target acquisition or moving-target practice.
- Use /reaction-time-test for visual response timing.
- Use /cps-test for sustained click or Spacebar rate.
Worked example
A pointer-practice session needs target-acquisition and tracking observations on the current display and input device.
Starting facts
- Mouse, pen and touch pipelines have different latency.
- Display scaling and browser scheduling affect comparisons.
Observed operation: Choose the practice mode, interact with visible targets and record local timing and tracking metrics for the session.
Review the result: Compare only sessions run under the same device, display, browser and foreground-tab conditions.
Boundary: The metrics do not certify skill, input latency, medical performance, anti-cheat status or comparability across devices.
Choose another tool when
- Practice metrics are not medical, anti-cheat, hardware-certification, or universal performance results.
If it does not work
- A hidden tab ends the attempt because delayed rendering would distort target timing.
- Pointer lock or fullscreen may be unavailable or denied by the browser.
- Touch, pen, and mouse sessions produce different input conditions and should not be treated as identical.
Things to know
- Metrics depend on display refresh, scaling, pointer settings, input hardware, and browser scheduling.
Privacy boundary
Browser interaction and local results stay in the current browser session and are not sent to an Aftermath processing service. How local processing is verified.
What this tool verifies
Reports local target-acquisition and tracking metrics for the selected input, duration, size, and practice mode.
Check before sharing
The score describes this browser session and input setup; it does not establish medical, competitive, or cross-device performance.