A high hit count alone does not explain a run. Use accuracy, acquisition times, streak, difficulty, and validity together to see how you produced the score.
What hits and misses record
A hit is a primary-button press on one of the three active targets. The hit target is replaced while the other two keep their positions and timers. A primary-button arena press outside every target is a miss: it resets the current streak and moves no target.
Accuracy is hits divided by total scored shots—hits plus misses—expressed as a percentage. Raising speed by clicking carelessly can increase hits while lowering accuracy, so both values matter.
Acquisition-time metrics
Each target has an independent timer beginning when it appears. A hit records the elapsed time for that target. Average target time uses every valid hit time; median target time is the middle recorded hit time after sorting. Fastest hit is the smallest acquisition time, while best streak is the longest sequence of hits without a miss.
A fastest hit shows a peak moment. Median and average are better summaries of the whole run.
Standard Mode and Hell Mode
Rule
Standard Mode
Hell Mode
Target size
64 logical units
32 logical units
Center metric
Not used
6-unit Ultra-Precision center zone
Personal-best order
Hits, accuracy, lower median time
Hits, accuracy, Ultra-Precision Rate, lower median time
Ultra-Precision Rate equals Ultra-Precision Hits divided by all valid hits. It describes center-zone placement among successful hits; ordinary accuracy separately accounts for misses.
Competitive and Practice Mode
Competitive Mode requires a mouse-reported primary pointer, a viewport of at least 1100 by 700 CSS pixels, and a rendered arena of at least 960 by 540 CSS pixels. Touch, pen, small screens, and other environments remain available in Practice Mode.
Only a completed valid Competitive result can replace the corresponding competitive personal best. Practice Mode is useful for learning the interaction, but it should not be treated as interchangeable with Competitive results.
A practical practice structure
Choose one mode and keep it unchanged for the session.
Use an opening run to settle into the target pattern rather than chase a record immediately.
Complete a small group of runs with a short break between them.
Review hit count together with accuracy and median target time.
If accuracy collapses as hits rise, slow down enough to restore controlled clicks.
Stop when fatigue changes technique; compare another session under the same setup.
This is a repeatability framework, not a promise that a browser drill will transfer directly to a particular game.
Keep comparisons honest
Use the same device, pointer settings, display mode, browser, difficulty, and rules version. A run becomes invalid if focus is lost, the page is hidden, the arena size changes beyond tolerance, or fullscreen is exited after a fullscreen start. Those controls reduce obvious inconsistencies but do not make the trainer tamper-proof.