Two laptops on the same UniFi access point can get different speeds because they may not be using the same Wi‑Fi path. One may be on a different band, using a different adapter or driver, or negotiating a lower link rate. Start by testing both laptops the same way, then check UniFi client stats before changing AP settings. If the wired uplink, switch port, or internet path is the real bottleneck, Wi‑Fi changes won’t fix it.
Symptom
You can see one laptop is fast and the other is slow, even though both connect to the same UniFi AP. The gap may show up on a browser speed test, a file copy, or a local network transfer. It often changes with room position, band choice, or battery status.
The confusing part is that both devices can still show a decent signal bar. Usually, the real difference is lower down: band choice, channel width, PHY rate, retries, power saving, or the wired path behind the AP.
Before you start
Before you change anything, make sure you are comparing like with like.
- Put both laptops in the same room, ideally side by side.
- Connect both to the same SSID.
- Confirm they are on the same band before you compare the numbers.
- Use the same test server for both laptops.
- Better yet, test against a wired host on the same LAN with
iperf3so the internet is not part of the result. - Disconnect Ethernet docks, adapters, and any VPN or proxy.
- Run one test at a time so the two laptops are not competing with each other.
If you skip this step, you can end up fixing the wrong thing. I’ve seen a laptop look “bad” only because it was on 2.4 GHz while the other one was quietly on 5 GHz, or because the internet server changed between tests.
1. Compare the two laptops fairly
First, make sure the comparison is real and not an artifact of the test setup. You want both machines tested in the same place, on Wi‑Fi only, with the same band and the same target. Then repeat the test after swapping positions so you can see whether the gap follows the laptop or the location.
- Put both laptops in the same spot.
- Confirm both are connected over Wi‑Fi only.
- Check that both are on the same band: 2.4 GHz, 5 GHz, or 6 GHz.
- Use the same local test target, or the same internet speed-test server if you do not have a LAN test host.
- Run each test separately.
- Re-run the test after swapping the laptops’ positions to see whether the gap follows the laptop or the location.
If the gap moves with the laptop, the client is the likely suspect. If the gap follows the spot in the room, the RF environment or AP placement is more likely. When both laptops are slow in the same way, look past Wi‑Fi and check the wired side.
2. Check the laptop first when only one device is slow
The most common laptop-side causes are the wireless adapter, the driver, power saving, and the Wi‑Fi generation of the card. A Wi‑Fi 5 adapter, a basic Wi‑Fi 6 adapter, and a better 6E-capable card do not behave the same way on the same AP.
On the slow laptop, check these items first:
- Adapter model and Wi‑Fi generation.
- Driver version.
- Power saving settings for the wireless adapter.
- Whether a vendor Wi‑Fi utility is overriding Windows settings.
- Whether the laptop is sticking to 2.4 GHz instead of 5 GHz or 6 GHz.
A laptop can show a strong signal and still negotiate a low PHY rate. In that case, the AP is often not the limiting factor; the client radio or driver is. Bluetooth coexistence can also reduce throughput on some laptops, especially in thin systems with crowded antennas.
If the laptop is on an older adapter or a stale driver, fix that before you touch the AP. That is a cleaner, lower-risk change, and it often explains the difference on its own.
3. Read UniFi client stats before changing AP settings
Open the client view in UniFi Network and look at the fields that describe the actual link, not just the speed test result. The first things I check are the client’s band, RSSI, PHY rate, retries, and recent client history.
What those usually tell you:
- Same AP, but each laptop is on a different band: the band choice is part of the problem.
- Similar RSSI, but one laptop has a much lower PHY rate: the client radio, driver, or channel conditions are more likely than distance.
- High retries or unstable history: the link is fighting interference or moving around.
- One laptop keeps landing on 2.4 GHz while the other uses 5 GHz or 6 GHz: the weaker client is probably being pushed onto the slower band.
- A DFS channel that changes unexpectedly: the AP may be reacting to radar events and moving clients.
If the laptops show similar RSSI and similar PHY rate on the same band, the AP radio is less likely to be the main cause. If one client keeps dropping to a lower rate or bouncing between bands, focus on the radio path before you touch anything else.
4. Check the AP and wired side when both laptops look similar
If both laptops are slow in the same way, or they look fine on a local LAN test but not on an internet test, stop treating it like a Wi‑Fi-only problem.
Check these wired-side items:
- The AP uplink speed in UniFi.
- The switch port speed and any errors.
- The cable and its seating at both ends.
- Whether the gateway or internet link is congested.
- Any policy or isolation setting that could affect the test traffic.
This is the clean split I use: if a local iperf3 test to a wired host is good but the internet test is poor, the bottleneck is outside Wi‑Fi. If the two laptops both cap at about the same level on both tests, the AP uplink, switch port, or cabling deserves attention before you change channel width or band steering.
That sequence matters. Changing Wi‑Fi settings first can make the symptoms look different without actually fixing the limit.
5. Change the smallest thing that matches the bottleneck
Once you know where the limit is, make one change at a time.
- If the slow laptop is the problem, update the driver, check adapter settings, and disable aggressive power saving on that client first.
- If the laptop is stuck on the wrong band, adjust band selection or band steering only after you’ve confirmed that is what the client is doing.
- If UniFi shows a low PHY rate with decent RSSI, review channel width and channel choice on the AP.
- If both laptops are capped on the wired test too, fix the uplink, switch port, or upstream internet before touching Wi‑Fi settings.
Leave channel width, roaming, and band steering alone until the bottleneck is proven. Random tuning makes it harder to tell whether you helped or just moved the problem.
Verify
You’ve fixed the right layer when the laptops behave the way you expected in a repeatable test. At that point, the comparison should be stable, and the remaining gap should match a known hardware difference or disappear.
- Both laptops are tested in the same spot, on the same band, with the same server.
- UniFi shows a sensible RSSI and PHY rate for each client.
- The slower laptop now tracks the faster one, or the remaining gap lines up with a known hardware difference.
- A local
iperf3test and an internet speed test point to the same bottleneck, not two different ones.
If the numbers are still inconsistent, go back to the test setup first. In troubleshooting like this, a bad comparison is often the whole story.
Conclusion
If you want the fastest path to the answer, start with a fair same-band test, then check the UniFi client stats, then decide whether the laptop, the AP radio, or the wired uplink is really at fault.
Frequently Asked Questions
How do I prove the AP is or isn’t the cause?
Test both laptops in the same place, on the same band, against the same local host or the same speed-test server. Then compare UniFi client stats. If the difference only appears on one AP and the band, RSSI, and PHY rate are otherwise similar, the AP or its radio settings move higher on the list.
Should I change channel width or band steering first?
Not until you know where the bottleneck is. If one laptop is stuck on 2.4 GHz or a low PHY rate, those settings may matter. If both laptops are capped on the wired test too, changing them won’t solve the real problem.