How to Diagnose and Fix Slow Mesh WiFi Backhaul: Throughput Tests, Node Placement Checks, and Band Locking for eero, Deco, and ASUS AiMesh

You bought a mesh system to eliminate dead zones — but the far satellite delivers a fraction of the speed you get next to the main router. The most common culprit is the backhaul: the link between your mesh nodes. A weak wireless backhaul link, poor node placement, or a misconfigured band allocation will rob every device connected to that node. This guide walks through how to diagnose and fix backhaul problems on the three most popular mesh platforms: Amazon eero, TP-Link Deco, and ASUS AiMesh.

What Is Mesh Backhaul and Why Does It Slow Down?

The backhaul is the data path between your mesh nodes — from the satellite node back to the main gateway. In a wireless backhaul setup, one of your router’s radio bands carries this inter-node traffic in addition to (or instead of) serving client devices. The key problem: when a single band handles both backhaul and client traffic simultaneously, only a fraction of its bandwidth is available to each. Each additional hop in a daisy-chained mesh setup compounds this penalty roughly by half per hop.

Wired Ethernet backhaul avoids this entirely. When nodes communicate over a physical cable, all wireless bandwidth is freed for client devices. See our overview of wired vs wireless mesh backhaul for a deeper look at the architecture.

Step 1: Establish a Baseline — Confirm the Main Router Is Not the Bottleneck

Before blaming the backhaul, verify that the main router itself is delivering your full ISP speed. Connect a laptop directly to the main router’s LAN port via Ethernet and run a speed test at WiFiSpeed. If that number matches your plan speed, the ISP connection and main router are fine. If it doesn’t, the problem is upstream of the mesh system entirely — check your modem and ISP signal first.

Step 2: Run a Throughput Test at Each Node

Stand 1–2 meters from each satellite node and run a speed test on a device connected to that node. Compare the result to your main router baseline. A healthy wireless backhaul should deliver 50–70% of the main router’s speed at the first satellite, assuming one hop. Less than 30% of baseline strongly suggests a backhaul problem.

• eero: Use the eero app’s built-in speed test (Settings → Network Settings → Run Speed Test) and compare per-node results. The eero app also shows each node’s backhaul signal strength under its device details.
• TP-Link Deco: Open the Deco app, tap each unit, and check the signal bar between nodes. Run a manual speed test from a device connected to that satellite.
• ASUS AiMesh: In the ASUS router app or web UI, navigate to AiMesh → Topology to see each node’s backhaul type (wired or wireless) and signal level.

Step 3: Check Node Placement

Poor node placement is the most fixable backhaul problem and requires no hardware changes.

The Half-Coverage Rule

Place satellite nodes at the midpoint between the main router and your dead zone — not at the dead zone itself. A node placed at the far edge of your router’s range has a weak, noisy backhaul link that reduces both backhaul throughput and reliability. Move the node one or two rooms closer to the gateway and you’ll often see backhaul speeds double.

Physical Obstructions to Avoid

• Thick concrete, brick, or stucco walls between nodes reduce 5 GHz backhaul signal by 30–60%. See our guide on mesh WiFi in concrete block homes for material-specific strategies.
• Metal appliances, mirrors, and filing cabinets reflect and scatter 5 GHz signals. Keep nodes at least 1 meter away from large metal surfaces.
• Placing a node inside a cabinet, behind a TV, or on the floor cuts the effective backhaul range by 30–50%. Mount nodes at chest height or higher in an open area.

Step 4: Check Whether Backhaul Is Using the Correct Band

Dual-band mesh systems share one band between backhaul and client devices. Tri-band systems include a dedicated backhaul radio — usually a second 5 GHz radio — that is reserved exclusively for node-to-node communication. If you’re on a dual-band mesh system and your nodes are far apart, upgrading to a tri-band system is often the single biggest performance improvement you can make.

Band Locking on ASUS AiMesh

