Start with a clean baseline
Separate the local link from internet reachability and application performance. Wi-Fi marketing speed, Ethernet port speed, ISP speed and browser throughput are different measurements.
Live evidence
Relevant checks
Browser Online Status TestCheck the browser online state, available connection hints, and a short round trip to DeviceOK.
→Browser Latency TestMeasure several browser-to-DeviceOK request round trips as a quick connection responsiveness check.
→Network Information CheckRead browser-exposed connection type, estimated round-trip time, downlink, Save-Data state, and online status where supported.
→First sequence
Do the high-signal checks before risky changes
- 1
Compare another device on the same Wi-Fi
- 2
Compare Ethernet or another network if available
- 3
Inspect adapter state/driver only after broader network checks
Decision points
What the result should change
If one client fails, others workPrioritize the client adapter, saved network, cable/port or device policy.
If all clients lose internet but stay associatedPrioritize WAN/modem/DNS/upstream status rather than each device.
If wired is stable and wi-fi is notPrioritize RF placement/interference/channel/client-band behavior.
Browser can help check
- Test HTTP connectivity
- Show coarse connection hints where exposed
Browser cannot prove
- Read Wi-Fi RSSI/channel on every browser
- Scan radio spectrum
- Replace router/adapter diagnostics
Repair boundary
Know when to stop browser troubleshooting
- Do not factory-reset a managed or ISP-provisioned router before saving configuration and credentials.
- Do not infer 2.5/10GbE from Wi-Fi class names; verify the exact physical ports.
- Browser Network Information API values are hints and are not a replacement for router/switch counters.
Used-device inspection
What to verify before paying or signing off a repair
- Verify exact WAN and LAN port speeds
- Check Wi-Fi generation/bands supported by your actual clients
- Check mesh/backhaul and VLAN/PoE needs before choosing hardware