SchulteLab

Processing Speed Test — Standard Scores & Reference Values

How many symbols should you be able to code in 90 seconds? This page collects what the published literature actually offers — written-version age anchors, a fully normed neighbor task, device and practice effects — with the source attached to every figure, plus an honest account of why none of it converts directly to a web score.

What processing speed is — and why symbol coding measures it

Processing speed (Gs) is a formal psychometric factor: how quickly you can execute simple, already-learned operations under time pressure. Its classic measure is symbol–digit coding — the best-known clinical example is the Symbol Digit Modalities Test (SDMT): 90 seconds, a key pairing nine symbols with digits 1–9, scored as the number of items completed correctly. Our web test follows that format with an original symbol set (the SDMT symbols are copyrighted); it is a training and self-tracking tool, not the clinical instrument.

The closest fully-normed digital neighbor is the NIH Toolbox Pattern Comparison Processing Speed Test — 90 seconds of same/different picture judgments, normed on a national sample of 4,859 participants aged 3–85 (Carlozzi et al. 2015: https://pmc.ncbi.nlm.nih.gov/articles/PMC4542749/). It proves the format normable at scale — but it is a different task (picture comparison, not symbol coding), so its norms cannot be relabeled as ours.

Your device matters less here than on a reaction-time test. Browser and platform pipelines add measurable noise — Anwyl-Irvine et al. measured end-to-end reaction-time delays of roughly 71–87 ms depending on platform, browser and device (2020, Behavior Research Methods: https://link.springer.com/article/10.3758/s13428-020-01501-5), and Passell et al. 2021 found mobile devices run 50–200 ms slower than desktop on the same tasks (https://link.springer.com/article/10.3758/s13428-021-01597-3). But a coding task aggregates items of 2–4 seconds each, so a ±100 ms device offset is a small fraction of every answer — where it would be a third of a 273 ms reaction time.

Practice effects on symbol coding are large and durable — repeat SDMT studies find gains persisting for up to 18 months (Novakova et al. 2025: https://pmc.ncbi.nlm.nih.gov/articles/PMC12357967/). Our countermeasure is the one clinicians use: alternate forms. The pairing key reshuffles at every session start, so your trend reflects lookup speed rather than a memorized key — though a residual warm-up effect is unavoidable and we will not pretend otherwise.

Written-SDMT age anchors (NIAAA) — top-quintile cutoffs

Age groupTop quintile (written 90 s, correct)Source
18–24 years≥ 67 correcthttps://www.niaaa.nih.gov/sites/default/files/match02.pdf
25–34 years≥ 65 correcthttps://www.niaaa.nih.gov/sites/default/files/match02.pdf
45–54 years≥ 62 correcthttps://www.niaaa.nih.gov/sites/default/files/match02.pdf
55–64 years≥ 55 correcthttps://www.niaaa.nih.gov/sites/default/files/match02.pdf
65+ years≥ 47 correcthttps://www.niaaa.nih.gov/sites/default/files/match02.pdf

WRITTEN-VERSION ANCHOR — NOT COMPARABLE WITH THIS WEB TEST. These cutoffs come from the supervised pen-and-paper SDMT (110 items, written answers, clinical administration) reproduced in the NIAAA MATCH manual. Our web task uses an original symbol set, key/button input and self-administration — a web score must never be read against this table. It is shown to give the age gradient an honest, sourced shape, nothing more.

A fully normed neighbor: NIH Toolbox Pattern Comparison

If you want a digitized processing-speed task WITH norms, the honest pointer is the NIH Toolbox Pattern Comparison test: 90 seconds of same/different judgments on pairs of pictures, up to 130 items, normed on 4,859 participants aged 3–85 representative of the US population (Carlozzi et al. 2015: https://pmc.ncbi.nlm.nih.gov/articles/PMC4542749/). It demonstrates that a 90-second format can carry real norms — and it is still not interchangeable with symbol coding, which adds the lookup-and-remember component. That is exactly why we publish our own live community distribution (the strip above) instead of borrowing someone else’s table.

Device and browser effects — real, but diluted here

Web timing is noisy: Anwyl-Irvine et al. (2020) measured end-to-end response delays of roughly 71–87 ms across platform/browser/device combinations (https://link.springer.com/article/10.3758/s13428-020-01501-5), and Passell et al. (2021) found mobile devices running 50–200 ms slower than desktop on identical tasks, with Android about 0.56 SD behind Windows after covariates (https://link.springer.com/article/10.3758/s13428-021-01597-3). On a simple reaction test that noise swallows a third of the signal; on a 90-second coding run it rides on items that each take 2–4 seconds, so the device tax shrinks to a few percent of your pace. Still: compare your scores on the same device, and expect a phone to read slightly below a desktop.

Practice effects — and what we do about them

Symbol-coding scores rise with repetition and the gain is stubborn: repeat-administration studies of the SDMT find practice effects still measurable up to 18 months later (Novakova et al. 2025: https://pmc.ncbi.nlm.nih.gov/articles/PMC12357967/). The standard clinical countermeasure is the alternate form, and this site builds it in: the symbol–digit key is reshuffled with a seeded random generator at every session start, so memorizing last week’s pairing buys you nothing. Honest residue: the task itself still gets easier with familiarity, so treat your first few sessions as warm-up and your later trend as the signal.

Does training processing speed transfer? The honest evidence

The strongest positive result in this field is the ACTIVE trial: 2,832 older adults randomized to memory, reasoning or speed-of-processing training (JAMA 2002: https://pubmed.ncbi.nlm.nih.gov/12425704/). At the 10-year follow-up, the group receiving the speed-of-processing intervention — a specific, adaptive UFOV-style training protocol — showed a 29% lower dementia risk than controls (Edwards et al. 2017: https://pmc.ncbi.nlm.nih.gov/articles/PMC5700828/). Read that sentence carefully: it is about a particular adaptive training intervention, not about taking a test like this one.

The counterweight: a major review of the brain-training literature found strong evidence that practice improves the trained task and weak evidence for transfer to untrained abilities (Simons et al. 2016: https://gwern.net/doc/dual-n-back/2016-simons.pdf). So our claim is deliberately boring: practicing here improves your score here, visibly, in your local history. We do not claim — and no honest site may claim — that this test prevents dementia or raises intelligence.

Speed coordinates — where the anchors sit

Three fixed points to orient a processing-speed score, plus our live one: the paper ceiling (the written SDMT packs at most 110 items into 90 seconds — nobody completes it), the written top-quintile cutoff for young adults (≥ 67 correct, ages 18–24, NIAAA table above), the fully normed digital neighbor (NIH Toolbox Pattern Comparison, n = 4,859 — a different task), and this site’s own live community distribution in the strip under the reference table, which is the only anchor measured on THIS task and THIS input modality.

Take or print the test

Run your own 90-second coding round, or print seeded practice sheets for offline use. Open the printable coding sheets →

Frequently asked questions

What is processing speed, in plain terms?

It is how quickly you can perform simple, well-understood operations — matching, comparing, looking up — under time pressure. Psychometric models treat it as its own ability factor (Gs), distinct from reasoning or memory. Symbol–digit coding tasks are its classic measure, which is the format this site’s test follows with original symbols.

What is a good score on the 90-second coding test?

There is no published norm for a web version, so no honest "good" number exists yet. The written-SDMT quintiles above are paper anchors that cannot be converted (different input, symbols and administration). Your meaningful references are your own trend across days — practice effects are real — and the live community strip above, which grows into a proper site distribution as samples accumulate.

How is this different from a reaction time test?

A reaction time test measures one stimulus–response loop in milliseconds and is heavily polluted by device latency; a coding test aggregates dozens of lookups over 90 seconds, so device noise dilutes to a few percent. Coding also loads on more than speed: visual scanning, pairing lookup and short-term remembering of the key. The two correlate, but they are not the same measurement.

Does training processing speed actually help?

On the test itself, yes — practice gains are large and can persist up to 18 months (which is why our key reshuffles every session). On anything beyond the test, the evidence is narrow: the ACTIVE trial’s 29% lower 10-year dementia risk came from a specific adaptive UFOV-style training intervention, not from a self-test; and broad reviews (Simons et al. 2016) find far transfer weak. Treat your trend as a fitness tracker for one skill, nothing more.

Why does the symbol key reshuffle every session?

To keep the measurement honest. If the key were fixed, repeat visits would increasingly test memory of the key instead of lookup speed — the practice effect documented to persist up to 18 months on the SDMT. A reshuffled key is the web equivalent of the alternate test forms clinicians use, so your cross-day trend tracks skill rather than memorization.