Reaction Time vs Vertical Jump
The reaction time calculator and the vertical jump calculator are both measured-performance field tests: each one turns a simple, repeatable measurement into a summary statistic you can track over time. The reaction time calculator measures browser-observed latency for a visual prompt across repeated trials and reports best, arithmetic mean, median, and spread. The vertical jump calculator measures jump height from a standing reach and three jump-reach trials, reporting the best jump and the observed range. Neither tool judges performance level, readiness, or injury risk — both are measurement tools with deliberately narrow claims.
Both calculators live in the same measured-performance family on this site, alongside the stride length calculator and the one rep max calculator. Choose the one that matches the ability you want to measure, and track consistent measurement conditions across sessions.
What each calculator does
The reaction time calculator runs a trial in your browser: wait for a randomized visual prompt, then respond with the button or keyboard. A trial starts when the ready callback records its timestamp and ends when the page’s event handler records your response, so the randomized wait is not included in a completed trial. Early responses are discarded, and Reset All clears the complete set. The retained set is limited to 100 completed trials, and the five-row Recent Results section is only a view of the newest five. The result is browser-observed latency, not neurological reaction time — rendering, the event loop, the operating system, and the input device can all add delay.
The vertical jump calculator takes a standing reach and three jump-reach trials. Each trial height equals jump reach minus standing reach, the highest trial is displayed as the best jump, and the observed range across trials is reported alongside it. Calculations use unrounded values with rounding only for display. The reach subtraction provides no power, performance-level, readiness, training, safety, or injury conclusion.
Side-by-side comparison
| Feature | Reaction Time Calculator | Vertical Jump Calculator |
|---|---|---|
| What it measures | Browser-observed latency for a visual prompt | Jump height from standing reach and jump reach |
| Inputs | Repeated visual-prompt trials (button or key responses) | Standing reach plus three jump-reach trials |
| Trial handling | Early responses discarded; randomized wait excluded from completed trials | Each trial = jump reach − standing reach |
| Primary output | Best, arithmetic mean, median, and spread across accepted trials | Best jump and observed range |
| Retained data | Up to 100 completed trials | Three trials, with best and range reported |
| Interpretation boundary | Not neurological reaction time; device and browser latency can add delay | No power, readiness, or injury conclusion |
When to use which
Use the reaction time calculator when the ability you are tracking is response speed to a visual prompt — for example, practicing or logging repeated reaction trials in the browser. Keep the measurement context in mind: the result depends on your device, browser, and input method, and it is not a clinical or neurological measurement. Use the vertical jump calculator when you can take a standing reach and three jump-reach trials and want a repeatable jump-height figure with the spread across attempts. Both tools are most useful when you keep the measurement conditions consistent from session to session, and neither should be used to rank performance, readiness, or injury risk.
Where to start
- Reaction time calculator — repeated visual-prompt latency trials with best, mean, median, and spread.
- Vertical jump calculator — jump height from standing reach and three jump-reach trials, with best and observed range.
Informational note: This page is an educational comparison. Neither calculator measures neurological reaction time, athletic performance level, readiness, or injury risk, and neither provides a clinical, diagnostic, or safety conclusion. Results depend on measurement conditions, so track them consistently.