Video Conferencing

Improving Zoom, Teams & Meet call quality

Video calling sits in a brutal middle ground — interactive enough that latency matters, bandwidth-heavy enough that contention matters, and visible enough that small glitches feel like big ones.

The network targets that matter

  • Latency to the meeting server — under 150 ms one-way ideal, under 200 ms acceptable.
  • Jitter — under 30 ms; above that, audio becomes choppy.
  • Packet loss — under 0.5%; above 1% degrades video noticeably.
  • Upload bandwidth — 3 Mbps minimum, 5 Mbps comfortable, 10 Mbps for HD screen sharing.

Wire the call machine

Ethernet eliminates the single most common source of call instability — Wi-Fi jitter. For laptops, a USB-C dock with Ethernet is a one-time purchase that pays back instantly for anyone running multiple calls per day.

Asymmetric upload is the silent killer

Cable plans often advertise 500 Mbps down / 20 Mbps up. That 20 Mbps gets saturated by one cloud backup, one game patch upload, or one family member uploading a video. The call freezes because the upload pipe is full. Fixes:

  • Enable router QoS/SQM to prevent any single flow from monopolizing upstream.
  • Pause large uploads before joining important calls.
  • If calls are core to your work, switch to a fiber plan with symmetric speeds.

VPN considerations

Corporate VPNs route call media through the VPN endpoint, adding latency and a routing detour. Most VPN clients support 'split tunneling' — exclude Zoom/Teams/Meet domains so call media bypasses the VPN.

Wi-Fi mitigation if Ethernet isn't an option

  • Sit within ~15 feet of the AP, on 5 GHz, with line of sight.
  • Close apps consuming the radio — large cloud syncs, streaming on other devices.
  • Reboot the AP weekly if running 24/7.
  • Avoid USB 3.0 hubs near the laptop — they generate interference in the 2.4 GHz band.

What to check during a bad call

  1. Open the platform's stats panel (Zoom: Statistics → Network).
  2. Note latency, jitter, packet loss.
  3. If loss is high — try wiring or moving closer to AP.
  4. If jitter is high — same fix.
  5. If latency is high — distance to server, VPN, or upstream congestion.