Internet Speed Test

Because a speed test measures a path, not just your line — your device to some server — and every test uses different servers, routes, and methods. Testing to a nearby ISP-hosted server (as some big-name tests do) often shows the rosiest number; testing to a general CDN edge, as here, reflects ordinary real-world routes. Variation of 10–20% between tests is normal and doesn't mean either is broken. For decisions, what matters is consistency: run the same test at different times and compare like with like.

Work the checklist before the phone call: test wired or standing next to the router (Wi-Fi, especially at 2.4GHz through walls, routinely halves throughput and is the number-one culprit); close backup tools and streams that share the line; try another device; test at a non-evening hour (neighborhood congestion is real). If wired tests at off-peak hours still show a large shortfall, that's legitimate ISP-call evidence — screenshot several results with timestamps. Also honest: plans are advertised 'up to,' and a modest gap is contractually normal.

Less than marketing suggests, for most uses: HD streaming ~5 Mbps per screen, 4K ~25, video calls 3–5, competitive gaming under 1 Mbps of bandwidth (latency is what matters there). Bandwidth is per-simultaneous-use: a household of four heavy users is comfortable at 100–200 Mbps; a gigabit plan mostly buys faster large downloads. The chronically underrated number is upload — video calls, cloud backup, and streaming yourself all lean on it, and cable plans often ship 10–20x less upload than download.

Latency is the round-trip time for a packet (the 'ping'); jitter is how much that time varies. They govern everything interactive: gaming, video calls, and page responsiveness feel snappy under ~30ms latency, fine to ~70, and laggy beyond ~100 — regardless of bandwidth. A 300 Mbps connection with 150ms ping makes worse video calls than 30 Mbps at 20ms. High jitter specifically causes the robot-voice moments on calls. If your bandwidth tests fine but things feel laggy, latency and jitter are where to look — and they're mostly a function of route and congestion, not your plan tier.