Four different signals
Capacity, delay, variation, and delivery are not interchangeable
- Throughput
- The transfer capacity observed to the selected test endpoint. It affects downloads and concurrent traffic but does not define game-server response time.
- Latency
- Round-trip delay on a specific path. Distance, routing, queueing, endpoint, and local access all contribute.
- Jitter
- Variation between retained latency probes. Timing swings can make movement or voice feel inconsistent even when the central latency result is unchanged.
- Packet or probe loss
- Missing traffic can force recovery or hide state updates. The meaning depends on protocol and method; this site's HTTP probe loss is not a complete network-loss measurement.
How games expose network behavior
Similar symptoms can have different causes
| Observed symptom | Network evidence to inspect | Non-network evidence |
|---|---|---|
| Delayed actions | Game-region latency, route, loaded latency | Display, controller, frame time, server tick behavior |
| Rubber-banding | Jitter, in-game loss, Wi-Fi retries, congestion | Server health or game simulation |
| Stutter | Timing spikes only if game telemetry agrees | CPU, GPU, storage, shader compilation, frame pacing |
Versioned editorial planning
Online gaming row, dataset 2026.07.24
Download
10 Mbps
Upload
3 Mbps
Ping ceiling
50 ms
Jitter ceiling
15 ms
These are editorial gameplay-planning values, updated 2026-07-24. They are not universal guarantees. Game downloads need more throughput, and a title's own region and route conditions remain authoritative for live play. Download the versioned data.
Measurement limits
A browser result cannot certify a game route
- The selected SwiftSpeedTest endpoint may use a different route and region from the game server.
- HTTP application-probe loss is not ICMP loss and does not observe every game packet.
- A short test cannot guarantee future congestion, server health, matchmaking region, or Wi-Fi conditions.
- Use the game's own telemetry and the controlled gaming test before using the optimization workflow.
Versioned data source
Checked July 24, 2026. This page intentionally avoids universal excellent, good, acceptable, poor, and bad latency bands.
https://swiftspeedtest.com/data/internet-speed-requirements/2026.07.24.json