A mobile reaction-time score and a desktop reaction-time score should not be treated as identical. The person may be the same, but the input method, display refresh, browser power mode, hand posture, and touch pipeline are different. Use the reaction time test hub as the main map before comparing devices.
PulsarMS works on mobile because accessibility matters. For serious baselines, desktop with a stable mouse or keyboard is usually cleaner.
Why mobile scores can differ
Mobile testing changes several variables at once:
| Variable | Mobile effect | |---|---| | Input | Touch contact replaces mouse switch timing | | Posture | Phone grip changes finger movement | | Display | Refresh rate varies by device and power mode | | Browser | Background throttling and battery modes can matter | | Target size | Smaller targets increase slips and hesitation | | Audio | Phone speakers and Bluetooth earbuds add uncertainty |
The result is still useful if you compare mobile sessions against other mobile sessions. It is less useful if you compare one phone run against a desktop mouse run and call the difference your true reflex.
Touchscreen reaction time cautions
Touch input has a different physical action than clicking. You may move your finger farther, touch the surface before activation, or trigger accidental taps. Mobile UI guidance often focuses on touch target size because small targets increase selection time and errors. That same principle applies when you are trying to run a clean reaction-time test on a small screen.
For accessibility background, see W3C's mobile technique on adequate touch target size and NN/g's article on touch targets on touchscreens.
When mobile testing is still useful
Mobile is useful when:
- you want a quick casual baseline,
- you only compare against your own phone history,
- you are testing fatigue rather than hardware,
- the task you care about is actually touch-based,
- you keep the same phone, browser, and posture.
For leaderboard-grade comparisons, use a consistent desktop setup and read input lag vs reaction time.
How to make mobile tests cleaner
- Put the phone on a stable surface.
- Use the same finger and posture each time.
- Disable battery saver.
- Keep the browser foregrounded.
- Run several sessions and compare medians.
- Do not compare phone touch results to mouse results.
For screen-specific details, read the visual reaction time measurement guide and monitor refresh rate and reaction time.
Sources & context
The touch-target cautions here follow W3C's mobile technique on adequate touch target size and NN/g's guidance on touch targets on touchscreens. PulsarMS reads the same pointer and touch event timestamps on every device, so a phone score and a desktop score describe different setups, not different people. See how we measure for the timing model behind both.