Why internet calls echo and lag

Echo and delay are different faults with different causes, and it helps to know which one you are dealing with before you start changing settings. Echo is a loop: your caller's voice comes out of your speaker, your microphone picks it up, and it travels straight back to them. Delay is a queueing problem — speech takes too long to cross the network, so you both end up talking over each other and pausing awkwardly. If you hear your own voice a split second after you speak, that is echo. If the conversation feels like a satellite link, that is latency.

Most people blame their broadband speed, but raw download figures rarely explain either problem. A fast connection with poor routing can sound worse than a modest one on a clean path. The numbers that actually matter are upload speed, jitter, packet loss and round-trip time, and you can check all four in a few minutes with a decent connection test.

Fix echo at the source: headsets and microphones

Echo is nearly always an audio hardware problem, not a network one. The quickest test is to switch to a headset: once your caller's voice goes into your ears rather than into the room, the loop is broken.

• Use a boom microphone. Position it two to five centimetres from your mouth and slightly off to one side, so you are not breathing directly into it. A mic on your desk picking up room sound will feed the speaker straight back.
• Avoid speakerphone for anything important. Laptop speakers are usually loud enough to be picked up by the laptop's own microphone, which is why built-in kit struggles most.
• Prefer wired to Bluetooth. A Bluetooth headset adds its own delay — often 100 to 200 milliseconds each way — which makes interruption worse and can confuse software echo cancellation. A wired USB headset is the safest option for a business call.
• Turn the volume down. Echo cancellation works far better when playback is moderate. If the person on the other end is booming in your ears, some of that sound is leaking into the microphone.

Your connection: the numbers that actually matter

Voice uses surprisingly little bandwidth — well under 100 kbps for the audio itself. What ruins calls is inconsistency. Jitter, the variation in how long packets take to arrive, forces your software to build a buffer, and every millisecond of buffer is a millisecond of delay.

As a rough guide, aim for round-trip time under 150 ms, jitter under 30 ms and packet loss under 1 per cent. If any of those are worse, your call will crackle, robot-voice or lag regardless of headline speed.

• Use a wired connection if you possibly can. Ethernet removes an entire class of problems. If you must use Wi-Fi, sit on the 5 GHz band and stay within sight of the router.
• Pause the bandwidth hogs. Cloud backups, photo syncing, game downloads and software updates all compete for upload capacity, which is usually the scarce resource on a home line.
• Watch out for bufferbloat. When one device saturates the line, everything else queues behind it. A router with voice prioritisation, or simple traffic shaping, can keep calls smooth even while someone else is streaming.
• Check whether you are tethered. Mobile data and phone hotspots vary minute to minute. Fine for a chat, risky for a sales call.

Software settings worth checking

Once the hardware is sensible, the app and operating system settings do the rest. These are the ones I would look at first.

• Echo cancellation: on. Noise suppression: on, but experiment. Aggressive noise suppression can clip the start of words and make you sound robotic. If people say you sound choppy, try turning it down a notch.
• Disable automatic microphone gain. Auto-gain creeps upward in quiet rooms and then amplifies background sound, including your own speaker. Set a manual level and leave it.
• Check your sample rate. A mismatch between 44.1 kHz and 48 kHz can introduce crackle. Set the microphone and speaker to the same value, usually 48 kHz.
• Turn off audio enhancements in your operating system's sound settings, and make sure nobody has enabled "listen to this device", which routes your mic to your own speakers.
• Try without the VPN. A VPN adds hops and can add a surprising amount of delay. If calls are consistently bad, test with it off.
• Close the extras. Screen sharing, video, and a dozen open tabs all compete for processor time, and a busy machine drops audio packets.

When the problem is on the other end

A useful diagnostic: if you hear an echo of your own voice, the problem is almost certainly at their end — their microphone is picking up their speaker. If they hear themselves, it is yours. If the delay feels the same in both directions, it is the network between you rather than either device. Ask them to switch to a headset, and nine times out of ten the echo vanishes. For calls to colleagues or clients on the other side of Europe, a long route with many hops will always add a little delay; that is physics, not a fault, and a headset plus a wired connection is the best you can do about it.

A five-minute routine before important calls

• Run a connection test and glance at upload, jitter and packet loss.
• Plug in a wired headset and check the mic position.
• Close downloads, backups and unnecessary applications.
• Move closer to the router, or switch to Ethernet.
• Join the call a minute early and record a short test message to hear yourself back.
• If it still sounds poor, ask the other person to try a headset before you touch anything else.

None of this is glamorous, but it works. Echo and lag are almost always a small number of fixable things — a microphone in the wrong place, a saturated upload, a Bluetooth link doing its best. Sort those, and internet calls become as natural as picking up the phone.