Network tool
Internet speed test
Measure approximate round-trip latency, jitter, download speed, and upload speed from your browser. Aegis runs the test against the endpoints configured for the deployment.
The published static configuration is disabled until a real test server is supplied. Results are directional browser measurements, not lab-grade network certification.
How the speed test works
- Confirm configuration. A deployment needs latency, download, and upload endpoints before the test can run.
- Start a run. The browser sends the configured requests and measures their observed timing and transfer rate.
- Review the summary. Inspect ping, jitter, download, upload, and the short local run history.
Speed test measurements
- Latency from repeated ping requests.
- Jitter derived from latency variation.
- Download throughput from uncached byte responses.
- Upload throughput from a configured upload sink.
- Local history and CSV export for recent runs.
Internet speed FAQ
Common questions
Why is the speed test unavailable?
The test is disabled until speed-test-config.json points to working latency, download, and upload endpoints with appropriate CORS and cache behavior.
What does jitter measure?
Jitter describes variation in observed latency between repeated requests. It can help indicate an inconsistent connection, but it depends on the test path and current network conditions.
Are speed-test results exact?
No. Browser scheduling, Wi-Fi conditions, other traffic, server location, and the configured sample sizes all affect the result. Treat it as directional.
Does starting a test use network data?
Yes. The speed test intentionally sends latency, download, and upload requests to the configured endpoints when you start it.