What the aim test measures
The Aim / Accuracy Test measures a controlled browser task: respond to one visible target at a time, for a fixed set of 30 trials. Each trial is resolved by one scoring pointer response. A press inside the circular target is a hit; a press inside the stage but outside the target is a miss.
The result separates accuracy from speed. Testpartout reports how many targets you hit, your accuracy percentage and your average hit time, but it does not combine those into an arbitrary aim score.
Thirty trials, one target at a time
The session has exactly 30 resolved trials. There is no bonus trial and no extension for a fast or slow response. After a target is hit or missed, the next target appears after a short blank transition.
Only one response can score a visible target. Once you press, that trial is resolved and later presses during the transition do nothing. This keeps each trial independent and avoids counting extra clicks after the result is already known.
Hit detection
Testpartout uses circular geometric hit detection. The target has a centre and a radius in the measured stage. When you press, the page compares the pointer position with that circle. A point on the circle boundary counts as a hit; outside the circle counts as a miss.
Accuracy is calculated over the fixed session:
Accuracy = hits / 30 × 100
Average Hit Time
Average Hit Time uses successful hits only. A missed trial has no time-to-target for the target, so it increases the miss count but does not enter the hit-time average. This keeps the timing number focused on successful target acquisition.
That is why two numbers are needed. A session with high accuracy and slower hits tells a different story from a session with faster hits and more misses, and Testpartout does not hide that trade-off behind a fabricated composite score.
How targets are placed
Target size is based on the measured stage width, with a lower and upper limit so targets remain usable on touch screens without becoming oversized on wide desktop layouts. Target centres are generated inside the stage so the whole circle remains visible.
Consecutive targets use a minimum-distance rule. The generator samples positions and accepts a target that is far enough from the previous one; if random sampling cannot satisfy the rule, it falls back to a deterministic in-bounds corner that is farthest from the previous centre. The goal is to avoid effectively repeating the same target position.
Pointer input and modality
Aim is a pointer measurement. Mouse, touch and pen input can score. Keyboard input does not score because pressing a key is not the same task as aiming at a point on the stage.
The first measured response freezes the session modality. If the session starts with a mouse, later touch or pen responses are ignored, and the same rule applies in the other direction. This prevents one result from mixing different input paths.
Browser, display and input latency
Target timing uses a browser-observed start reference: the target is committed for an upcoming frame, then performance.now() is read. The browser then paints, the display scans out the target, your input device reports the press, and the browser delivers the pointer event.
Those steps can add latency or variability. A faster display, a different pointer device, wireless links, touch sampling and system load may all influence the result. The same caveat applies to related tasks such as the Reaction Time Test and the Click Speed Test.
Reading the result
Testpartout does not turn the result into an FPS rank, esport label, percentile, average, or universal aim grade. Without real aggregated data, those labels would be invented. The most useful comparison is your result against your own later runs under similar conditions.
The broader rules behind Testpartout measurements are explained on the methodology page.