"> Audio Latency Test — Measure Bluetooth Delay Online

Audio Latency Test

Measure the delay between triggering a sound and hearing it through your audio device.

Time between audio playback trigger and first audible output in milliseconds. Click Start Test, wear headphones or place a microphone near your speaker, and follow prompts.

♢ Runs in your browserNo installationResults can be affected by browser and system conditions
◴

What does this test measure?

Time between audio playback trigger and first audible output in milliseconds.

☆

Why is this test important?

Measure the delay between triggering a sound and hearing it through your audio device.

▻

How do you run the test?

Click Start Test, wear headphones or place a microphone near your speaker, and follow prompts.

▥

How should results be interpreted?

Under 10 ms is ideal for music production; under 30 ms is acceptable for gaming.

☑

Normal and problematic results

Under 10 ms is ideal for music production; under 30 ms is acceptable for gaming.

△

Technical limitations

Accurate measurement requires a microphone feedback loop which most browsers cannot do.

↘

Why can the score decrease?

Unstable measurements, denied permissions, unsupported browser APIs, background load, power saving, or an incomplete test can affect the result. When a score changes, the result screen explains the reason.

⌕

What should you do if a problem is found?

Use ASIO drivers on Windows, reduce buffer size in audio settings, or use wired audio.

Example Result Explanation

✓ GoodA stable, repeatable result in the expected range. A clear and consistent experience is expected.
△ AttentionSome indicators should be checked again. Reduce background activity and repeat the test under the same conditions.
× ProblemA repeated clear failure or instability means the relevant setting, connection, or device needs closer review.

Frequently Asked Questions

Does this test provide a definitive hardware diagnosis?

No. The test measures signals the browser can safely access and clearly explains its technical limits.

Why can results change between runs?

Background applications, power mode, network conditions, permissions, and operating-system timing can affect results.

How should I repeat the test if I see a problem?

Repeat it on the same device and browser while changing only one condition, so the source of the difference is easier to identify.