Internet Speed Test

Internet Speed Test is a browser-based network diagnostic tool for checking whether your internet, Wi-Fi, VPN, or current browser route feels slow, unstable, or down. It measures download speed, upload speed, latency, and jitter with safe cache-busted requests from the browser and a same-origin upload endpoint for generated synthetic bytes.

1. Open the tool and click Start Test. 2. Keep the default Balanced mode for a quick everyday check, or switch to Quick or Thorough. 3. Choose Mbps, Kbps, or MB/s, and pick single-connection or multi-connection download sampling. 4. Disable download, upload, latency, or jitter when you only need one signal. 5. Review result details, server status, latency phases, diagnostics, and quality hints. 6. Copy plain text, copy Markdown, download JSON, restart the test, or clear local history.

Download speed estimates how quickly this browser can receive data and is shown in Mbps. Upload speed estimates outbound transfer speed when a safe upload endpoint exists. Latency is the request round-trip delay in milliseconds. Jitter is the variation between latency samples, which matters for video calls, voice calls, gaming, remote desktops, and other real-time work.

Use this tool when Wi-Fi feels slow, video calls lag, file uploads stall, online games feel delayed, CI dashboards stop loading, or you want a quick network snapshot before reporting a bug. Developers can also use it to separate app performance problems from local network instability.

Excellent means download is at least 50 Mbps with latency below 50 ms. Good means download is at least 20 Mbps with latency below 80 ms. Fair means download is at least 5 Mbps. Poor is reported for very slow download or latency above 150 ms. Unstable is reported when jitter is above 30 ms because real-time traffic may fluctuate.

The tool reports the current test provider, same-origin server label, upload endpoint status, endpoint health, environment, and download resource strategy so you can tell whether the browser route to CodingTool.dev is healthy. Single connection runs one download stream per sample. Multi connection runs a small number of parallel download streams per sample to better expose available throughput, but it does not claim to match proprietary speed-test networks or server selection.

This is an approximate browser-based route test, not a full public internet benchmark like Speedtest.net or Fast.com. Those services can select nearby measurement servers and use their own network infrastructure, while this tool measures same-origin CodingTool.dev endpoints through normal browser fetch APIs. Browser cache behavior, request scheduling, tab throttling, power-saving modes, device load, VPNs, proxies, CDN routing, local Wi-Fi congestion, and ISP routing can all affect the result. In localhost or development environments, the test is labeled as local development because it measures browser-to-local-server behavior rather than real public internet speed. Reruns can vary because network routes, Wi-Fi contention, CDN edge choice, and background device activity change over time.

Idle latency comes from lightweight request samples before sustained transfer. Download-phase latency and upload-phase latency use the elapsed transfer timing as an approximate phase signal when those metrics are measured. The latest results are stored locally in your browser only, making it easier to compare quick reruns without creating an account or sending history to a server.

No manual input is required, no user files are uploaded, and the default tests use same-origin browser requests with cache-busting. The upload test sends only generated disposable bytes to a CodingTool.dev API route, discards the body, and stores nothing.

Browser-based measurements are approximate. Same-origin tests estimate the route to CodingTool.dev, not every website, every ISP route, or every speed-test provider. Browser APIs do not expose full network-layer throughput details, and upload speed is not faked if the endpoint times out or fails. Use the reliability badge, environment label, endpoint health, diagnostics, and exported reliability metadata to decide whether a result is suitable for a quick troubleshooting note or should be verified with a dedicated benchmark.