A Go/No-Go task and a Continuous Performance Test both ask the same press-or-withhold question, but they apply it on very different scales: a Go/No-Go task is a short discrete-choice game in which each cue prompts one explicit Go or No-Go response, while a Continuous Performance Test (CPT) stretches the same press-or-withhold rule across a long vigilance run where a single button must be pressed for most stimuli and withheld on rare target trials. The two designs share a common ancestor in response-inhibition research, yet they target different cognitive demands, different session lengths, and different ways of recording a No-Go answer. Both have also been adapted into browser-friendly versions, though most public web tools tend to mirror the Go/No-Go shape rather than the long CPT shape. The fixed-route Go / No-Go Test is one such browser game: twelve labelled cues, six Green circles that ask for Go, six Purple triangles that ask for No-Go, and a button press (or G and N key) for every single cue. Because every response is explicit, the route stays observable and free of timer inference, and the resulting counts describe exactly what you chose.
What Each Task Measures in Practice
A Go/No-Go task measures how reliably a participant can apply a single press-or-withhold rule to a small set of labelled cues. The classic shape pairs one frequent Go stimulus with a less frequent No-Go stimulus and counts how often the participant presses for Go, withholds for No-Go, or slips on either side. The rule is short, the cues are labelled, and the result is a clean record of explicit choices. Researchers describe the No-Go rule as a way of exposing a tendency to act on a prepotent response, since pressing Go is the default and withholding it requires an active stop.
A Continuous Performance Test measures something adjacent but not identical. It uses the same press-or-withhold machinery but loads it with sustained attention: a long stream of similar stimuli, a low rate of target trials, and the requirement to stay vigilant for several minutes without drifting. Errors of commission (pressing when you should not) and errors of omission (failing to press when you should) both matter, and a CPT typically tracks reaction time alongside accuracy. The CPT is essentially a Go/No-Go task stretched over a long, monotonous run, with the proportion of targets shifted heavily toward the non-response side so the participant has to keep watching without acting.
The shared rule is the source of the comparison. Both tasks ask the same core question: when you see one type of cue, press; when you see the other, do not press. The differences live in session length, target frequency, and how the No-Go response is defined. A Go/No-Go design typically expects an explicit No-Go button or an explicit withhold; a CPT often uses the absence of a press inside a short response window as the No-Go record, which is why CPT results are so sensitive to the response window itself.
Cue Presentation and Response Style Compared
A compact table is the clearest way to see the structural difference between the two designs side by side. The features below reflect the publicly documented shapes of each task and not the result of any single browser round, so treat them as a structural contrast rather than as a score comparison.
| Feature | Go/No-Go task | Continuous Performance Test |
|---|---|---|
| Session length | Short, fixed route | Long vigilance run |
| Number of unique cue types | Two (Go and No-Go) | Two, sometimes with distractors |
| Target frequency | Balanced or skewed, by design | Rare targets among frequent non-targets |
| How a No-Go is recorded | Explicit withhold or button choice | Absence of press within a response window |
| Typical measures | Hits, misses, false alarms, correct rejections | Hits, false alarms, omissions, reaction time |
| Cognitive emphasis | Discrete response inhibition | Sustained attention over time |
| Browser adaptation | Common; explicit button choices | Rare in plain browser form |
The key contrast is the No-Go recording. A classic CPT often treats a missing press inside a short window as a No-Go, which means anything that prevents a press — a lost focus, a notification, an accessibility interruption — can look like a No-Go in the data. A Go/No-Go game can ask for an explicit button press instead, which means the result is never inferred from a hidden tab, a notification, or an abandoned page.
How to Play the Go / No-Go Test Game
The Go / No-Go Test is a small browser game that mirrors the Go/No-Go shape on a fixed twelve-cue route. The steps below come straight from the game's own controls, and each one keeps the result tied to a visible cue and a visible action.
- Start the fixed twelve-cue route and keep the Green circle and Purple triangle rule visible.
- Choose Go for every Green circle and No-go for every Purple triangle with a button or the G and N keys.
- Review hits, misses, false alarms, and correct rejections as explicit choices from this private game route.
Each cue appears in a large central panel alongside a reminder of the two rules, so you never lose track of which shape means which action. One response advances one visible cue, and repeated keyboard events, rapid clicking after a transition, and inputs after the route is complete do not create extra classifications. The total stays tied to the visible cue and the visible chosen action, which is what makes the result auditable later.
You can keep the rule visible by glancing back at the on-screen reminder between cues, and you can stay on either the labelled buttons or the G and N keyboard shortcuts without losing accuracy. Touch and pointer users can rely entirely on the labelled buttons; keyboard users can stay on the letter keys without ever needing to look at the buttons. The route is the same product-authored route every time, so the totals are known and repeatable rather than generated by a private algorithm.
Reading Your Result: Hits, Misses, False Alarms, and Correct Rejections
At the end of the twelve cues, the game separates four simple outcomes. Each one is tied to a specific cue-and-action pair, so the count is a transparent record of your route rather than a vague performance estimate.
- Hit — selecting Go for a Green circle.
- Miss — selecting No-go for a Green circle.
- False alarm — selecting Go for a Purple triangle.
- Correct rejection — selecting No-go for a Purple triangle.
Accuracy is the percentage of explicit selections that matched the fixed rule, so a route with twelve correct classifications has 100% accuracy and a route with one false alarm and one miss has 10 correct out of 12 cues, which equals 10 / 12 × 100 = 83.33% accuracy rounded to two decimals. The game shows that percentage on the completion panel; you do not have to derive it yourself. A clean route is a game completion with no misses and no false alarms. These four labels describe what happened on that one fixed route; they do not describe inhibition capacity, attention span, or any diagnostic threshold.
If you want a deeper walk-through of the same four-outcome frame, see Commission vs Omission Errors: A Twelve-Cue Game, which uses the same fixed route to compare the two error families side by side.
Why the Browser Route Stays Discrete
A timer-based no-go design can mistake a hidden browser tab, a notification, an accessibility interruption, or an abandoned page for a meaningful lack of response. The Go / No-Go Test deliberately avoids that pattern. No-go is always a visible deliberate choice rather than an inferred absence.
That design choice makes the interaction less like a traditional CPT and more like a clear browser game. There is no response timer, no reaction-time measurement, no countdown window, and no population norm table. There is also no diagnostic cutoff, no IQ score, no clinical protocol, and no public leaderboard. The page does not request an account, personal profile, camera, microphone, upload, or contact detail. Everything happens on your device, and a single best score may be saved in your browser storage but is not sent anywhere.
This is also why the four-outcome record reads cleanly: every hit, miss, false alarm, and correct rejection is tied to one cue and one chosen action. Familiarity with the rule, your screen reader or input method, ordinary interruptions, screen size, browser behaviour, and normal day-to-day variation can all change a round, so a route result is best read as an accurate description of your visible choices in that one local session. It is an entertainment exercise, not a clinical assessment, IQ test, or attention diagnosis. If you need an evaluation for health, school, work, or accessibility, use an appropriate qualified service.
What the Comparison Leaves Out
Comparing a Go/No-Go task to a Continuous Performance Test is useful, but it also has limits worth naming. The two designs trade off in opposite ways: a Go/No-Go task keeps the rule short and the responses explicit, which makes the result auditable but cuts out the sustained-attention demand that a CPT is built to expose. A CPT keeps the vigilance demand high, but its No-Go answer depends on the response window and the participant staying attentive the whole time.
The Go / No-Go Test stays firmly on the explicit, short-route side of that trade-off, so it cannot replace a clinical CPT or any other diagnostic procedure. What it can do is show the same press-or-withhold rule in a transparent, browser-friendly form, with twelve known cues, twelve known buttons or key presses, and a private record that lists each outcome by name. That is enough to compare the two designs honestly without confusing the browser game for the longer laboratory task.
If you want to keep the comparison theme and look at another pair of browser-based cognitive routes, the article Digit Symbol vs Trail Making: Two Browser Routes Compared sets up a similar short-route contrast between two different rules. The Go / No-Go Test, by comparison, stays focused on a single two-shape rule with one explicit choice per cue.
Related reading: Mental Rotation Accuracy vs Speed: Reading Both Numbers.