Start with evidence
Run the tests that separate the likely branches
Browser Latency TestMeasure several browser-to-DeviceOK request round trips as a quick connection responsiveness check.
Run →Browser Network Timing Variation CheckRun repeated HTTP round trips to DeviceOK and show timing variation between samples.
Run →Network Information CheckRead browser-exposed connection type, estimated round-trip time, downlink, Save-Data state, and online status where supported.
Run →Decision table
What the observation changes
ObservationWhat it meansNext action
One client slow, others normalAP hardware failure is less likely.Focus on that client's band, driver and RF position.
Many clients slow and AP uplink is 1GbEWired uplink may be a shared ceiling.Restore/verify 2.5GbE link where required.
High jitter near AP on multiple clientsRF/interference/config or upstream congestion is plausible.Check UniFi spectral/RF and gateway telemetry.
Sequence
Work from reversible checks to escalation
- 01
Verify 2.5GbE uplink and PoE+ state.
- 02
Compare two modern clients.
- 03
Measure latency/jitter before throughput.
- 04
Use UniFi RF telemetry for channel/interference decisions.
Likely areas
Keep these branches separate
Client capability2.5GbE uplinkRF interferenceChannel/band selectionWAN
Repair boundary
When to stop changing settings
Escalate if the AP shows persistent hardware/PoE/link faults on known-good switch/cabling.