Measurement methods
Every result should say what was measured—and what was not.
Updated August 21, 2026. MeterSee uses browser-observed values, disclosed practical thresholds, and explicit user confirmation. It does not turn unavailable data into a pass.
Result vocabulary
Pass means the observed value met the stated practical range. Needs attention means a measurement or user observation crossed a disclosed threshold. Failed means the browser could not complete a required operation. Not tested and Unavailable remain unknown; they are never silently converted to passes.
Microphone method
The pre-call test separates an initial quiet interval from a speech interval. RMS amplitude is converted to dBFS. The quiet interval median estimates background level, while the speech interval supplies peak level. MeterSee warns for no usable speech signal at or below −75 dBFS, speech peak below −35 dBFS, clipping above −1 dBFS or clipped buffers, and estimated background above −38 dBFS. These are practical call-screening thresholds, not calibrated sound-pressure measurements.
Camera method
Resolution and capture settings come from the active MediaStreamTrack. Where supported, frame rate is measured from video-frame presentation callbacks over a short visible sample; otherwise the browser-reported track value is labeled as reported. A stream below 640×360 or below 15 frames per second receives a warning. Focus, lighting, framing, color, and lens quality require visual confirmation.
Monitor timing and visual fields
Refresh timing uses visible-tab animation callback intervals. The displayed estimate is derived from the median frame interval; jitter is the median absolute deviation, and long frames exceed 1.5 times the median. Variable refresh, compositing, power saving, background tabs, and system load can affect the result. Pixel defects, banding, black level, ghosting, sharpness, and uniformity are user observations against generated patterns, not automatic panel measurements.
Headphones, speakers, and gamepads
Audio tests generate defined local signals at a conservative generator level. The site cannot know physical sound pressure or hear a transducer, so routing, phase, bass, sweep, and channel conclusions require the listener. Gamepad buttons and axes are raw browser API values. Neutral-stick calibration uses a disclosed practical warning threshold of ±0.12; games may apply different dead zones and response curves.
Reports and privacy
Diagnostic PDFs are generated locally and distinguish measured values from manual confirmations. Device labels can be hidden. Media, control events, and report contents are not submitted to MeterSee; normal hosting, advertising, and analytics requests are described separately in the Privacy Policy.