How scoring works
Every scored session gives you two separate results: accuracy and a performance score.
Accuracy
The number of correct answers out of 10, and the percentage. Speed never affects it.
Performance score (out of 100)
Each question earns points based on whether you were right and how quickly you answered. The clock starts only after the interval has finished playing the first time, pauses if the app is hidden or interrupted, and keeps running if you press Repeat — there is no separate replay penalty.
t = active response time in seconds speedFactor = clamp((12 − t) / 10, 0, 1) Correct: points = 6 + 4 × speedFactor Incorrect: points = −3 × speedFactor Score = round(clamp(sum of points, 0, 100))
| Answer | Points |
|---|---|
| Correct within 2 seconds | +10 |
| Correct at 7 seconds | +8 |
| Correct at 12 seconds or later | +6 |
| Wrong within 2 seconds | −3 |
| Wrong at 7 seconds | −1.5 |
| Wrong at 12 seconds or later | 0 |
Why a wrong answer can cost points
A fast wrong answer loses up to 3 points, which discourages guessing. A slow wrong answer costs nothing extra — but it still forfeits the 6–10 points a correct answer would have earned. Ten quick, correct answers score 100.
Interruptions
If the app is hidden or audio is interrupted while you're answering, playback and timing pause until you choose Resume. That question uses a neutral speed factor of 0.5, is labelled as interrupted in your results, and is left out of response-time averages.
Versioning and fairness
This is scoring version 1. Each session stores the version and settings it was scored with, so a future change never rescores your history. Scores are calculated on the server; browser timing is treated as learning feedback rather than competition data, and there is no leaderboard.