If you work hybrid from Falkirk and your Teams or Zoom calls keep freezing — even though your speed test says everything is fine — you are not imagining it, and you are not the only one. We see this pattern almost every week from the new builds around Carronshore and Maddiston, the Victorian stone terraces in the town centre, and the modern semis around Larbert and Stenhousemuir.
The frustrating bit is the disconnect: a speed test reports 200 Mbps down, the router lights look normal, and the BBC iPlayer stream in the next room is fine. But your video call still breaks up at the worst possible moment. That gap between "fast internet" and "stable call" is real, and it has a few specific causes worth understanding before anyone calls a technician.
The "But My Speed Test Was Fine" Problem
A speed test measures one thing: how fast a big file can move between your device and a nearby server, right now, for a few seconds. A video call measures something completely different: whether tiny packets of audio and video can be delivered consistently, in order, every few milliseconds, for the entire length of the meeting.
You can have brilliant download speed and still have a dreadful call, because the two depend on different qualities of the connection. Speed is about size. Calls are about steadiness. The technical words for the things that wreck a call are latency, jitter, and packet loss — and none of them show up on a normal speed test.
What Actually Breaks a Video Call
Latency is how long a packet takes to get from your device to the other end. Jitter is how much that delay varies from packet to packet. Packet loss is exactly what it sounds like — small bits of the conversation never arriving. A call only needs a couple of percent packet loss, or twenty milliseconds of jitter, to start sounding like everybody has turned into a robot, even if your raw speed is plenty.
Teams, Zoom, Google Meet and Webex all do the same thing when they hit these problems: they degrade the call to try and keep it alive. Video drops to a blur, audio glitches, and eventually somebody freezes on screen mid-sentence. By the time it looks bad on screen, the underlying network has been wobbly for several seconds already.
The Real Culprits We See on the Bench
When somebody brings a call-quality problem to us, the cause almost always turns out to be one of a small number of things. The first is the 2.4 GHz Wi-Fi band being overcrowded — particularly an issue in Falkirk terraces and town-centre flats where you can see ten or fifteen neighbouring networks all fighting for the same airspace. The second is the ISP-supplied router sitting in a hall cupboard or a meter box, with your home office two thick walls away.
The third is interference from a household source: a microwave that runs through the school-lunch slot, a baby monitor on the wrong channel, an old wireless doorbell, an early-generation smart plug. The fourth, and the one nobody likes to hear, is the ISP router itself being end-of-life — a five-year-old ISP-supplied router shared between a working-from-home laptop, two phones, a smart TV, two doorbells and a robot vacuum has a hard life.
A Recent Falkirk Story
A customer working hybrid from a new-build off Maddiston Road rang us in May. Teams calls had been dropping for a fortnight, always mid-afternoon, and his manager had started commenting on it. Speed test: 270 Mbps down, 35 up. Router lights: normal. He had already followed every "five quick fixes" article on the web and was about to spend a small fortune on a mesh kit.
On the bench-side, we ran a continuous ping and a jitter trace from his work laptop while he sat there. For the first ten minutes everything looked clean. Then, on the dot, the jitter chart went vertical and packet loss climbed to about four per cent. The cause? His neighbour's child had come home from school and started a Roblox session over an old 2.4 GHz extender that was hammering the same Wi-Fi channel his ISP router defaulted to. Forcing his laptop onto the 5 GHz band and pinning the router to a less-crowded channel fixed it. No new hardware needed.
What to Try Before Calling Anyone
If you want to rule out the simple stuff yourself, there are a handful of steps that genuinely help. Plug the laptop into the router with an Ethernet cable for one call and see if the problem disappears — if it does, you have a Wi-Fi problem rather than an internet problem, and that narrows things down enormously.
Make sure your device is connected to the 5 GHz network (often the network name ends with "-5G") rather than 2.4 GHz. Move the router out of the cupboard or the meter box if at all possible — Wi-Fi hates being boxed in. Power-cycle the router properly: off at the wall for sixty seconds, then back on, not just a quick reboot. And close other bandwidth-hungry things on the network during the call — a cloud backup mid-meeting will fight the call for every packet it can grab.
When It's Time to Get Help
If the problem keeps coming back, or only happens at certain times of day, or the router is more than four or five years old, it's worth getting somebody to actually measure what's happening rather than guessing. A proper survey takes about an hour and turns up the real cause — a dying router, a poorly-placed access point, a duff cable from the master socket, or genuine ISP-side packet loss that needs raising with the provider.
We cover Falkirk, Larbert, Stenhousemuir, Grangemouth, Bo'ness, Maddiston and the surrounding M9 corridor for networking and Wi-Fi work, often as a single home visit. A lot of the diagnostic side can also start with a remote support session — we connect in, run the right traces while you're on a call, and tell you honestly whether you need new hardware or just a tweak to the existing setup. For Falkirk businesses doing serious hybrid working, the same tools roll into our wider business IT support.
The Honest Bottom Line
"Fast internet" and "good calls" are not the same thing, and your speed test result is not the answer. If your video calls keep dropping on what looks like a perfectly healthy connection, somewhere in the chain — the airspace, the router, the device, the placement — there's something specific causing it. It's almost never the broadband line itself, and it's almost always fixable without ripping out and replacing your kit.
Last updated: 30 June 2026