English
LibreSpeed Hosting
Run your own no-Flash speed test to measure connection performance from any browser.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Tech
- Docker image
- lscr.io/linuxserver/librespeed:latest
- Default port
- 80
How LibreSpeed works
LibreSpeed generates transfers between a visitor’s browser and the hosted service, then reports download speed, upload speed, ping, and jitter. The test runs with browser technologies rather than a plug-in or installed client. Its configuration can adjust the interface and measurement behaviour, while the result reflects the path to this particular server at the time of the test.
The LinuxServer package in the catalogue also exposes a results page protected by generated credentials and persists its configuration directory. The public speed-test page itself does not use that results-page password. Visitors who know the application address can initiate tests, and optional result collection should be reviewed before the page is shared broadly.
Key LibreSpeed features
A self-hosted endpoint helps teams compare routes to a chosen region or repeat a diagnostic after changing Wi-Fi, routing, or firewall settings. Browser, device, VPN, local-network, distance, peering, congestion, and server-plan conditions can all change the result. Measurements from different endpoints are therefore not directly interchangeable.
LibreSpeed is not continuous monitoring, a packet-capture tool, an internet-provider certification service, or a complete history and alerting platform. The hosted application does not add user quotas, private invitation controls, provider-grade test-node validation, or a promise that public tests will not consume the plan’s network allocation.
LibreSpeed vs Speedtest by Ookla
LibreSpeed gives the operator control over the web interface and destination server for browser-based throughput, ping, and jitter tests. Speedtest by Ookla combines official applications with a wide provider-operated test network and a familiar public measurement experience across many regions and access technologies.
Speedtest by Ookla may suit consumer comparisons and workflows that rely on its established network. LibreSpeed is useful when an organisation wants repeatable tests to one known endpoint and accepts responsibility for bandwidth, access, configuration, interpretation, and any collected result data.
Who uses LibreSpeed
Support desks use LibreSpeed as one step in diagnosing a remote user’s route to a hosted region. Offices compare wired and wireless networks, labs examine changes between segments, and administrators repeat tests before and after network maintenance using the same browser and destination.
A single low number does not identify the fault domain. Teams should combine results with route information, device checks, wireless diagnostics, provider data, and application monitoring before deciding whether the client, local network, transit path, or hosted endpoint caused a limitation.
Self-hosting LibreSpeed: requirements and cost
Active tests drive network transfer, browser connections, and processing, while optional stored results and application configuration use the persistent package directory. The catalogue marks PostgreSQL and MariaDB as Not required because no relational database container is provisioned. Concurrency and transferred data matter more than application memory for public use.
On AvaHost, LibreSpeed uses Plan 1 at €2. The hosted LibreSpeed package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. The test page is publicly reachable through its domain, while the generated password protects the separate results view rather than the testing endpoint. AvaHost does not add visitor accounts, per-user quotas, provider certification, or continuous network monitoring. Decide whether result collection is appropriate and account for bandwidth before sharing the URL widely.
F.A.Q
LibreSpeed starts at €2 on Plan 1. Occasional tests by a small group fit the entry plan. Simultaneous visitors, repeated upload and download runs, optional stored results, and public sharing can increase network and processing use. Monitor the endpoint and move to a larger allocation if sustained test traffic develops.
The catalogue credentials protect the separate results page, not the public speed-test interface. Anyone who can reach the application domain may be able to start a test and consume plan bandwidth. Share the address intentionally, review whether stored results are enabled, and do not describe the generated password as full application access control.
A custom hostname can be connected with automated HTTPS for browser traffic. The branded address does not change what the measurement represents: it is still the route between the visitor and this hosted endpoint. Keep the URL controlled when public testing is unnecessary, because repeated tests can use network capacity even without access to the protected results page.
LibreSpeed reports performance to the selected server under current browser and network conditions. Wi-Fi, device load, VPNs, routing, distance, peering, congestion, and hosted capacity can affect the result. Use repeated controlled measurements as supporting evidence, not as the sole basis for attributing a problem or verifying every destination on the internet.