Why My Router VPN Slowed Every Device—and Why I Stopped Tunnelling the Whole House

The television began buffering halfway through a programme. In the next room, my partner’s video call froze just as she started presenting. My phone still showed full Wi-Fi bars, so I blamed the broadband provider and restarted the modem.

Nothing improved.

Then my laptop’s cloud upload slowed to a crawl, and I remembered the change I had made the night before: I had moved the VPN from my personal devices onto the router.

Putting the VPN on the router had seemed like the cleanest solution.

After stronger online age checks took effect in the United Kingdom on July 25, 2025, interest in VPNs rose sharply. Many adults were not trying to evade ordinary safeguards; they were uncomfortable repeatedly handing identity or age information to websites and verification services. (1 Ofcom, guidance on age checks for)

I wanted a VPN available whenever I needed it, but I did not want to install and manage another app on every screen in the house.

The router appeared to solve that problem elegantly. Every connected device would inherit the encrypted connection. The television would not need its own app. Phones would remain covered even when someone forgot to connect. Guests would join the Wi-Fi and use the same route automatically.

One installation. One switch. Whole-house coverage.

By the following morning, that single switch had become a bottleneck for everyone.

My first assumption was that I had chosen a congested VPN server. I opened the control panel for the established provider I had configured on the router.

It was a reasonable service to trust. The company had years of public history, detailed router instructions and a large selection of locations. I noticed that the connection was using a distant server, so I moved it closer to home.

The television played normally for a few minutes, then buffered again. My partner rejoined her meeting, but her voice still broke apart whenever somebody opened a large webpage. My upload moved in short bursts and then stalled.

I selected another nearby server.

That changed where the traffic went. It did not change what was processing it.

A VPN running on a laptop encrypts one device’s traffic. A VPN running on a router must handle traffic from every connected device while also managing Wi-Fi, local connections and the router’s normal network duties.

That distinction was the real problem.

Consumer routers are usually built to move ordinary internet traffic efficiently. Once the VPN is installed on the router, its processor must encrypt and decrypt data for the television, laptops, phones, console and background devices at the same time. OpenWrt’s hardware guidance identifies processor capacity as the main limit on router VPN performance.

The number printed on the router box can therefore be misleading. A router may advertise very high Wi-Fi speeds while supporting much lower throughput once VPN encryption is involved. ASUS, for example, lists one Wi-Fi 7 router with wireless capacity measured in gigabits, but its published VPN figures are much lower.

In other words, fast Wi-Fi does not guarantee a fast router VPN.

That explained why every device still showed a strong signal. The wireless connection inside the house was fine. The slowdown appeared after all that traffic reached the router and entered the same encrypted tunnel.

There was another delay as well. Instead of travelling directly to each website or service, traffic first passed through the VPN endpoint. The longer route and shared endpoint added more work to a router that was already struggling.

One phone loading a page did not expose the weakness. A video call, television stream and cloud upload running together did.

I could not inspect exactly how the router firmware was prioritising each connection internally, but the pattern was clear: as soon as several devices became active, the whole house slowed down.

That was why my late-night speed test had fooled me. When I tested the connection alone, the number looked acceptable. During a working morning, the network behaved very differently.

Other home users run into the same trap when they place a VPN on the router for one television or streaming device, then discover that laptops, consoles and calls have been pulled into the same route.

I had treated whole-house coverage as an automatic improvement.

It was actually a trade: fewer installations in exchange for making one small device responsible for everyone’s encrypted traffic.

The obvious response was to buy a more powerful router. A newer model with a faster processor could raise the tunnel’s speed. But replacing functioning hardware felt excessive when only two people in the house regularly needed the VPN.

That was the point at which the solution became simpler.

I did not need to make the whole-house tunnel faster.

I needed to stop sending the whole house through it.

I disabled the VPN client on the router and returned the household network to the direct broadband connection.

The change was immediate.

My partner’s voice call cleared. The television continued without another loading circle. My cloud upload began moving steadily again. Even the smart speaker responded without its usual pause.

The router was back to doing the job it handled well: moving ordinary household traffic.

That fixed the shared network, but it also brought back the reason I had enabled the VPN in the first place. I still needed protected access on my laptop, and I wanted the same option on my phone without rebuilding router rules whenever circumstances changed.

So instead of searching for another router protocol, I moved the decision closer to the devices that actually needed it.

I installed OnlydogVPN on my laptop.

The smaller app did not begin by asking me to choose among dozens of countries. Its interface was organised around the situation I was trying to solve. I selected the relevant preset and connected.

The page I needed opened.

More importantly, it opened without pulling the television, my partner’s meeting and every background appliance into the same tunnel.

My laptop upload continued through the VPN. The video call in the next room remained clear. The television kept streaming over the direct connection. The console was no longer taking an unnecessary detour through a route selected for my work.

Nothing else in the house had to participate.

That was the result I had been trying to achieve with the router setup, but with a better boundary. The VPN stayed on the device that needed it, and the router stopped acting as an encryption gateway for appliances that did not.

The difference was not only speed. It was control.

With the router VPN, one setting affected everyone. Someone starting a game, joining a meeting or turning on the television had no obvious way to know that my VPN choice was changing their connection.

With the app installed locally, the boundary was visible. My laptop used the tunnel when I connected. The rest of the house continued normally.

After the laptop was working, I added the service to my phone. Verification-code sharing let me connect the second device without typing a shared account password across screens.

That small step removed the main argument in favour of returning to the router.

Device-level VPNs often sound inconvenient because people imagine repeating the same registration, configuration and server selection on every device. Here, adding the phone was quick enough that managing two personal devices felt easier than maintaining a whole-house tunnel.

The service does have fewer server locations, a shorter public history and fewer independent reviews than the established provider I had configured first. Someone who needs a large catalogue of specific countries may still prefer the older company.

That was not my requirement.

I needed private access on a laptop and phone without slowing a working call, a television stream and every connected appliance in the house.

There are more technical ways to divide router traffic. Policy-based routing can send selected devices through a VPN while letting others connect directly. For someone comfortable managing firmware, device addresses and routing rules, that can work well.

For an ordinary home, it was more administration than the problem deserved.

The smaller app gave me the same practical separation without turning the router into another project. The laptop could use the VPN. The phone could join when needed. Everything else remained on the fast direct connection.

I had initially judged the setup by how many devices it covered.

That was the wrong standard.

The important question was how many devices genuinely needed the VPN at the same time. In my home, the answer was usually one and occasionally two. Encrypting traffic for everything else consumed processing power and added delay without providing a useful benefit.

The established provider had not failed because it lacked servers or experience. I had placed the VPN at the wrong level of the network. Changing countries could not correct that design choice.

The smaller app worked because it kept the tunnel close to the task. My laptop reached what it needed. My phone could connect without another password. The rest of the household kept the direct connection it had been paying for all along.

The router VPN gave me one switch for every device. Moving the VPN onto the devices that actually needed it gave the house its speed back.