Important tool limitations

Measurement Disclaimer

FPS Tester reports browser-visible signals and visual observations. It cannot turn limited web APIs into certified hardware, game, or medical measurements.

Browser FPS Is Not Native Game FPS

Frame tools sample this page’s requestAnimationFrame() timing. They do not read the renderer, presentation queue, graphics settings, or frame rate of a separate native game. Use an appropriate in-game or native capture tool for game FPS. Browser results must not be used as a guaranteed prediction for a named title.

Refresh Rate Is an Estimate

The refresh-rate tool estimates browser-observed cadence from repeated frame intervals and compares it with common standards. It does not directly read EDID, monitor firmware, or every physical scan. Multiple monitors, dynamic or variable refresh, power mode, browser scheduling, and system load can affect the estimate.

Mouse and Reaction Results Include the Browser Path

Mouse rate is based on movement events delivered to JavaScript, not direct interrogation of the USB controller or mouse firmware. Reaction time includes display, browser, operating-system, input-device, and human delays. It is not pure neurological response and must not be used for medical diagnosis.

Gamepad and Controller Results Are Browser-Exposed

The gamepad and controller tools read only states exposed through the browser Gamepad API. They cannot inspect firmware, electrical contacts, or exact USB polling. Browser, operating system, driver, mapping, and device differences affect which controls appear and what values they report. A nonzero stick offset, missing control, or rapid repeated transition is an observation, not proof of a hardware defect. Standard mapping labels describe API positions rather than a console brand or a guarantee about physical legends.

Visual Tests Are Inspection Aids

Dead pixel, screen bleeding, color banding, monitor, screen tearing, motion blur, and UFO tools present controlled fields or moving patterns for visual inspection. They do not automatically detect a defective pixel, quantify panel response time, perform professional calibration, establish a warranty outcome, or certify that a display is defect-free. Fullscreen does not guarantee one CSS pixel maps to one physical pixel, and a clean browser observation does not guarantee identical behavior in another presentation mode.

Results Vary

Browser, operating system, active monitor, window placement, tab visibility, power saving, thermal state, system load, extensions, device state, viewing conditions, and user input can all change results. Repeat under controlled conditions. No result guarantees that hardware is healthy or faulty, detects every issue, or replaces vendor, laboratory, clinical, or professional testing.