NETWORK SPEED TESTER
Measurement methodology and public beta limits
How Network Speed Tester counts bytes, samples latency and labels synthetic workload evidence and unavailable hardware measurements.
How measurements are collected
The browser initiates a bounded session with our managed test endpoint. Download bytes are counted from received data; uploaded bytes require server acknowledgement. Idle and directional loaded HTTP RTT samples remain separate. Valid sustained throughput requires enough verified observations and sufficient steady-window time.
Validity before a headline number
A short observation window, data cap, errors, insufficient probes or local scheduling interference can make a metric inconclusive. The interface displays limitations instead of filling in invented values. Endpoint HTTP 429 responses represent admission or quota controls, not proof of network packet loss. Recovery RTT remains unfinished.
Synthetic application profiles
Eight profiles exercise gaming, cloud gaming, streaming, conferencing, market-style feeds, AI-style streams, outbound hosting and resumable synthetic backups. They reproduce selected traffic mechanics, not third-party service execution or certification. Conferencing uses two synthetic browser peers with relay-only ICE. Both directions must select external relay candidates and deliver RTP packets and decoded frames across three stages. Relay round-trip evidence is not an independently located remote caller or conferencing-provider certification.
What is not measured
The public beta does not independently inspect Wi-Fi radios, mesh backhaul, router resources, physical ISP access nodes or OS utilisation. Authorised companion and controller integrations remain unfinished. Measurements are not yet independently calibrated over the full reference-link and browser/hardware matrix.
Fair use and availability
Tests require deliberate user action and have byte, duration, session, request and socket limits. Production sessions are admitted independently: there is no shared two-session limit or sitewide daily byte reservation. Per-test expiry, user-selected byte allowances and abuse protections remain. Platform resources and the connection itself still bound achievable concurrency. No measurements start merely because a crawler or visitor loads a page.