Trail Making Test Online — Free Processing Speed & Visual Search Task

The trail-making task asks you to tap the numbers 1 through 15, scattered randomly across the screen, in ascending order as quickly as you can. Because you continuously alternate between visually locating the next number and moving your hand to hit it precisely, the total time reflects how quickly and smoothly you process information.

The original Trail Making Test grew out of the 1944 Army Individual Test Battery and was later established as a neuropsychological measure by Reitan. It has Part A (numbers only) and Part B (alternating numbers and letters). Soundary's task is our own web implementation of the number-only Part A concept; it does not include the letter alternation of Part B or the original normative tables, and it is not the paper-and-pencil TMT from the Halstead-Reitan battery.

Numbers you have already tapped are joined by a line so you can see your progress, and the next target number is shown at the bottom of the screen. Tapping a wrong number is logged as an error, but the task continues, ending when you reach 15. The actual tracing usually takes about a minute, and the whole thing, including instructions, under three.

The headline result is the total time, in seconds to one decimal place, from tapping 1 to tapping 15. Lower is better, and the easiest change to read is whether your time drops when you repeat under the same conditions. The detailed results add your error count and accuracy, your fastest and slowest segments, the average segment time, and a bar chart of all 14 segments (1 to 2 through 14 to 15).

Accuracy is calculated as 15 divided by (15 plus the number of errors), times 100: no errors gives 100%, three errors about 83%. With zero errors the note says you finished error-free; with one or two, that you made some errors but tracked well overall; with three or more, that errors were fairly frequent and you might focus on accuracy over speed.

This time is your raw score, not a scaled score compared against standardized norms. Because the layout is random each time, some rounds spread the numbers farther apart and take a little longer, and touch latency or screen size (on small screens the nodes sit closer together, so mis-taps increase) also feed into the result. Look at the broad trend rather than differences of a few tenths of a second.

Sleep deprivation, fatigue, caffeine or alcohol, and time of day show up fairly strongly in processing-speed tasks. Longer times with increasing age are a well-known pattern in the original test too, and switching between tablet, PC, and phone changes the same person's time because the screen size differs. It is natural for your first one or two attempts to speed up as you get used to the format, a practice effect.

To track a trend, repeat about once a week on the same device, at a similar time of day and in similar condition, and check that your error count is not creeping up alongside faster times. If speed improves only at the cost of more errors, you have shifted toward fast-but-inaccurate, so read accuracy together with time. Viewing it alongside the selective attention, Stroop, and visual search tasks helps you tell whether a slowdown is about processing speed or inhibitory control.

This task is a self-check, not a neuropsychological diagnostic instrument. That said, if your time keeps growing clearly compared with earlier attempts even when you feel well, or everyday things like finding your way, doing arithmetic, or locating objects seem noticeably slower, it is worth getting a formal neuropsychological evaluation from a psychiatrist or neurologist.