Controlled mobile test
Test one carrier condition at a time
- 1. Turn Wi-Fi off and confirm cellular data is active.
- 2. Stop moving; note the room or outdoor location.
- 3. Pause app updates, cloud sync, and hotspot clients.
- 4. Run three tests without moving or changing settings.
- 5. Keep each result; summarize with the median and observed range.
Evidence labels
Do not mix four different kinds of numbers
- Vendor minimum
- A first-party app or service requirement for a defined mode. It is not a mobile-network guarantee.
- FCC household benchmark
- The FCC's 100/20 Mbps fixed-broadband benchmark is household-level policy context, not a minimum for a phone, LTE, or 5G. Read the FCC report.
- Editorial planning target
- A conservative workload-planning value from SwiftSpeedTest dataset 2026.07.24; it is not a promise that every app succeeds at that boundary.
- Measured diagnostic
- A snapshot of one browser-to-endpoint path. Repeated variation is evidence about the tested path, not a universal carrier grade.
Versioned planning data
Compare mobile results with the activity, not the network icon
These values come directly from dataset 2026.07.24, updated 2026-07-24. They are per-activity editorial planning baselines; the interactive calculator adds household headroom after combining simultaneous sessions.
| Activity | Download plan | Upload plan | Ping ceiling | Jitter ceiling |
|---|---|---|---|---|
| Web browsing and email | 5 Mbps | 1 Mbps | 150 ms | 40 ms |
| HD video stream | 8 Mbps | 1 Mbps | 100 ms | 30 ms |
| HD video call | 4 Mbps | 4 Mbps | 100 ms | 30 ms |
| Online gaming | 10 Mbps | 3 Mbps | 50 ms | 15 ms |
Diagnose, do not grade
What repeated mobile results can tell you
- Same spot, wide spread: investigate tower load, radio changes, plan priority, device temperature, and background traffic.
- Outdoor improves over indoor: the building or indoor radio path is a likely contributor.
- Phone is healthy, hotspot client is not: inspect tethering policy, hotspot Wi-Fi, client radio, and plan terms.
- Metrics meet the planning row but the app fails: inspect the app, endpoint, route, VPN, packet loss, and device; more peak Mbps may not solve it.
Sources and data
Source-checked July 24, 2026. The FCC figure is fixed-household policy context; the SwiftSpeedTest distribution is a versioned editorial planning dataset.