Why We Built This Platform
Many online diagnostic tools have degraded into ad-heavy, slow, and bloated experiences that require user registrations, collect unnecessary telemetry, or rely on fabricated animations rather than executing real measurements.
NetTestLab was architected with a strict set of engineering standards: zero tracking cookies, zero account walls, transparent scientific measurement methodology, and mobile-first performance optimized for Core Web Vitals.
How Our Internet Speed Test Works
Our speed test engine is executed natively inside your web browser using standard Web APIs:
The client dispatches sequential low-overhead HTTP requests to our ping endpoint with cache-busting nonces. High-resolution timestamps from performance.now() calculate the exact round-trip time (RTT). Jitter is computed using the RFC 3550 recursive statistical filter across consecutive RTT intervals.
The client establishes concurrent streaming connections using ReadableStream readers. A warm-up period allows TCP congestion windows to scale naturally without penalizing early sample calculations. Periodic chunk transfers are tracked, and a trimmed-mean calculation eliminates temporary garbage-collection spikes or network anomalies.
The client transmits in-memory binary chunks using HTTP POST to our discard endpoint. Payloads are constructed with non-repeating byte patterns to prevent transparent transport-layer compression from distorting the measured bandwidth.
Known Browser & Network Limitations
In keeping with our commitment to transparency, users should understand inherent factors that influence browser-based network benchmarking:
- Browser JavaScript Overhead: Benchmarking at gigabit speeds (1000+ Mbps) requires substantial CPU power to process millions of network bytes in JavaScript. Browser performance may differ slightly from native CLI socket benchmarks (e.g. iPerf3).
- Proxy & VPN Routing: Running tests behind an active VPN or corporate proxy routes traffic through encrypted tunnels, reflecting the VPN provider's bandwidth rather than your direct ISP line.
- Server Proximity: Results reflect the end-to-end throughput between your device and the active benchmark server endpoint, including all intermediate ISP peering exchanges.
Privacy Commitment
We believe diagnostic tools have no reason to harvest user data. We do not store your speed test results or IP address in an application database. All network benchmark payloads are streamed in-memory and immediately discarded.
Read Our Full Privacy Policy →