Bluetooth and audio latency test

See how many milliseconds your Bluetooth headphones, speaker or audio setup lags behind, measured 10 times.

Choose how to measure

Loopback for speakers: the mic hears the clicks. Tap test for headphones: you tap along. Start with the volume low.

Average—
Spread—
Runs used—
Verdict—

Device

The name is saved with each result, so the recent list compares your devices.

Clicks

Loopback clicks are short chirps 0.8 s apart; tap-test clicks are a steady 80 beats per minute. The first 4 tap-test clicks are for finding the beat and are not counted.

Browser latency

Baseline

Microphone

Sound is analysed on this device and never uploaded. Echo cancelling and auto gain are switched off where the browser allows.

Export and share
Recent results
    Sound never leaves your device. Nothing is uploaded. Space start/stopT tapB baseline

    How to use the latency test

    Loopback is the exact method and works when the microphone can hear the sound:

    1. Connect the speaker or headphones and set the volume low. Type the device name under Device.
    2. Put the phone or laptop mic close to the speaker. For headphones, hold one ear cup right over the mic.
    3. Press Start and allow the microphone. Ten short chirps play, 0.8 s apart. Keep quiet.
    4. Read the average delay, the spread and the verdict. Press Baseline on a wired result to compare the next device with it.

    Tap test is for headphones you cannot hold to the mic. Choose it, press Start clicks and tap the big button (or press T) on every click you hear, 16 in all. The first 4 are only for finding the beat. Your own timing is part of this number, so use the tap test the same way on each device and compare the results with each other.

    How to read the result

    click sent heard by the mic delay 212 ms echo time →
    The made-up demo speaker: the mic hears each click 212 ms after it is sent.

    The average is the delay to quote. In loopback mode it is the full trip: out of the browser, through the device and the air, into the mic and back into the browser. Even a wired speaker never reads zero this way, because the sound card adds a little on the way out and on the way in. Save that as your baseline: the extra delay of a Bluetooth device is its result minus the baseline.

    The spread (±) shows how much the 10 runs differ. Bluetooth links buffer the sound and the buffer changes size, so a spread of 10 ms or more is normal for them. The verdict uses the average: under 40 ms is great even for video, 40 to 150 ms is noticeable in games, and over 150 ms makes lips and voices drift apart. Under Browser latency you can see the output delay the browser itself reports, where it gives one. To see the click itself, see the click on a scope.

    A run marked × on the chart was too quiet to time; if several are, raise the volume a little or move the mic closer. A single run far from the others, for example one at 400 ms among runs near 200 ms, usually means the mic caught a noise or an echo instead of the click, so the tool leaves it out of the average and tells you. In the tap test, a negative offset simply means you tapped a little before the click, which many people do with a steady beat.

    Use cases

    Gaming headset

    Many wireless headsets have a gaming or low-latency mode. Measure with it off, save that as the baseline, then switch it on and measure again; the recent list shows both side by side with the difference. If a mode takes you from, say, 190 ms to 70 ms, footsteps and shots will line up far better with the picture. A USB dongle headset is worth testing against the same headset over plain Bluetooth.

    Lip-sync for video

    If voices on a TV or a laptop seem late, measure the speaker or soundbar you watch with. Many TVs and video players have an audio delay or lip-sync setting: use the measured number as a starting point, for example set 200 ms if the soundbar measured 200 ms more than the TV’s own speakers. Then fine-tune by eye on a clip with clear speech.

    Music practice

    Playing along with a backing track, a metronome app or a digital piano through Bluetooth headphones can feel sluggish, because the sound reaches you late. A wired result near your baseline means the delay is low enough to play in time comfortably. If the Bluetooth result is 150 ms or more, use wired headphones for practice and keep the wireless ones for listening.

    Typical latencies

    These are rough ranges, not promises: the same headphones can measure differently on another phone, laptop or app, so measure your own setup.

    ConnectionTypical delayNotes
    Wired headphones or speakersUnder 10 ms, plus the deviceThe phone or computer’s own audio path adds a little on top.
    Bluetooth, standard codecs (SBC, AAC)Usually 100–300 msVaries with the phone, the headphones and the signal; the spread is often large.
    Bluetooth low-latency modes (aptX Low Latency, gaming modes)Often near 40–80 msBoth ends must support the same mode.
    Bluetooth LE Audio (LC3)Depends on the deviceBuilt to allow shorter delays than classic Bluetooth; measure it to know.

    Remember that loopback numbers also include the microphone path, which is why a baseline helps. If one speaker seems both late and thin, check its wiring with the polarity test. More tests are in the speaker and audio test tools.

    FAQ

    How much latency do Bluetooth headphones have?

    Usually 100–300 ms; low-latency codecs and gaming modes can get near 40–80 ms.

    What latency is noticeable?

    Most people notice over about 40 ms in games and over 100 ms in lip-sync.

    Why does the result vary?

    Bluetooth buffers change from moment to moment. The tool averages 10 runs and shows the spread.

    Can it test wired headphones?

    Use the tap mode; wired delay is usually tiny (under 10 ms plus the device).

    Written and tested by the SpectrumAnalyzer.app team · Last checked

    How we tested: Checked with made-up two-channel recordings of a speaker with a known delay (from 5 ms to 400 ms, with jitter, a wall echo and room noise) fed through the same code as the live test, and with made-up taps of known offset for the tap test.