Optimize WiFi with evidence, not a fake signal meter
A standard web page normally cannot read WiFi signal dBm, channel utilization, nearby access points, or radio retries. Use the router, access-point controller, or operating-system tools for radio evidence, and use browser tests for browser-to-edge performance.
Source reviewed July 10, 2026.
Build a baseline
- Select one device and note its model, operating system, and WiFi adapter.
- Record the access point, band, channel, and signal information shown by a trusted OS/router tool.
- At one fixed location, run several browser-to-edge tests and retain the median and spread.
- Record the time and other active network traffic.
Change one variable
| Variable | Controlled change | Evidence to record |
|---|---|---|
| Location | Move the same device to one documented location. | OS/router signal and link data; repeated throughput and RTT. |
| Access point | Associate with one identified access point while other conditions stay fixed. | AP identifier from managed tooling; repeated results. |
| Band | If both the device and network support it, compare configured 2.4 GHz and 5 GHz operation. | Reported band/channel, signal, link rate, retries if available, and application result. |
| Channel plan | Change only through the router/AP interface and vendor guidance. | Before/after channel utilization and repeated results; do not infer from a browser score. |
| Wired control | Use a known working Ethernet connection on the same device when available. | Matched wired and wireless test series. |
Band and placement guidance has conditions
Microsoft's current Teams network guidance says 2.4 GHz may provide an adequate experience depending on access-point placement, while 5 GHz is better suited to real-time media in dense deployments but requires enough access points for coverage and compatible endpoints. It also advises planning bands and access-point placement, avoiding adjacent same-channel access points, and following the wireless vendor's specific guidance.
That is not a universal instruction to force 5 GHz on every device. Coverage, device support, building layout, and the managed design determine the appropriate configuration.
What the site's browser diagnostic shows
- Network Information API values only when the browser exposes them; MDN describes
downlinkas an estimate rounded for privacy. - First-party HTTP throughput and RTT observations when a comprehensive test runs.
- A site-defined diagnostic score whose inputs are displayed.
Unavailable values remain unavailable. The page does not substitute assumed speed, signal, channel, or latency.