Methodology
How Testpartout measures
These are the principles behind every test on the platform. Each test page then documents its own procedure and its own limits in detail.
Platform-wide principles
Measurements use browser APIs
Every Testpartout test is built on standard web platform APIs — pointer and keyboard events, requestAnimationFrame, and related interfaces. What the browser can observe is what the test can measure; nothing is simulated to look more precise than it is.
Timing-sensitive tests use performance.now()
Where a test depends on elapsed time — reaction time, click speed, time-to-target and similar — the measurement is anchored on performance.now(), the browser's monotonic high-resolution clock, rather than wall-clock time.
Methodology is documented per test
This page describes platform-wide principles only. The specific procedure of each test — trial counts, exclusion rules, scoring formulas — is documented on that test's own page, next to the tool itself, and kept in step with the implementation.
Your environment affects the result
Browser, device, display refresh rate and input-device latency all influence a measurement. A score taken on one machine is not directly comparable to a score taken on another, and small differences between runs are normal.
Browser measurements, not laboratory instruments
Testpartout tests are practical browser measurements. They are useful for comparing your own runs and spotting changes, but they are not calibrated laboratory equipment and should not be read as clinical or scientific measurements.
No invented population averages
Testpartout does not publish population averages, global percentiles or rankings that are not backed by real aggregated measurements. Until such data genuinely exists, no comparative statistics are shown.
Personal bests are currently local
Where a test keeps a personal best, it is stored in your browser's local storage on your device. It is not uploaded, and clearing your browser storage removes it.
Future benchmarks will use real data only
If aggregated benchmarks are ever introduced, they will be computed from real measured results and labelled as such. Synthetic or placeholder statistics will not be published in their place.
Per-test methodology
The detailed method for each live test — including what the implementation does and the limits of a browser measurement — is on the test's own page:
- Reaction Time TestMeasure how fast you respond to a visual cue, in milliseconds, across repeated attempts.
- Typing Speed TestWords per minute, accuracy and mistake patterns over a timed typing passage.
- Click Speed TestClicks per second over a fixed interval, with consistency across attempts.
- Visual Memory TestRecall increasingly complex patterns to measure your visual memory span.
- Sequence Memory TestRepeat growing sequences to find the longest order you can hold and recall.
- Aim / Accuracy TestHit targets under time pressure to measure accuracy, hits, misses and time-to-target.