About & Methodology

Reaction Benchmark is 13 short browser tests that measure reaction speed, focus, self-control, time sense, aim, memory, color discrimination and typing speed. You can send a friend the exact board you just played, or open a group room where everyone plays the same one. Everything runs in your browser, and you never need an account. Only two things reach our server. One is the anonymous statistics record described below. The other is the nickname and score you submit if you choose to join a leaderboard or a group room. Your bests and history stay in your browser.

Who runs this

One independent developer builds and runs this site. If something is broken, wrong or unfair, write to ysc9550@gmail.com and we will fix it.

Every figure here was checked against the paper it came from before it went up. If we could not verify a source, the number is not on the site. In our view, a missing number is better than a made-up one.

How the percentiles work

Your score is compared with results from published research, not with other visitors to this site. People who find a reaction time test by searching for one are not a fair sample of everyone.

The rule is simple. If a published norm fits the task, you get a percentile, and that test's page names the study. If none fits, you get your score and your own history instead. Inventing a distribution would be easy and would look more impressive. It would also be a lie.

Reaction Time — reference study

Our reference is Woods, Wyma, Yund, Herron & Reed (2015), Factors influencing the latency of simple reaction time, Frontiers in Human Neuroscience 9:131. It tested 1,469 adults aged 18 to 65. Their mean simple reaction time was 231 ms, and the spread between people (the standard deviation) was 26.8 ms.

That study used lab equipment. A browser adds its own delay on top of your reaction. Tests of online experiment platforms put that delay at roughly 71 to 87 ms (Anwyl-Irvine, Dalmaijer, Hodges & Evershed, 2021, Behavior Research Methods 53(4):1407–1425).

So a fair comparison would take about 80 ms off your time. On the study side, it would use the authors' own device-corrected mean of 213 ms instead of the raw 231. That puts both numbers on the same device-free scale. Comparing a corrected score with an uncorrected mean would make everyone look faster than they are.

The catch is that your own device may add more or less than 80 ms. A correction that is right on average can still be wrong for you. That is why reaction time gets no percentile here. The study and the 80 ms figure stay on this page as reference and never turn into a "top N%" on screen.

Sequence Memory — percentile shown

Your span is compared with the forward Corsi block-tapping span in Facchin et al. (2024), Regression-based normative data for Corsi Span and Supraspan learning and recall among Italian adults, Neurological Sciences 45(12):5707–5718. That study tested 340 healthy adults aged 21 to 89. Their mean span was 4.97, with a standard deviation of 1.03 and a range of 2 to 8.

In the classic task, an examiner taps nine blocks placed at odd spots on a board. A 3×3 grid clicked on a screen is a close relative of that task, not the same test.

Aim Test, Number Memory, Visual Memory, Chimp Test, Verbal Memory, Color Match, Focus Test, Stroop Test, 10 Second Challenge, Typing Speed — compared with your own history

No published norm matches these tests as they are played in a browser. So your score is compared with your own history on the same device, and with the leaderboards.

Each test's own page explains the reasoning in full.

What we do not claim

None of these tests diagnose anything. They do not screen for color blindness, attention disorders, dementia or brain injury, and a low score on a web page is not medical information. If you are worried about your eyesight or your memory, please see a doctor, not a browser tab.

Accessibility

How this is built and checked

Plain code, on purpose

The site uses no framework and no UI libraries. It is plain JavaScript modules and plain CSS, uploaded as static files, so pages load in well under a second on a phone. Speed was not the main reason, though. A test that measures the gap between two moments should have nothing extra between your click and the code that records it. Every library in that path adds a delay nobody can see.

Outside scripts

Three outside scripts load here: Google Analytics, Microsoft Clarity, and the Google AdSense loader, which sits idle while our application is reviewed. All three load in the background, so none of them sits in the measurement path. Clarity is not loaded on the test pages or the Full Brain Test at all. On the Korean pages, the KakaoTalk share buttons (on a result, in a group room and in the footer) also load Kakao's script, but only when you press one.

Analytics and Clarity show us which pages people use and where they get stuck. When you finish a test, Analytics also gets an event with the test name and your score, but nothing that says who you are. Your bests and history stay in your browser. The privacy page explains what Clarity records and how to switch these tools off.

Checks that stop a bad release

We do not rely on good intentions to keep things correct. Automated checks stop the build instead. The build refuses to publish when:

We added each of those checks after that exact mistake reached the live site.

Before anything goes live, a script plays the 12 main tests from start to finish in both languages. It clicks through real rounds and reads the result panel, because unit tests can pass even when a result screen never shows up. That script is how we learned that browsers slow down timers in background tabs enough to break the timing. Now a hidden tab gets a notice instead of a bad number.

Your data

Your personal records (bests, streaks, achievements) are kept in your own browser's local storage. They disappear if you clear your browser data.

Only two things go to our server. When a test finishes, an anonymous statistics record helps build this site's own percentile baseline. It holds the game, mode, score, device type, language, date and whether it was the daily, plus accuracy on the aim test and voided clicks on reaction time. Nothing in it can identify you. And if you choose to join a leaderboard or a group room, the nickname and score you submit are stored there, along with whether you played by mouse or touch. The privacy page has the full detail.

Changelog