FEATUREDLatestTOP STORIESVOIPWebRTC

Why Is WebRTC So Slow (and How to Fix It)

If you have ever been on a WebRTC call that froze mid-sentence or where the audio lagged behind the conversation, you know how frustrating it is. WebRTC is designed for real-time communication, so when it feels slow, something specific is usually getting in the way. In my experience it comes down to four things: the network, the device, the relay servers and the media settings. Below is how to spot each one and what to do about it.

Common causes of slow WebRTC calls

1. Poor network conditions

WebRTC needs a steady connection more than a fast one. Packet loss, jitter (packets arriving at uneven intervals) and congestion on the upload side cause most frozen video and robotic audio. Voice needs little bandwidth (the Opus codec typically uses tens of kilobits per second), so a voice call that breaks up is usually suffering from loss or jitter rather than a lack of speed. Video needs far more, and an upload of under about 1 Mbps will struggle with HD video. A speed test such as Speedtest shows bandwidth; a tool such as PingPlotter shows loss and latency along the route over time, which tells you more.

2. High CPU usage

Encoding and decoding video in a browser is CPU-intensive, especially with several HD streams or other heavy applications open. When the processor cannot keep up, the browser lowers the resolution or frame rate, and older laptops and phones feel this first. Audio-only calls are much lighter.

3. Relayed media and distant TURN servers

When a direct connection between the two ends is blocked, WebRTC sends the media through a TURN relay. If that relay is far away from the callers or overloaded, every packet takes a longer trip and latency rises. STUN and TURN also affect how quickly a call connects in the first place.

4. Codec and resolution settings

The video codec and resolution decide how much data has to be sent. VP8 and H.264 are supported by every major browser; VP9 and AV1 compress better at the same quality but need more processing power to encode, which can make things worse on a weak device.

How to speed up WebRTC calls

Fix the network first

Use a wired Ethernet connection where possible, and keep large uploads and backups off the same connection during calls. If you rely on Wi-Fi, set up Wi-Fi QoS with DSCP and WMM so voice traffic gets priority. On a phone, see why WebRTC calls fail on mobile data.

Put TURN servers close to your users

If you run your own infrastructure, host TURN servers in the same region as your users. Managed services such as Twilio’s Network Traversal Service and Cloudflare’s TURN service run relays in many locations. For a self-hosted setup with Asterisk, Innovate Asterisk has a guide to STUN and TURN for NAT traversal.

Measure instead of guessing

In Chrome, open chrome://webrtc-internals during a call to see bitrate, packet loss, jitter and round-trip time for each stream; Firefox has the equivalent at about:webrtc. The WebRTC.ventures team has a useful tour of webrtc-internals. Running pre-call tests before users join catches many of these problems early.

Lower the video resolution

A 720p picture has fewer than half the pixels of 1080p, so it needs considerably less bandwidth and processing while still looking clear on most screens. For business calls where the conversation matters more than the picture, turning video off altogether is the most reliable fix of all.

Final thoughts

A slow WebRTC call is rarely a fault in WebRTC itself. It is usually packet loss or jitter on the network, a relay server in the wrong place, or a device that cannot keep up with the video. Measure first, fix the network, and the rest usually follows. For more on the common faults, see 12 pain points in browser VoIP and how to fix them.

Updated 12 November 2026: corrected the network and codec guidance, replaced the Google STUN reference with current TURN services, and added measurement tools for Firefox.

Related: WebRTC topology: SFU vs MCU vs P2P.

Leave a Reply

Your email address will not be published. Required fields are marked *