Check your true internet speed in seconds.

The test measures download throughput, upload throughput, latency (ping), and jitter. Download is calculated by fetching progressively larger payloads from a nearby server and dividing the bytes transferred by the time taken. Upload works the same way in reverse. Latency is sampled separately with lightweight requests before either throughput stage runs. All four values reflect the connection between your device and the test server.

It runs client-side in your browser. The test code executes on your device and measures the connection between your device and a nearby test server. Pingie's own servers are not in the measurement path. This is the key difference between this tool and most other tools on the site, which send probes from Pingie's infrastructure to a target you specify.

Several layers sit between your plan's advertised speed and what the browser measures. Wi-Fi introduces radio interference, signal attenuation, and channel congestion. Background applications consume bandwidth during the test. Your network adapter or CPU may become a bottleneck before the connection does. ISP plans also describe maximum speeds under ideal conditions. Plugging in via ethernet and closing background apps before retesting helps isolate which layer is limiting your throughput.

Jitter is the variation in latency between successive measurements. If your ping averages 20 ms but swings between 5 ms and 80 ms, your jitter is high. High jitter causes audio dropouts in voice calls, stuttering in video conferencing, and inconsistent performance in online gaming, even when average latency looks acceptable. A stable connection produces low jitter; a congested or noisy wireless link tends to produce high jitter.

The speed test measures throughput (how much data your connection can move per second) and latency together, running from your browser to a nearby test server. The ping tool sends lightweight ICMP-style requests from Pingie's servers to a host you specify, and reports only round-trip time and packet loss. Use the speed test to evaluate your own connection capacity. Use the ping tool to check whether a specific external host is reachable and how long it takes to respond.

Browser-based tests are reliable estimates for most consumer connections. On very fast connections (above roughly 500 Mbps), the browser's own CPU and memory overhead can become a ceiling that caps what the test can observe. Dedicated native applications bypass browser overhead and can report higher peak throughput on gigabit or multi-gigabit links. For typical broadband plans up to a few hundred Mbps, the browser-based result is a practical and accurate enough measure for troubleshooting and verification purposes.

No results are stored after your session ends. The test runs in your browser and the measurements are displayed to you only. Pingie does not log your speed results or associate them with your IP address beyond what is standard in any web server access log. You can review the full privacy policy at pingie.net/en/privacy for details on what data the site collects during a visit.

Thresholds depend on use case. Streaming HD video typically requires 5 to 25 Mbps download. Video conferencing at high quality needs roughly 10 Mbps down and 3 Mbps up per stream. A household with multiple simultaneous users benefits from 100 Mbps or more download. Upload matters more for content creators, remote workers sharing large files, or anyone hosting services. Latency below 20 ms is considered low; above 100 ms becomes noticeable in real-time applications.

Network conditions change between runs. Background processes on your device, other devices on your local network, congestion on your ISP's infrastructure, and radio interference on Wi-Fi all vary over time. The test selects a nearby server, but routing paths can shift between runs. Running the test three or four times and averaging the results gives a more representative picture of your connection than any single measurement.

No. This tool measures your own connection, not a remote server's capacity. The test runs between your browser and a designated test server. If you want to check whether a remote host is reachable or how quickly it responds, use the ping tool or the port check tool instead. Those tools send probes from Pingie's servers to a target you specify, which is a different measurement entirely.

Yes. A VPN routes your traffic through an additional server and encrypts it, both of which add overhead and latency. The test will measure the throughput of your VPN tunnel rather than your raw ISP connection. If you want to check your baseline ISP speed, disconnect the VPN before running the test. If you want to measure what your connection delivers through the VPN, run it with the VPN active.

Start by isolating the problem layer. Connect via ethernet and close all background applications, then retest. If wired speeds match your plan but wireless speeds do not, the issue is in your local Wi-Fi setup. If wired speeds are also low, restart your modem and router and retest. If the problem persists on a wired connection after a restart, contact your ISP with the test results as documentation. Consistent low speeds at the same time of day often indicate ISP network congestion.