English
OpenSpeedTest Hosting
Test download, upload, and latency in the browser with a clean, self-hosted speed test.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Tech
- Docker image
- openspeedtest/latest:latest
- Default port
- 3000
How OpenSpeedTest works
OpenSpeedTest transfers generated data between a browser and the hosted web service, then calculates download throughput, upload throughput, latency, and jitter. It uses browser networking capabilities rather than requiring a plug-in or installed test client. The result describes the connection between that browser and this particular the hosting service endpoint at that moment.
The test does not measure every segment of a user’s internet service or establish a universal line speed. Browser behaviour, Wi-Fi, device load, VPNs, routing, distance, congestion, proxy limits, and the hosted plan can influence a result. Repeated tests from the same controlled devices and locations are more useful than comparing unrelated measurements from different environments.
Key OpenSpeedTest features
Because the endpoint is public through its application domain, visitors can initiate transfers that consume network and processing capacity. The hosted package does not add user accounts, quotas, a private invite system, a historical results database, provider-grade test-node certification, or a promise that public traffic will be isolated from the plan’s resource limits.
OpenSpeedTest is useful for comparing local-network paths, validating office connectivity to a hosted region, or checking changes after router and Wi-Fi work. It should not be used as the only evidence in a dispute with an internet provider, because the selected endpoint, route, browser, and server allocation differ from standardised provider testing networks.
OpenSpeedTest vs Speedtest by Ookla
OpenSpeedTest gives an organisation control over the test endpoint and presents browser-based throughput, latency, and jitter for that route. Speedtest by Ookla operates a broad global measurement network, supplies official consumer applications, and aggregates internet-performance data across participating servers and providers.
Speedtest by Ookla may be better for familiar consumer testing, comparisons across its network, and provider-recognised workflows. OpenSpeedTest is more useful when a team wants a repeatable test against its own chosen location, understands the endpoint limits, and can interpret differences caused by routing and hosted capacity.
Who uses OpenSpeedTest
IT teams publish OpenSpeedTest to compare branch-office routes, remote-user connectivity, or changes after a network upgrade. Labs can test browser performance across VLANs, and support staff can ask a user to run a measurement against one controlled regional endpoint while discussing a connection problem.
The tool does not identify the root cause of packet loss, perform continuous monitoring, trace routes, replace wireless diagnostics, or certify contracted bandwidth. A low result starts an investigation; it does not by itself prove whether the client, local network, provider, route, browser, or hosted server caused the limitation.
Self-hosting OpenSpeedTest: requirements and cost
Resource use is driven by active tests, selected payload behaviour, simultaneous visitors, browser connections, and transferred data. PostgreSQL and MariaDB are Not required because this package serves the test interface without a relational results service. Network throughput and concurrency are more important than persistent storage for ordinary operation.
On AvaHost, OpenSpeedTest uses Plan 1 at €2. The hosted OpenSpeedTest package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. The public address measures the path to this AvaHost application, not a provider-wide or global internet benchmark. No user authentication, test quota, historical result store, external monitoring, or certification is included. Restrict how broadly the URL is shared and account for bandwidth use when several visitors may run tests at once.
F.A.Q
OpenSpeedTest starts at €2 on Plan 1. A small number of occasional tests fits the entry allocation. Simultaneous visitors and repeated download or upload runs can consume more processing and network capacity, so organisations that publish the URL broadly should monitor usage and upgrade when the endpoint becomes persistently busy.
It measures the browser’s route to the hosted OpenSpeedTest endpoint. Device performance, Wi-Fi, VPNs, routing, distance, congestion, browser limits, and server allocation can affect the number. Use repeated controlled tests as one diagnostic signal rather than treating a single result as a universal measurement of every path your connection can reach.
A custom domain can be attached with automated HTTPS, giving staff or customers a memorable testing address. The page remains a public transfer endpoint unless access is controlled elsewhere, so anyone who knows the URL may run tests and use plan bandwidth. Share it deliberately and avoid presenting the hostname as proof of provider certification.
The catalogue does not declare a relational results database or user account service for OpenSpeedTest. The package provides the browser test interface, while AvaHost applies application updates and scheduled backups to the hosted installation. Record important measurements in your own monitoring or ticket system when trend analysis or audit history is required.