Wi‑Fi Speed Test

Measure your wireless download, upload, ping, jitter, and packet loss—and get clear, practical steps to fix slow or unstable Wi‑Fi at home.

How to run an accurate Wi‑Fi speed test

Follow these steps to get reliable results (then compare with Ethernet as a baseline):

1. Be in the same room as your router (line‑of‑sight if possible).
2. Connect to 5 GHz or 6 GHz; avoid 2.4 GHz unless you’re far away.
3. Close background apps, cloud backups, torrents, and VPNs.
4. Pause OS/app updates on all devices on the network.
5. Run multiple tests at different times (peak vs. off‑peak) and average them.

Tip: If your results fluctuate heavily, check the “jitter” and “packet loss” values—these usually indicate congestion or interference.

Quick Wi‑Fi audit (simple checklist)

A quick audit can recover a lot of lost speed and stability:

• Placement: Put the router high and central; avoid closets, metal cabinets, fish tanks, and microwaves.
• Bands: Use separate SSIDs for 2.4 GHz and 5 GHz/6 GHz so you can force faster bands on capable devices.
• Channels: Pick a clear channel. On 2.4 GHz, stick to 1/6/11. On 5 GHz/6 GHz, avoid overlapping with neighbors; DFS channels can be cleaner but may be subject to radar detection.
• Width: Use 80 MHz on 5 GHz and 160 MHz on 6 GHz if your environment is not crowded; reduce width in congested apartments to improve reliability.
• Firmware: Update router firmware; reboot if uptime is very long.
• Interference: Keep distance from microwaves, cordless phones, Bluetooth hubs, baby monitors, and thick walls.
• Client limits: Older phones/laptops may cap speeds (1×1 or 2×2 radios). Test with a modern device to verify ceiling.
• Backhaul: For mesh, use Ethernet backhaul if possible; otherwise place nodes for good overlap, not too close or too far.
• QoS/SQM: Enable Smart Queue Management (SQM) to reduce latency under load (bufferbloat) during uploads/downloads.

Interpreting your Wi‑Fi test results

• Download (Mbps): Affects streaming and downloads.
• Upload (Mbps): Affects cloud backups, live streaming, and sending video in calls.
• Ping (ms): Round‑trip latency; lower is better.
• Jitter (ms): Variation in latency; high jitter causes call/video glitches.
• Packet loss (%): Should be ~0% for smooth apps; any loss can cause dropouts.

Recommended minimums (over Wi‑Fi)

If ping rises a lot while you’re downloading or uploading, your connection likely suffers from bufferbloat. Turning on SQM/QoS and reducing bandwidth sliders to ~85–95% of your plan can help.

2.4 GHz vs 5 GHz vs 6 GHz

• 2.4 GHz: Better range, worse speed; crowded and interfered.
• 5 GHz: Higher throughput, moderate range; good default for most devices.
• 6 GHz (Wi‑Fi 6E): Highest throughput, least interference; short range, requires 6E‑capable devices.

Rule of thumb: Use 5/6 GHz for high‑bandwidth tasks (4K, gaming, large downloads), and 2.4 GHz for long‑range IoT/legacy devices.

Fix common Wi‑Fi problems fast

• Weak signal (RSSI < −65 dBm): Move closer, relocate router/AP, add a mesh node, or upgrade antennas.
• Congested apartment: Narrow channel width (e.g., 40 MHz on 5 GHz), pick the cleanest channel, enable DFS if supported.
• Buffering during uploads: Enable SQM/QoS; set upload bandwidth to ~85–95% of real‑world max.
• Random call dropouts: Move to 5/6 GHz, reduce interference, check for packet loss, and disable power‑saving Wi‑Fi modes on laptops.
• Old hardware: Upgrade routers older than ~5 years; ensure client supports at least Wi‑Fi 5/6.

Compare Wi‑Fi vs Ethernet

Run one test on Ethernet (wired) and one on Wi‑Fi in the same room:

• If Ethernet is fast but Wi‑Fi is slow → optimize Wi‑Fi (placement, bands, channels).
• If both are slow → ISP plan, modem, or outside network might be the bottleneck.

Try our main Internet Speed Test for an overall connection baseline.

Advanced diagnostics (optional)

• Latency under load (bufferbloat): Test ping while downloading/uploading; large spikes indicate queuing issues.
• Airtime utilization: Too many devices or wide channels can hog airtime; consider narrower channels or more APs.
• SNR (signal‑to‑noise ratio): Aim for 25 dB+ for high rates; below 20 dB will cause retries and low throughput.
• Band steering: Guide capable clients to 5/6 GHz; give 2.4 GHz a different SSID if steering isn’t reliable.

See our full Blog for how we measure throughput, ping, jitter, and packet loss.

Frequently asked questions

What is a good RSSI for Wi‑Fi?

• −50 to −60 dBm is strong; −67 dBm is acceptable for VoIP; below −70 dBm is weak and may be unstable.

Which channels should I use?

• 2.4 GHz: 1, 6, or 11 only (non‑overlapping).
• 5 GHz/6 GHz: Use a clear channel; DFS can be cleaner but may change when radar is detected.

Do VPNs affect Wi‑Fi speed tests?

Yes, VPNs add overhead and can change routing, often reducing speeds and increasing latency.

Why does my phone test faster than my laptop (or vice versa)?

Different radios (1×1 vs 2×2), driver quality, and antenna design can change real‑world speeds significantly.

Related tools and calculators

• Internet Speed Test