Wired is fast; Wi-Fi is slow
Test close to the router, then in the problem room. Compare a second device. Reposition the router and check the band and device capability.
Follow the Wi-Fi steps →Four numbers describe different parts of one test route. Use them together, then repeat under comparable conditions before deciding whether your device, Wi-Fi or plan needs attention.
Mbps means megabits per second, a rate of data transfer. It is different from MB/s, megabytes per second: eight bits make one byte, before accounting for overhead. A 100 Mbps reading is therefore roughly 12.5 MB/s as a simple unit conversion, not a promise that every download will transfer at that rate. The remote server, protocol, device and route also matter.
Ping and jitter are measured in milliseconds. A lower ping to this site can indicate a more responsive path, while lower jitter indicates more consistent timing. There is no universal “good” threshold that predicts every video call or game: each service reaches a different destination and has its own buffering and performance needs.
Test close to the router, then in the problem room. Compare a second device. Reposition the router and check the band and device capability.
Follow the Wi-Fi steps →Check the plan tier, Ethernet port and cable, then pause background traffic. Retest at another time and record a series for provider support.
Follow the wired steps →Watch upload and jitter. Pause backups or uploads and test again. A high download number alone does not guarantee a stable call.
Follow the call and gaming steps →Compare wired readings at several times. Household demand and congestion elsewhere on the route are possibilities; a browser test cannot locate the exact fault.
Record an evening pattern →Use the first comparison to change only one condition at a time. This does not identify the fault automatically; it creates stronger evidence for the next decision.
Confirm the subscribed tier, check that the Ethernet link is not stuck near 100 Mbps, pause other traffic and repeat at a quiet time and the problem time.
Check an Ethernet cap →Pause cloud backup, camera sync and large sends. Compare the result with the plan’s separate upload tier instead of the headline download number.
Record upload evidence →Repeat with other household traffic paused, then with normal activity. AI Speed measures unloaded HTTP timing to this endpoint, not packet loss or loaded latency.
Understand latency under load →Test the affected app directly. Its server, route, account, device or service status can still be the bottleneck; one general speed test cannot certify every destination.
Run the guided diagnostic →For support, save several comparable readings rather than the single worst result. The connection worksheet records date, time, device, Ethernet or Wi-Fi, other traffic and the four measurements without sending the record to AI Speed.
A retail tier and a browser reading answer different questions. Your measured number includes the device, Wi-Fi or Ethernet link, router, other traffic, route and the test endpoint. Start with the wired baseline and several dated runs. If they remain far below the subscribed tier, ask your provider what to expect at the modem or optical terminal and provide the conditions you recorded. Read why tests disagree before relying on a single result.
The CRTC’s universal service objective calls for access to at least 50 Mbps download and 10 Mbps upload with an unlimited data option. It is an availability objective, not a guarantee that every device or test route must return 50/10. Read the CRTC explanation ↗.
AI Speed measures the path between your browser and this site’s hosted endpoint at one moment. It cannot identify a fault within your provider’s network, certify your access line’s maximum speed, predict a game server’s latency, or produce a representative city or ISP average from your one result. The IP location lookup started with a test, or requested manually, estimates location and ownership of an IP range; it is not a precise address.
To shop, confirm service at the complete civic address and unit number. Use the provider comparison and regional directory as research starting points, then obtain a current written offer.
Measurement Lab explains that test results depend on the client, server, network path and measurement method. The CRTC separates service availability objectives from an individual test result and directs readers to consider performance and reliability evidence. This guide applies those principles to a repeatable troubleshooting sequence; it does not publish unverified provider benchmarks or diagnose a provider fault.
Use the home connection test worksheet to compare Ethernet and Wi-Fi with the same device, then prepare useful support evidence.