TapLab mixes real browser tests with model-based recommendations. This page explains where the numbers come from and what they do — and do not — mean.
← Back to TapLabReaction, click-speed and aim results are measured directly in your browser using high-resolution timing APIs. Browser scheduling, display latency, input devices and background load can still affect results.
System Lab FPS ranges are synthetic estimates built from relative CPU/GPU performance tiers, game workload weights, resolution, graphics target and memory configuration.
They are not laboratory benchmarks and should be treated as planning ranges.
The displayed percentage is a workload-imbalance estimate for the selected game set. It is not a claim that a component permanently wastes that percentage in every application.
Before/after comparisons use the same model on both systems so the relative uplift is internally consistent.
PSU guidance adds modeled system power plus headroom and rounds upward. PSU build quality, connectors, transients and vendor guidance remain more important than one wattage number.
Mouse, graphics and NVIDIA color profiles are starting points rather than universal best settings.
The standalone build stores rankings locally. With the optional backend enabled, nickname and best scores can be shared globally.
Modern CPU gaming tiers are calibrated to the 2026 Tom’s Hardware 1080p gaming hierarchy, while modern GPU tiers are calibrated to its 1440p raster hierarchy. Those source rankings help establish relative component strength; TapLab still applies its own game workload model to produce FPS ranges, 1% low estimates and workload-imbalance percentages.
Hardware not included in the current hierarchy may use legacy or TapLab-estimated relative tiers. See Sources.