Does internet lag actually affect your reaction time score?
The short answer: it depends entirely on the test architecture. A well-designed online reaction time test runs timing logic entirely client-side (in the browser's JavaScript), using performance.now() for high-resolution timestamps. When done correctly, network latency is irrelevant to measured reaction time — the test is self-contained in your browser.
A poorly designed test that sends a timestamp to the server and uses server-side timing is genuinely affected by network round-trip time. This adds the full round-trip latency (RTT) plus server processing time to your score. On a typical home broadband connection to a domestic server, that could be 15–80ms of artificial penalty on every trial.
How Human Benchmark handles this
The Human Benchmark Reaction Time test uses client-side JavaScript timing exclusively. The start and end timestamps are both captured locally in your browser using high-resolution time APIs. Network latency does not appear in your score — it's irrelevant once the page has loaded.
The score is only sent to the server after the measurement is complete, for logging purposes. This means even a 200ms network ping does not affect the displayed result.
What actually affects your score (it's not ping)
1. JavaScript event loop jank
High impactThe browser's JavaScript engine runs on a single thread. If another tab, extension, or background process causes the JS event loop to "jank" (stall for a frame or more), the timing of both stimulus delivery and click detection can be delayed by 16–50ms. This is a client-side problem unrelated to network — caused by browser load, not internet speed.
Mitigation: Close other tabs, disable browser extensions before testing, and avoid background downloads during your session.
2. Display refresh rate (the frame latency)
High impactAs discussed in our mobile vs desktop guide, your display's refresh rate determines how quickly a stimulus change is actually visible after the JavaScript fires. On a 60Hz monitor, this adds up to 16.7ms of random variance. This is display hardware latency — nothing to do with internet.
3. Page load state and asset caching
Moderate impactIf the test page is still loading assets (CSS, fonts, images) when you start your first trial, the browser may experience rendering delays that affect the first 1–2 results. This is why the first trial on a fresh page load often appears slower. The fix is simple: let the page fully load, take a few warmup trials, then record your actual score.
4. When network DOES matter: poorly architected tests
Site-specific riskSome older or poorly built reaction time websites use server-round-trip timing. Signs: your score gets worse when your ping spikes; test results vary dramatically on different network connections; the test has a noticeable delay between clicking and result display. Avoid these for any serious benchmarking.
Jitter: the hidden enemy of consistent scores
Even if network latency doesn't affect your score directly, poor network conditions can cause browser resource throttling and CPU scheduling delays that introduce timing jitter — random variation between trials that isn't your reaction time at all.
| Condition | Expected score variance | Primary cause |
|---|---|---|
| Ideal (wired, no tabs) | ±8–15ms | Genuine RT variability |
| Wireless WiFi (stable) | ±12–20ms | Minor wireless jitter |
| Many tabs open | ±20–35ms | JS event loop contention |
| Mobile LTE (congested) | ±25–45ms | Network jitter + touch latency |
| Video streaming in background | ±30–60ms | CPU/GPU competition |
High variance across trials usually indicates an environmental problem, not genuine cognitive inconsistency. Use your median score (not mean, not best) and take at least 10 trials to get a stable estimate. Compare to the global leaderboard only when using optimal conditions.
The optimal testing setup
- → Wired ethernet (not WiFi)
- → Wired USB mouse (not wireless/Bluetooth)
- → 144Hz+ display
- → Fast SSD (reduces OS latency)
- → Close all other browser tabs
- → Disable non-essential extensions
- → Pause background downloads/updates
- → Use Chrome or Firefox (best JS performance)
For most cognitive tracking purposes, these optimizations aren't critical — the signal from your actual reaction time dwarfs the hardware noise. But if you're trying to set a personal best or compare precisely against others on the leaderboard, controlling your environment matters. Also review how screen refresh rate affects your score for the display-specific piece of this puzzle.
Test under optimal conditions
Close other tabs, use a wired mouse, and let the page fully load before starting. Your score will reflect your brain — not your browser.
Take the Reaction Time test