ASUS AiMesh systems support manual backhaul band selection. In the router web UI (192.168.1.1), go to AiMesh → Topology → select the node → Backhaul Connection Priority. Options are Auto, 5 GHz, 2.4 GHz, or Ethernet. Set it to 5 GHz to force backhaul onto the faster band and keep 2.4 GHz free for IoT devices. If you have a tri-band ASUS system with a second 5 GHz radio, the dedicated backhaul band is selected automatically.

Backhaul Visibility on eero and Deco

eero and Deco do not expose manual band-locking controls to users — both systems manage backhaul band selection automatically based on signal quality. Your best lever is node placement (step 3) and switching to Ethernet backhaul (step 5 below) rather than trying to force a specific band.

Step 5: Switch to Wired Ethernet Backhaul

Wired backhaul eliminates the wireless bandwidth penalty entirely and is the single most impactful upgrade for mesh performance. It requires running an Ethernet cable from the main router to each satellite node, which is often practical using existing cable channels, baseboard raceways, or coaxial runs with MoCA 2.5 adapters.

eero Ethernet Backhaul

Plug an Ethernet cable into any port on an eero node. eero detects the wired connection automatically and switches that node to wired backhaul within 60 seconds — no settings change required. The eero app will show a wired backhaul icon in the topology view once the switch has occurred.

TP-Link Deco Ethernet Backhaul

On most Deco models (M5, XE75, BE95, and similar), connecting Ethernet to a satellite Deco unit automatically enables wired backhaul. Navigate to Deco app → More → Advanced → Ethernet Backhaul to confirm status. Some older Deco models require a factory reset and re-setup after adding Ethernet backhaul; check the TP-Link FAQ for your specific model.

ASUS AiMesh Ethernet Backhaul

Connect an Ethernet cable from your main ASUS router’s LAN port to a LAN port on the satellite node. Then in the web UI, go to AiMesh → Topology → node settings → Backhaul Connection Priority and select Ethernet. Alternatively, leave it on Auto and AiMesh will prefer Ethernet when detected. After switching, reboot both the main router and the node to confirm the change takes effect.

Step 6: Additional ASUS AiMesh Optimizations

If you’re on ASUS AiMesh with wireless backhaul and can’t run Ethernet, two settings in the router web UI can improve backhaul stability:

• Airtime Fairness: Found under Wireless → Professional, this prevents slow legacy 2.4 GHz devices from monopolizing airtime and starving the backhaul. Enabling it typically improves throughput fairness across the system.
• Hardware WiFi Offloading: Found under Wireless → Professional, this moves packet forwarding to dedicated hardware rather than the router’s main CPU, reducing latency under heavy load.

Quick Diagnostic Checklist

Symptom	Likely Cause	Fix
Satellite node <30% of main router speed	Weak backhaul signal	Move node closer to gateway
Speed drops with each mesh hop	Wireless bandwidth halving	Add Ethernet backhaul or go tri-band
Inconsistent speeds throughout the day	Shared band congestion	Lock backhaul to 5 GHz (AiMesh) or upgrade to tri-band
Node placed in a cabinet or behind a TV	Physical obstruction	Reposition at chest height, open air
Wired backhaul not detected	System needs reboot	Reboot both main router and satellite node

The Bottom Line

Most slow mesh backhaul problems trace to one of two causes: a node placed too far from the gateway (fix it by moving the node to the midpoint), or a wireless backhaul sharing bandwidth with client traffic (fix it with Ethernet backhaul or a tri-band system). Run the throughput baseline test first so you know whether you have a backhaul problem at all — many users discover the issue is actually at the ISP level or with the main router, not the mesh system itself.

If wiring Ethernet isn’t feasible and your home has existing coaxial cable, MoCA 2.5 adapters are the next best option: they deliver 1–2 Gbps throughput over the coax you already have, with performance nearly identical to Ethernet backhaul at a fraction of the cost of rewiring.