Speedtest vs Fast.com vs VelociBar: Which Test to Use
Use Speedtest or Fast.com for a quick connection check, and VelociBar when you want scheduled tests with local history on a Mac. Both web tools can report more than download speed. Differences between their results can reflect the server, route, workload, or timing; they do not by themselves prove ISP throttling.
How Ookla's Speedtest works
Speedtest looks through thousands of servers spread across the world and picks one that's close to you and very well connected, usually hosted on carrier infrastructure or in a datacenter with plenty of bandwidth to spare. It then opens several parallel connections against that server and adds up their combined throughput.
A throughput test estimates how much data the connection to its selected server can carry during the run. That is useful for checking a plan’s performance, provided you account for the device, connection type, and other traffic.
No single test server represents every application. Real applications can also use CDNs and multiple connections, so it is misleading to label one tool “theoretical” and another “real.” Compare equivalent conditions, and use a second destination when investigating a discrepancy.
How Fast.com works
Fast.com estimates current connection speed using transfers to Netflix servers. Its own FAQ describes a general speed estimate, not a conclusive test of deliberate traffic throttling.
Its main view emphasizes download speed. “Show more info” also displays upload speed and unloaded and loaded latency. The settings allow you to adjust test duration and parallel connections.
What Speedtest and Fast.com have in common
Beyond their differences, both share a structural limitation: they're a snapshot of one moment, taken right when you, deliberately, decide to look. And that detail matters more than it seems.
Results can differ because of server selection, routing, background traffic, device limits, and timing. To investigate a repeatable gap, keep the setup stable and alternate tools across several time windows. A discrepancy alone is not evidence that a provider recognizes or favors test traffic.
Comparison: Speedtest, Fast.com, and VelociBar
| Feature | Speedtest | Fast.com | VelociBar |
|---|---|---|---|
| Measurements | Download, upload, and latency; details depend on client | Download, upload, unloaded and loaded latency | Download and responsiveness; method depends on engine |
| Destinations | Speedtest server network | Netflix servers | Apple networkQuality and a CDN download |
| Best use | A connection check against a selected server | A quick browser test using Netflix infrastructure | Scheduled measurements and local history on a Mac |
| History | Available in apps; behavior depends on client | Record results yourself | Automatic local history, every 15/30/60 minutes while running |
| Sharing | Result sharing; export options depend on client | Record or capture the result | Local CSV with timestamps, source, results, and error flags |
| Limits | A single run covers one moment | A single run covers one moment | Periodic samples; neither engine represents every destination |
What a single test cannot tell you
A single run cannot tell you whether a connection is slower at 9 p.m. than at 9 a.m. Repeating and recording tests can answer that question, whether you collect them manually, automate a suitable tool, or use an app with built-in scheduling.
Those questions don't get answered by a one-off test, no matter how good the test is. They get answered by continuous monitoring: automatic, repeated measurements that draw a curve, not a point. That's exactly why VelociBar exists: a macOS menu bar app that runs an automatic test every 15, 30, or 60 minutes, measures both download speed and responsiveness under load (RPM), and keeps the entire history locally, exportable to CSV.
Use a spot check before an important call and a history to investigate recurring trouble. Ookla’s app listing includes test history and sharing; the available workflow depends on the client. VelociBar combines scheduled tests and local CSV export on macOS. See how to test on a Mac and how to document slowdowns for support.
VelociBar runs active tests while the app is running and the Mac is awake. Tests transfer data and may affect calls or downloads. Compare results from the same engine; missing or failed tests are not valid zero-speed samples.
Sources
A one-off test can't show you the full pattern
VelociBar measures your connection automatically from the macOS menu bar and keeps the full history on your Mac. No accounts, no cloud.
Download VelociBar