The mobile penalty is real — and it's not you
If you've ever taken the Human Benchmark Reaction Time test on both your phone and your computer, you've probably noticed your mobile score is worse. Most people assume they're just less focused on mobile. The real explanation is almost entirely hardware.
A desktop PC with a wired optical mouse and a 144Hz+ monitor has a total input-to-display pipeline latency of roughly 5–15ms. A mid-range smartphone running Chrome adds 30–60ms of latency from the moment your finger touches the glass to the moment a JavaScript click event fires. That latency ends up embedded in your score.
Latency breakdown: desktop vs mobile
Where the latency actually comes from
1. Display refresh rate (output latency)
High impactOn a 60Hz display, a new frame appears every 16.7ms. This means the stimulus (the colored box appearing) can arrive up to 16.7ms before the next frame renders — adding up to half a frame of random latency to every trial. A 240Hz display reduces this to just 4.2ms maximum. Most smartphones run at 60Hz (budget) or 90–120Hz (flagship), still below 240Hz gaming monitors.
2. Touch digitizer sampling rate
Moderate impactThe touch screen samples finger position at a fixed rate (typically 60–240Hz on consumer phones, 120–240Hz on gaming phones). When your finger touches the glass, it must wait for the next sampling window before a touch event is registered. This adds 4–16ms of input-side latency before the JavaScript even "knows" you tapped.
3. Browser JavaScript event handling
Moderate impactMobile browsers on ARM processors handle JavaScript events more slowly than desktop Chrome on x86 CPUs. The event timestamp recorded for timing purposes may also lag the actual browser main-thread processing by 2–10ms on low-power mobile hardware, adding systematic bias to every recorded score.
4. Physical tap mechanics vs. mouse click
Small impactA mouse button requires approximately 2–3mm of travel before actuation. A touchscreen registers the moment capacitance is detected — theoretically faster. In practice, most users experience an extra 5–8ms due to the need to lift and re-drop the finger between trials vs. a mouse button remaining in position. This effect is highly individual and largely cancels out.
How to normalize scores across devices
If you need to compare a mobile score to a desktop score, apply the following rough correction. These factors are estimates — individual device variation is significant.
| Device type | Est. hardware latency | Correction to desktop |
|---|---|---|
| Desktop, wired mouse, 240Hz | ~8ms | baseline |
| Desktop, wired mouse, 144Hz | ~12ms | subtract ~4ms |
| Desktop, wired mouse, 60Hz | ~20ms | subtract ~12ms |
| Laptop trackpad, 60Hz | ~28ms | subtract ~20ms |
| Flagship phone, 120Hz | ~35ms | subtract ~27ms |
| Mid-range phone, 60Hz | ~47ms | subtract ~39ms |
The safest approach: single-device tracking
The correction table above is approximate. For meaningful longitudinal tracking, always use the same device. Even minor changes in browser version or OS update can shift your scores by a few milliseconds. Track relative change, not absolute numbers, especially across devices. Check the full breakdown by device type for more context on what a "good" score looks like on your specific hardware.
When is mobile testing acceptable?
Mobile testing is perfectly valid for several use cases — just not for comparing against desktop leaderboard scores or lab data.
- → Tracking your own progress over time (same device)
- → Comparing mobile scores with friends on mobile
- → Quick cognitive state check (sleep, stress, alertness)
- → Sequence and number memory tests (no hardware latency)
- → Comparing against the global leaderboard
- → Benchmarking against published lab reaction time norms
- → Claiming a "personal best" for cross-device comparison
- → Evaluating the same person's score from desktop vs. mobile
Tests with no hardware-latency issue include Sequence Memory, Number Memory, and Verbal Memory — these measure cognitive capacity, not motor timing, so device type is irrelevant to your score.
Get your true baseline on desktop
Use a wired mouse on a 144Hz+ display for the most accurate reaction time measurement.
Take the Reaction Time test