Wi-Fi Signal Test
Check your connection quality live in the browser — effective type, estimated speed and latency — then learn how to read the numbers and fix weak spots.
Your connection right now
Values come from your browser's Network Information API. Move around your home and refresh to compare rooms.
- Effective type
- —
- Downlink
- — Mbps
- Round-trip time
- — ms
Connection class
Estimated bandwidth
Estimated latency
Your browser doesn't expose live connection data.
The Network Information API isn't available here (common on Safari and Firefox). For a real measurement, run a full speed test instead — it sends actual data and doesn't rely on browser estimates.
Everything runs in your browser. No data about your connection leaves this page.
How the signal test works
This test asks your browser what it already knows about your connection
through the Network Information API. It
returns three values: the effective type (a rough class like
4g), the estimated
downlink in megabits per second, and the estimated
round-trip time in milliseconds. We read those values, score them,
and turn them into a plain-language verdict. Because the numbers are
estimates the browser rounds for privacy, treat them as a quick health
check rather than a precise benchmark.
Browsers deliberately can't see your radio signal strength, your Wi-Fi channel or your network name — that needs operating-system access. So this is an honest, lightweight reading you can repeat in seconds, room by room, to spot where your connection weakens.
How to read your results
Use this guide to judge each value. Latency (round-trip time) matters more than raw speed for video calls and gaming — a fast line that spikes is what makes calls stutter even when the speed test "looks fine".
| Metric | Good | Fair | Poor | What it means |
|---|---|---|---|---|
| Effective type | 4g | 3g | 2g / slow-2g | Browser's overall class of your connection. |
| Downlink | ≥ 10 Mbps | 2–10 Mbps | < 2 Mbps | Estimated bandwidth, rounded by the browser. |
| Round-trip time | < 50 ms | 50–150 ms | > 150 ms | Estimated latency — the lag you actually feel. |
Frequently asked questions
Why is the result different from a full speed test?
This reading comes from the browser's Network Information API, which reports a rounded estimate based on recent activity — not a fresh measurement. It's great for a quick sense check, but a full speed test sends real data to a server and is far more precise.
Why does my browser say "not supported"?
The Network Information API is mainly available on Chrome, Edge and other Chromium-based browsers, often on Android. Safari and Firefox don't expose it for privacy reasons. When it's missing we tell you honestly instead of inventing a number.
Can this measure my Wi-Fi signal strength in dBm?
No. Browsers cannot read the radio's signal strength (RSSI), the SSID, or the channel. Those need operating-system access. This tool reports the connection quality the browser can see, then we point you to OS tools for the radio details.
How do I test the signal in different rooms?
Carry your phone or laptop to each room, wait a few seconds for the line to settle, then refresh the reading. Compare the values room by room to find dead spots — that's usually where a mesh node or a better router placement helps.
A weak reading is a symptom, not the diagnosis
Slow or spiky here? The Doctor runs the full panel — download, upload, ping, jitter and packet loss — then tells you whether the culprit is your Wi-Fi, your router or your ISP, and exactly what to do next.