what it measures
How the speaker latency test works
A speaker latency test estimates the time between the browser scheduling a sound and that sound reaching you or returning through a microphone. The delay can include browser scheduling, operating-system buffers, drivers, USB or HDMI transport, Bluetooth encoding, amplifier processing, digital signal processing, and the speaker itself.
Mic Round-Trip is the most speaker-specific mode because the microphone listens for short pulses played through the selected output. The result includes playback delay, travel through the room, microphone capture, and input buffering, so it is a practical round-trip estimate rather than a laboratory output-only measurement. Tap Test and A/V Sync provide useful cross-checks when the room is noisy or the microphone cannot detect the pulse reliably.
Best for comparisonsKeep the microphone position fixed and compare one speaker or setting at a time.
No recording uploadTiming analysis runs in the browser while microphone permission is active.
clean setup
How to test speaker delay accurately
Place the microphone 20 to 50 cm from the speaker, reduce background noise, and set a clear but comfortable volume. Select only one output device, close apps that may take exclusive control of audio, and keep the browser tab active. Run at least two passes before treating the average as representative.
For a fair wired-versus-wireless comparison, use the same browser, computer, volume, microphone position, and room. Change only the output path. If a TV or monitor is involved, test with and without game mode, audio enhancements, virtual surround, lip-sync correction, and Bluetooth. For USB speakers or studio monitors, also compare direct ports with hubs and confirm that the sample rate is consistent.
Jitter matters as much as the average. A stable 90 ms result may be easier to compensate than readings that jump between 35 and 160 ms. High jitter can come from inconsistent tapping, room echoes, aggressive noise suppression, CPU load, wireless interference, or an unstable device connection.
Repeat the same modeCompare like with like instead of mixing Tap and Mic results as if they were identical.
Change one settingRecord the baseline, change one option, then run the same speaker latency test again.
read the result
What is a good speaker latency result?
There is no universal pass number because each mode measures a different path. For calls and ordinary listening, a small stable delay may not be distracting. Games, musical performance, live monitoring, and lip-sync work are more sensitive. Once total delay approaches roughly 100 ms, many people begin to notice that sound feels detached from an action or picture, although sensitivity varies by task and person.
Use the measurement as a comparison and troubleshooting signal. If Bluetooth is much slower than wired output, try a low-latency or game mode, move closer to the source, remove competing wireless connections, or use a cable. If a TV or soundbar is late, compare passthrough, PCM, game mode, and built-in lip-sync settings. If every speaker path is high, test another browser and inspect system audio enhancements or virtual devices.
Under 50 msOften feels responsive for everyday playback, though the Mic mode includes input delay too.
Over 100 msCommonly noticeable in games, video sync, instrument monitoring, and interactive work.