1. Purpose of the test
The test estimates the performance available between the user’s browser and a selected SpeedFiber test endpoint at that moment. It is designed for practical diagnosis, not laboratory certification.
2. Download measurement
The browser requests test data and measures the amount received over elapsed time. Multiple requests may be used to make effective use of faster connections. Browser, CPU, memory, Wi-Fi, Ethernet, route and server capacity can limit the result.
3. Upload measurement
The browser sends generated data to the test endpoint and calculates the delivered rate. Background backup, cameras, cloud sync and application traffic can consume upstream capacity during the measurement.
4. Ping and jitter
Ping represents measured round-trip response time to the test endpoint. Jitter represents variation between latency samples. These values describe the selected route, not every destination on the internet.
5. Recommended test method
- Use a capable device and close large transfers.
- Record device, server, time, VPN status and Wi-Fi or Ethernet.
- Run three tests under the same condition and use the middle result as a practical summary.
- Change only one variable, such as cable versus Wi-Fi or room location.
- Repeat during the period when the real problem normally occurs.
6. Important limitations
One test cannot prove the capacity of every route, service or application. Results can differ across test providers because of server location, connection method, duration and algorithm. A provider’s contractual measurement process may use different equipment or rules.
7. Privacy and retention
The service processes technical request data needed to run the test and maintain security. See the Privacy Policy for details.
8. Reporting a measurement problem
Send the exact page, timestamp, device, browser, connection type, test server and observed values through the contact page.