You bought a three-pack mesh kit — Eero, Orbi, Google Wifi, Deco, or whatever was on the endcap at Costco. You put one node downstairs, one upstairs, one near the back of the house. And for a while it was better than the ISP router. Then it started doing the thing: rooms that drop, video calls that freeze, devices that “aren’t connected” despite the mesh node being ten feet away.
This post is about why that happens, what “wireless backhaul” actually means, and why a single wired access point in the right location almost always outperforms a three-node mesh system in the wrong ones.
What “wireless backhaul” means and why it matters
Every mesh node needs to get data from your router to the internet. It can do this two ways:
- Wired backhaul: the node is connected to the router via Ethernet cable. It has full-speed, full- duplex, zero-contention access to the router.
- Wireless backhaul: the node uses one of its Wi-Fi radios to talk to the router (or another node), and the remaining radio(s) to talk to your devices. The data hops through the air twice.
The second option is the default on every consumer mesh kit. It’s also the root of most performance problems.
The half-duplex tax
Wi-Fi is half-duplex: a radio can either send or receive at any given moment, not both. When a mesh node uses one radio for backhaul and one for client traffic, those radios are sharing the same medium and time-slicing access to it.
In practice this means:
- Each wireless hop cuts effective throughput roughly in half. A two-hop path (device → node → router) delivers ~50% of the radio’s capacity. A three-hop path (device → node → node → router) delivers ~25%.
- Latency increases with each hop. Not by a lot (usually 5–15ms per hop), but enough for video calls, gaming, and VoIP to feel it.
- The backhaul radio is contending with the same interference that’s affecting the client radio. In a dense neighborhood or a house with heavy log/stone construction, the backhaul link suffers the same attenuation problems as the client link.
This is why mesh kits often work fine in an open-plan 1,800 sq ft apartment and fall apart in a 4,000 sq ft house with stone fireplaces and timber walls — exactly the houses we see across the Wasatch Front.
Dedicated backhaul radios help, but don’t fix it
Some tri-band mesh systems (Orbi, Eero Pro 6E, Deco XE75) dedicate a third radio exclusively to backhaul traffic. This is meaningfully better — the backhaul and client radios don’t compete for airtime. But the underlying physics haven’t changed:
- The backhaul radio is still wireless, still subject to attenuation through walls, still half-duplex.
- A thick stone or timber wall that kills the client- facing 5 GHz signal kills the backhaul signal too.
- Multi-hop topologies (node → node → router) still compound the loss.
Dedicated backhaul is better. Wired backhaul is better still.
What a wired AP actually gives you
A ceiling-mounted access point (UniFi, Aruba Instant On, TP-Link Omada, Ruckus) wired back to the switch on Cat6 has:
- Full-speed backhaul. 1 Gbps on Cat6, 2.5 Gbps on Cat6 with a multi-gig switch, 10 Gbps on Cat6A. No contention, no half-duplex tax, no hops.
- Every radio available for clients. A tri-band Wi-Fi 7 AP with a wired uplink gives all three radios (2.4, 5, 6 GHz) to devices. No radio wasted on backhaul.
- Power over Ethernet. The same cable that carries data powers the AP. No outlet needed, no wall wart.
- Ceiling mounting. The AP goes at the ceiling, center of the coverage area, radiating downward. A mesh node on a shelf radiates sideways through furniture and walls. Ceiling mounting is acoustically better for Wi-Fi in the same way that overhead lighting is better than a floor lamp — physics, not opinion.
- Central management. One controller manages channel assignments, power levels, roaming thresholds, and VLAN assignments across every AP. A mesh kit does some of this; an enterprise-grade controller does all of it, with granular per-AP tuning.
The “but I can’t run Ethernet” question
This is the real barrier, and it’s a fair one. Running Cat6 to the ceiling of three rooms in a finished house isn’t free — it means attic access, crawlspace access, or drywall cuts. In a new build, it’s trivially cheap while the walls are open. In a retrofit, it’s real work.
That said, the cost is usually less than people expect:
- If you have an accessible attic (most Utah homes do), running Cat6 from the attic to a ceiling AP location is a 30–60 minute job per drop.
- If the network closet is in the basement, vertical runs to upper floors can often go through interior-wall chase cavities alongside existing plumbing/electrical risers.
- In genuinely impossible retrofit scenarios (concrete slab, no attic, brick interior walls), MoCA adapters over existing coax can provide a wired-equivalent backhaul to APs, and that’s still far better than wireless mesh.
Our general advice: if you can wire even two APs — one upstairs, one downstairs — the improvement over a three- node wireless mesh is immediately obvious. You don’t need to wire every room; you need to wire every AP.
When mesh is actually fine
Mesh systems aren’t bad. They’re the right answer when:
- The house is small or open-plan — under about 2,500 sq ft with standard drywall-on-stud construction, one or two mesh nodes cover it.
- You rent and can’t modify anything — mesh is portable and self-contained.
- The device load is light — a few phones, a couple of laptops, a TV. No heavy IoT, no cameras, no Sonos multi-room that needs rock-solid multicast.
- Temporary or transitional housing — mesh is deployable in an hour and packs up in a box.
Mesh is a good product for the wrong house. Wired APs are the right product for the right house.
What a real install comparison looks like
For a 4,500 sq ft, two-story home with a finished basement on the east bench:
Three-node Eero Pro 6E mesh kit
- Hardware: ~$500.
- Install: self-install, 30 minutes.
- Typical throughput at far end: 150–300 Mbps (on a gig fiber line).
- Latency: 8–20ms internal, plus ISP.
- Roaming: hit-or-miss, sticky devices hang on to weak nodes.
- VLAN support: none. Guest network is a simple toggle. No IoT segmentation.
Three wired UniFi U7 Pro APs + Cloud Gateway Ultra
- Hardware: ~$700.
- Install: ~$400–600 labor to run three Cat6 drops to ceiling AP locations (attic access assumed).
- Typical throughput at far end: 600–1,200 Mbps.
- Latency: 1–3ms internal.
- Roaming: 802.11r fast roaming, BSS transition managed centrally.
- VLAN support: full. Guest, IoT, Main, cameras — properly segmented.
Total cost difference: $600–800 more for the wired install, with 3–4x throughput, dramatically lower latency, and proper network segmentation. For a house that’s already running 30+ devices — which most homes with cameras, IoT, Sonos, and a couple of gamers do — the wired system isn’t a luxury. It’s what the device count requires.
The mountain-home version
In Park City, Promontory, and Deer Valley, where the houses are larger, the construction is heavier, and short-term rental guests are streaming on a dozen devices, mesh is especially inadequate. We’ve replaced more consumer mesh kits in Park City homes than anywhere else on the Wasatch Front. Heavy timber, full-log, and stone construction attenuate the backhaul link as badly as the client link. It’s physics, and no firmware update fixes physics.
Bottom line
Mesh is easy. Wired APs are better. The gap is widest in larger homes, heavy-construction homes, device-dense homes, and any home where network segmentation matters. If you can wire even two APs — which in most Utah homes with attic access is a half-day job — do it. The throughput, latency, and roaming improvement is immediate and permanent.
Keystone Integration replaces consumer mesh systems with wired AP installs across Murray and the rest of the Wasatch Front — ceiling-mounted, PoE-powered, centrally managed, on customer-owned gear. You can see the full list of what we do on our main site, or get in touch to scope a proper install for your house.