Independent browser diagnostic
Starlink internet speed test
Track Starlink with stable dish and router conditions, obstruction-aware app checks, and repeated latency evidence.
Independent, not provider-operated: SwiftSpeedTest is not affiliated with Starlink. This browser result does not isolate the Starlink access line or replace an official gateway, router, dish, app, account, or outage diagnostic.
Test Your Internet Speed
Measure your connection's download speed, upload speed, and latency
Optional context is saved with recent results and included only if you copy a share link.
Low-data measurement
Active because the browser cannot report connection quality. The time- and byte-bounded run requests at most about 52 MiB of test payload, and usually less. Protocol overhead may add a little more.
Test endpoint
Default Server - Nearest Location
Same-origin hosted endpoint
Endpoint readiness unavailable
Default endpoint is ready.
For the most accurate results, close other apps and devices using your network
What it measures
Device-to-SwiftSpeedTest endpoint download, upload, idle and loaded latency, jitter, p95 tail delay, and browser HTTP request confidence.
What it includes
The browser, test device, Ethernet or Wi-Fi, household traffic, Starlink path, internet route, and selected endpoint all influence the result.
What it cannot prove
One run cannot prove an outage, throttling, plan compliance, address availability, or whether the fault sits inside or outside the home.
Low-Earth-orbit satellite option
How to interpret your Starlink result
Pair Starlink app diagnostics with repeated independent browser tests. The app can separate router-to-internet and device-to-router paths; SwiftSpeedTest adds another device-to-endpoint route, loaded responsiveness, and private time-window history.
Dish obstructions, installation, and the current satellite path can affect performance.
Network demand and satellite availability can make consecutive runs differ.
Device-to-router Wi-Fi quality can be a separate bottleneck from the satellite link.
Weather and route conditions can coincide with changes but one result cannot prove causation.
Controlled comparison
Four checks for a cleaner Starlink diagnosis
- 1
Review obstruction and installation status in the Starlink app before testing.
- 2
Keep dish, router, device, and test location unchanged during comparisons.
- 3
Use the app's router and device scopes, then run the independent browser test.
- 4
Save repeated quiet- and busy-period runs, including latency and jitter, before inferring a pattern.
FCC-derived context
State profile entries for Starlink: 50 of 50
These entries reuse provider-reported fixed broadband availability as of December 31, 2025. A footprint can overlap other providers and is not market share, measured performance, or a promise that Starlink serves an exact address.
Provider-owned references
Compare the official diagnostic scope
Use Starlink's own resources for account, gateway, router, dish, app, outage, or network-specific checks. A difference between methods is a reason to inspect scope and conditions, not proof that either result is false.
Frequently asked questions
Starlink speed-test questions
- Is this Starlink speed test operated by Starlink?
- No. SwiftSpeedTest is independent and is not sponsored by, endorsed by, or affiliated with Starlink. The page pre-fills Starlink as test context and links to provider-operated resources for a complementary official diagnostic.
- What does this Starlink internet speed test measure?
- It measures browser download and upload throughput, idle latency and jitter, loaded latency and jitter, p95 tail delay, and browser HTTP request confidence to a selected SwiftSpeedTest endpoint. The result includes the device, local network, ISP path, and internet route.
- Why can this result differ from Starlink's own speed test?
- Starlink says its default app test measures router-to-internet performance and its advanced test can isolate device-to-router and device-to-internet paths. SwiftSpeedTest does not access dish telemetry; it contributes an independent device-to-hosted-endpoint measurement.
- Why does the Starlink app show more than one speed-test scope?
- Starlink documents router-to-internet, device-to-router, and device-to-internet views. Separating those paths helps distinguish local Wi-Fi from the satellite and internet route.
- Can one Starlink result prove an outage or throttling?
- No. One browser run cannot establish outage status, throttling, service compliance, or the exact fault domain. Compare repeated same-condition tests, provider equipment diagnostics, status information, and support evidence before attributing a cause.
- How should I document a recurring Starlink speed problem?
- Save several full-confidence runs with the provider, connection type, location, endpoint, and time window recorded. Compare Ethernet with Wi-Fi, use the private history median and spread, and then compare eligible runs with the advertised and Broadband Consumer Label values in the plan-audit tool.
- Does the 50-state figure mean Starlink serves my address?
- No. It only counts appearances in SwiftSpeedTest's 50 FCC-derived state profiles. Provider-reported footprints can overlap and do not establish market share or exact address eligibility. Verify the technology and service directly with the provider.