Resource
Speed test by ISP, device, or city
A raw Mbps result only answers part of the question. Use provider footprint data, the device you tested on, and the local environment to decide whether the next move is upgrading service, fixing Wi-Fi, changing hardware, or documenting an ISP support case.
ISP entry points from FCC state data
These provider summaries reuse SwiftSpeedTest's state guide dataset. Coverage is reported statewide residential footprint, not a promise that an exact address can order that service.
T-Mobile 5G Home
Appears in 49 state guides.
63.6%
avg.
AT&T
Appears in 37 state guides.
54.7%
avg.
Verizon
Appears in 20 state guides.
42.7%
avg.
Quantum Fiber or CenturyLink
Appears in 14 state guides.
59.6%
avg.
Telephone and Data Systems
Appears in 8 state guides.
56.9%
avg.
Fidium Fiber
Appears in 3 state guides.
67.4%
avg.
State-level starting points
Start with a state guide when your question is whether the local provider mix can realistically outperform your current result.
Device lens
- Run one test on the exact device that feels slow, then repeat on a newer phone or laptop nearby.
- Use Ethernet or a USB-C Ethernet adapter for one comparison when the device supports it.
- If only one device is weak, check Wi-Fi adapter limits, VPN software, power saver mode, and background sync.
City and neighborhood lens
- Run a quiet-hour test and a busy-evening test to expose local congestion patterns.
- Apartments and dense city blocks need Wi-Fi channel cleanup more often than single-family homes.
- Rural and edge-of-network locations should compare terrestrial options against fixed wireless or satellite fallbacks.