Umingle Lag, Freeze and Audio Fixes: The Complete Troubleshooting Guide
You are two minutes into a good conversation and the other person turns into a statue. Or there is a pause before every answer and you both keep talking over each other. Or somebody tells you that you sound like you are calling from inside a washing machine. Three different complaints, three different causes — and the first thing most of us do is apologise for our own internet, when often enough we are apologising for somebody else's, or for a problem a different chair would have fixed.
A live video call has three places it can break: your device, their device, and the long path between the two. This guide works through all three — how to tell whose side a freeze is on, what distance really costs, and how to sound better without buying anything. Every number here is public physics or published engineering guidance you can check yourself; we do not publish measured figures for this service, so none are quoted.
Part 1: Whose side is the freeze on?
Run these checks in order — each one rules something out, and you usually have your answer within four:
- Look at your own preview first. The little picture of yourself in the corner goes from your camera to your screen and never touches the internet. Wave a hand. If it is stuttering too, no amount of router-fiddling will help — the problem is your camera, your browser, or a machine too busy to draw frames. This is the single fastest fork in the whole diagnosis.
- Say something and find out whether the audio survived. Sound and picture travel as two separate streams, and the voice one is tiny by comparison: when a connection struggles, it sheds video quality first and hangs on to the voice. A frozen picture with clean audio is a healthy link doing triage — a call worth staying in. A voice that turns robotic or arrives in bursts is a link running out of room for both.
- Count to five before you touch anything. A large share of freezes are a brief burst of lost packets that resolve on their own. Reloading costs you the connection, the camera handshake, and — on a service that pairs you with a random person — the person. There is no way back to a stranger you have walked out on.
- Check whether the rest of the page still moves. Scroll a little. If the entire interface is stuck, your browser tab is starved of processor time — too many tabs, a video playing somewhere behind the call, an update installing itself. A starved tab and a starved connection look identical and have opposite fixes.
- Take the next hello as a voice-only call. Your outgoing video is the heaviest thing your connection is carrying, and you cannot put it down mid-call — the in-call camera control draws a cover over both pictures, but your video is still being sent, so it frees nothing. Pick voice mode before you match instead. Home connections are lopsided — upload is often ten or twenty times thinner than download — so if voice-only calls run clean all evening while video falls apart, the shortage is on your upload, not on their side and not on the path.
- Find out what else is uploading right now. Photo backup, a cloud folder syncing, a game patching, someone else in the flat on their own call. Background transfers are built to use whatever they can get; pause the one you can pause.
- Look at where you are physically sitting. How far from the router, how many walls in the way, are you on the crowded 2.4 GHz band? A weak wireless link produces exactly the symptoms of a bad internet connection, but the fault is in the last few metres — the one part of the chain you fully control. Move six metres and see whether the problem follows you.
- Watch the pattern across several different people. One frozen call tells you nothing; three in a row, all freezing the same way, tells you almost everything. Random matching means everyone you meet has a different device, provider and country — a random sample of connections around the world. If all of them freeze, the one thing they have in common is you.
- When it really is their side, say so once, then move on. "You are frozen for me — I can hear you but you are not moving" is genuinely useful to them, because a frozen picture looks normal on the sending end. Give it fifteen seconds; if nothing changes, leave kindly and take the next hello. You cannot repair a stranger's router, and skipping is not rude here — it is the design.
- Fix your baseline once instead of every call. If the pattern points at you, spend fifteen minutes outside of a conversation: a cable instead of wireless if the socket is near, a restart before a session, battery saver off (power-saving throttles exactly the work video encoding needs), laptop on a hard surface rather than a duvet (an overheating machine drops frames long before it warns you). A live conversation is the worst possible moment to debug anything.
Two patterns worth knowing: a stutter in the first second or two of every call that never comes back is the beginning behaving normally, not a fault — and both of you freezing at exactly the same moment is the one pattern that points at the path between you rather than either end. Nothing to fix, nothing to apologise for; wait it out.
Part 2: Cross-continent delay — what distance really costs
You say something, there is a pause, then you both start talking at once and apologise at the same moment. Quite often nobody's internet is at fault: you are simply eleven thousand kilometres apart, and the gap you keep tripping over is the time it takes light to cross that distance and come back. Delay on a long call is not a defect — it is a distance.
- Work out the floor for your route. Light in a glass fibre travels at roughly 200,000 km/s. Divide the distance by that and you have the one-way floor in the best case that will ever exist: London–New York about 28 ms, San Francisco–Tokyo about 41 ms, London–Sydney about 85 ms. Double it for a round trip, then expect real routes to land well above the floor — cables follow coastlines and politics, and every hop adds its own small tax.
- Learn the three thresholds. Under about 150 ms one way, nobody notices the delay. Between 150 and 300 you begin to overlap each other by accident. Past 300 you have to take turns on purpose, the way people do on a radio. (These follow the long-standing ITU-T G.114 guidance for interactive speech — not numbers made up for this page.)
- Measure your own baseline. Run a round-trip measurement to something near and something far, once wired and once from where you normally sit. The gap between those two readings is the delay that lives inside your own home — the only part you directly control.
- Take out the hops you own. You cannot shorten the Atlantic, but you can remove a congested wireless link and a VPN that is quietly routing you through another continent. A VPN in particular can double your distance before your traffic even starts heading towards the other person.
- Change how you take turns. On a long-haul call, leave a clear beat after they finish before you start, and drop the reflexive "mm" and "yeah" — on a delayed line they land in the middle of their next sentence. One deliberate beat removes almost all of the collisions.
- Stop reading the delay as a personality. A pause before every answer is not hesitation; a late laugh at your joke is not a polite laugh. When you have thirty seconds of first impression to work with, half a second of transmission delay reads as coldness if you do not know it is there. Assume the wire before you assume the person.
- Watch the wobble, not just the size. A steady 250 ms is a call you can have all evening; a delay swinging between 60 and 400 is the one that stutters. Variation is harder to handle than distance — which is why a call to the other hemisphere can feel better than a call across town on bad wireless.
Two stubborn myths: bandwidth and latency are unrelated (a very wide road across an ocean does not shorten the ocean), and your speed test's 12 ms is measured to a server chosen precisely because it is close. On satellite internet, geometry matters more than geography — a geostationary hop adds roughly a quarter of a second each way before the ocean is even involved. And if your own free hours are unusual, picking which part of the world is awake when you are is a question of clocks, not cables — the time-zone arithmetic is in the night-shift section of our friendship guide.
Part 3: Sound better without buying anything
Somebody says you sound muffled, or far away. The obvious conclusion — your microphone is cheap — is wrong often enough to be worth a section, because a live call compresses your voice hard so it can survive the connection in real time. That compression sets a ceiling well below what the microphone already built into your laptop can produce. Under a ceiling like that, position is almost everything and price is almost nothing. In order of how much difference each makes:
- Find out where the microphone actually is. Not roughly — exactly. On laptops it is usually a pinhole near the top of the screen, on the hinge, or along the front edge; on a phone, a hole on the bottom edge next to the charging port. You cannot aim something you cannot locate, and a surprising share of "bad microphone" is a hand resting over the only hole.
- Halve the distance. Sound falls off steeply with distance, so halving the gap makes your voice substantially louder at the microphone while the fan and the room's hum stay exactly where they were. Your voice does not get better; it gets bigger relative to everything you did not want. A hand's width to a forearm's length is the useful range — closer than that and your breath lands on the diaphragm as a thump on every "p" and "b".
- Take the microphone off the surface you type on. If the microphone is in the laptop and the laptop is on the desk, the desk is part of your microphone — every keystroke arrives through the body of the machine far more efficiently than through air. A folded towel under the laptop costs nothing, which is also why your typing sounds catastrophic to them and almost inaudible to you.
- Talk towards it, but ten degrees off-axis. Speech thrown past a microphone loses its high frequencies first, and high frequencies carry consonants — that is precisely what "muffled" is.
- Give the room something soft. Bare walls and hard floors make the microphone hear your voice once directly and again a few milliseconds later from every wall — the hollow "calling from a bathroom" sound. Curtains, a rug, a bookshelf: you are removing two or three of the flattest surfaces, not building a studio.
- Turn off the steady noise before fighting it in software. The fan, the air conditioning, the open window facing the road. Constant noise is the hardest kind for noise reduction to separate from speech, and when the software works too hard it starts taking pieces of your voice with it — that swimmy, underwater quality.
- Wear wired earphones instead of using the speakers. When the other person's voice comes out of your speakers, your microphone hears it and sends it back; echo cancellation stops that by quietening your microphone whenever they talk, which is why you get clipped off mid-sentence. Any wired earphones remove the loop completely. Wireless earbuds are the trap almost everyone walks into: most switch to a much narrower two-way mode the moment their microphone is enabled, so both your voice and theirs get thinner.
- Record twenty seconds and listen. You never hear yourself the way anybody else does. Record once before you change anything and once after; listen for three specific things — are the consonants crisp or smeared, is there room echo, how loud is everything that is not you. Whichever is worst tells you which step to repeat.
- Check which input the browser actually chose. With a webcam, a headset and a laptop all plugged in, the selected device is not necessarily the one you meant. This is one of the most common causes of "I did everything and nothing changed" — ten minutes spent optimising the position of a microphone that was not being used.
- Only now think about spending money. An expensive microphone in a bad position sounds worse than a laptop microphone in a good one, every time — and on a live call both get squeezed through the same narrow voice channel at the end. If you do upgrade, the cheap thing that gets a microphone close to your mouth beats the expensive thing that sits across the desk.
Sound does more work than picture in a conversation with somebody new. A slightly soft image is easy to forgive; a voice that has to be decoded is exhausting after about ninety seconds, and people leave those conversations without quite knowing why. When both of you are deciding within the first minute whether this is going anywhere, being easy to listen to is a genuine advantage.
The honest summary
Most freezes are not caused by the ocean. They are caused by the last ten metres — a wireless link fighting through two walls, a laptop that is too busy, a backup that chose the worst moment. That is good news, because the last ten metres belong to you and the ocean does not. And when you really are talking to somebody on the far side of the planet with a third of a second between you, that is the world working correctly: leave a beat, keep your own hops short, and enjoy the fact that the conversation exists at all — talking to somebody on another continent is the whole point of meeting people at random on video; the delay is the receipt.
If none of this is the problem and something on the site itself seems broken, write to [email protected] — it reaches a person.