Published Aug 19, 2026, 5:00 PM EDT His love of PCs and their components was born out of trying to squeeze every ounce of performance out of the family computer. Tinkering with his own build at age 10 turned into building PCs for friends and family, fostering a passion that would ultimately take shape as a career path. Besides being the first call for tech support for those close to him, Ty is a computer science student, with his focus being cloud computing and networking. He also competed in semi-pro Counter-Strike for 8 years, making him intimately familiar with everything to do with peripherals. For the better part of a year, I blamed my Wi-Fi for terrible video call performance. Calls would freeze periodically, but when I would run a speed test, I'd get the rated speed that I paid for. No matter what device I tried, if it wasn't on a wire, I'd be a smeary mess for the other person. The fix was turning on QoS in my router settings, which turned out to be something that actually limited my top speeds. Despite that, flipping it on completely fixed the connectivity issues I was having, and it did the same for everyone else in my household. Video calls aren't as demanding as you might think It's a consistency issue Intuitively, you might think that video calls are demanding on your internet bandwidth, but it's actually fairly minimal. An HD group call can be anywhere between 3 and four megabits per second in each direction, and audio only drops to a fraction of that. Screen sharing is lighter still, and even if you were to stack a 4K video stream and a game download, you're still probably using a sliver of a multi-gig connection like I was. The catch comes in the form of consistency, and this is where the problems arise. During a meeting or family FaceTime, that sliver has to be there every second without interruption, while everything else in the house competes for the same path. Conferencing apps can handle scarcity somewhat gracefully at least, because they're able to drop resolution and framerate before dropping video completely. When packets arrive in unpredictable bursts rather than a steady stream, the codec has nothing to work with, and no matter how much headroom you have in terms of bandwidth, it won't matter. On a consumer router, prioritization has a cost Turning on QoS doesn't come without a price The ASUS ROG Rapture GT-AXE16000 allows for QoS prioritization based on several categories.AmpliFi Alien allows for QoS settings by individually labeling devices as normal, streaming, or gaming. On my TP-Link Archer router, turning on QoS asks you to enter the maximum upload and download bandwidth that your ISP gives you, then set priority percentages and flag specific devices and applications. As soon as you lock in that number, that tells the router what the ceiling is for your connection, and it holds you to it. The second concession is larger, but less obvious. TP-Link's own explanation of this is actually quite clear, and it was refreshing to read. NAT acceleration works by forwarding a frame the moment it knows where the frame is going, while prioritization works by requiring the router to hold packets and decide what goes first. These are mutually exclusive by design, because if you turn on QoS, you drop into software-based forwarding, and the silicon that's in a consumer router simply cannot push gigabit-class traffic through software. The result is a severe drop in throughput in a lot of cases. Queue buildup, known as bufferbloat, is a large part of this. If you're on multi-gig, the bottleneck is in your house Bufferbloat on fast connections is different When it comes to solving bufferbloat, it's about finding where the bottleneck is, and in a lot of cases, it's not at your ISP. On a slower cable connection, it's unmistakably your ISP handoff, and an oversized buffer there takes hundreds of milliseconds to drain. Shaping just below the line rate transforms the experience. On a symmetric multi-gig line, that same buffer empties almost instantly, and plenty of people with fast fiber have enabled smart queuing, watched their throughput collapse, but seen their latency refuse to budge. The bottleneck has moved closer to your devices. A multi-gig line feeding gigabit LAN ports is one way you can see a bottleneck, but Wi-Fi is a bigger one, especially for video calls. A phone uploading photos in another room can absolutely mess with the quality of your call, and that's why fixing it at the router level fixes it for everyone. Modern hardware should be able to handle this on its own And it often does If you're on a newer router, this is mostly a solved problem. Wi-Fi 7's multi-link operation specifically exists to stop the wireless hop from injecting any additional delay, and you can definitely feel it if you've used it before. The problem is, even with the defaults set as such, you can still experience poor performance, and most client devices ship with the single radio variant rather than true simultaneous operation, so the best case scenario differs from your case quite considerably, even if the settings are set correctly. Flipping a switch can often be a fix, but it's not one size fits all, as is the case with most wireless networking. It doesn't hurt to try it Run a bufferbloat test before you change anything, then run it afterward. If your numbers barely move, turning off QoS (and anything else you tried) gives you your bandwidth back, and you've eliminated a possible cause. If your calls are still unreliable on a connection that tests well, there are likely multiple factors at play, and more troubleshooting is needed.
I deliberately gave up some of my internet speed, and every video call in the house got better
Full Article
Original Source
Read the full article at Xda-developers →KhanList aggregates and links to publicly available news content. We do not host full articles from third-party sources. Always verify important information with original sources.