Flick Test

A repeatable task, not a universal rating.

Each round uses an 800 × 450 logical arena with targets at least 36 units wide. On small screens, Flick Test enlarges them to at least 28 CSS pixels. Each target keeps a 16-unit margin outside its radius. We balance 140, 240 and 340-unit moves, shuffle their order, then choose random feasible directions. Every 15-target round has five of each distance.

These are distances in the browser’s logical coordinate system, not physical mouse distances. The first planned move starts at the arena center; pointer-mode starting cursor position is not standardized.

What counts?

A primary click or tap outside the target but inside the arena is a miss. It does not advance the target. Right-clicks and outside-arena clicks are ignored. Changing focus, input method or arena size discards the active round.

How the Flick Score works

The accuracy fraction is squared to penalize missed clicks. Time spent recovering from misses is also included in acquisition time. This is a transparent product heuristic for MEDQE Tools comparisons, not a scientifically validated scale.

What is acquisition time?

Time from drawing a target to hitting it, measured with performance.now(). We retain unrounded values for calculations and display whole milliseconds. Session duration also includes the frames between targets.

What should I compare?

Use the same session length, input type, arena size, display scale and device. Target direction, practice and fatigue still add variation. Local Flick Score records are separated by length, input type, arena size and display scale.