Slow Wi-Fi? Find the bottleneck first.

Define what “slow” means

A download that takes too long and a video call that keeps stuttering are different symptoms. Throughput describes how much data transfers per second. Latency describes delay; jitter describes how that delay varies. A healthy download number does not by itself establish that a connection will behave well during a call.

Write down the affected device, room, application, and time. Try another website or service. If only one service struggles, keep that observation in your notes before changing the whole network. The aim is to narrow the fault, not collect the largest possible speed-test result.

Compare three paths

Use the same device and test service for three short comparisons: your usual spot, close to the main router, and, if available, Ethernet connected to a LAN port on that router. Pause large transfers during the comparison and note whether a VPN is active. Repeat surprising results instead of trusting one run.

This is a diagnostic inference: if Ethernet and nearby Wi-Fi perform well but your usual room does not, wireless coverage or interference deserves attention. If Ethernet is also slow, investigate the wired path, router, and upstream service before assuming a wireless fault. If only one device struggles, compare its software and connection settings with a working device.

A router’s built-in internet test can add another clue. Google explains that its router test measures the path from the router to its servers, while many browser tests include the personal device. Those are different measurements. A speed test is a snapshot of a particular path at a particular time.

Fix the part the evidence points to

Google’s troubleshooting guidance identifies distance, physical barriers, interference, device capabilities, and competing traffic as factors in Wi-Fi performance. If the problem follows your location, try a more open router position and retest. With a mesh system, check the connection between its points as well as the connection from your device to the nearest point.

Avoid changing every radio setting at once. Apple recommends automatic channel selection and a 20 MHz channel width on 2.4 GHz for routers used with its products; wider channels can be more susceptible to interference. Follow your router manufacturer’s guidance, save the previous settings, and compare before and after each change.

If wired tests are poor too, check cables and port capabilities. An Ethernet connection can be constrained by a slower component. Also check the provider’s service status and compare results at different times before buying new equipment.

Measure the symptom again

For calls or gaming, look beyond throughput. Cloudflare’s measurement documentation distinguishes unloaded latency from latency during uploads or downloads. A connection that responds quickly while idle can behave differently when busy. Record latency, jitter, and packet loss when your test exposes them, then retry the application that originally failed.

Keep a small evidence log: connection type, location, time, and observed result. If you contact your provider, those comparisons are more useful than saying the Wi-Fi feels bad. They can also prevent an unnecessary upgrade when the trouble is confined to one room or one device.