Utilities tool

Internet Speed Test

Estimate transfer speed to the RizzKit server.

Measure browser-to-server download and upload throughput and HTTP round-trip latency with an explicit, bounded network test.

How to use Internet Speed Test

  1. Review the data allowance and measurement limits before starting.
  2. Press Start test and keep the page visible while latency, download, and upload are measured.
  3. Read the measured estimates, cancel at any time, or retry after the cooldown.

What this tool does

Real transfers

Calculates throughput from transferred binary bytes and elapsed time, never from a browser connection hint.

Bounded run

Each session is limited to 50 MiB of test payload and 30 seconds, with server quotas, cooldowns, and concurrency protection.

Honest failures

Cancelled, timed-out, offline, rate-limited, or insufficient samples are reported without invented results.

Common uses

  • Estimate download and upload throughput on the route to RizzKit.
  • Observe HTTP round-trip latency under your current network conditions.
  • Compare manually initiated runs while accounting for routing and server limitations.

Processing and privacy

Server processing: Starting a test transfers random binary payloads between your browser and the RizzKit hosting server. Payloads and network results are not stored by the tool. Short-lived session and client rate-limit state are kept in memory; infrastructure may process ordinary request metadata.

Browser processing: The browser calculates Mbps from actual bytes and elapsed time, including the upload acknowledgement, and displays the median HTTP round-trip latency. Results are not saved between visits.

Limitations to know

  • This is not a certified benchmark or a guaranteed ISP line-speed measurement.
  • Server load, hosting proxies, routing, Wi-Fi, browser scheduling, and competing traffic can limit results.
  • At most 50 MiB of test payload and 30 seconds per session; protocol overhead is additional. Cooldowns and capacity limits may prevent a run.
  • Very short transfers may produce insufficient samples rather than meaningful speed estimates. Hiding the page or leaving it interrupts the test.

Keep original files where applicable, inspect the result, and do not rely on an automated output without checking that it fits your intended use.

Examples

Understand throughput units

Input: A measured 1,000,000 payload bytes over 1 second

Output: 8 Mbps (megabits per second), not 8 megabytes per second. This is an illustrative calculation, not a test result.

Interrupted test

Input: Start a test, then press Cancel or hide the tab

Output: The run stops and reports the interruption. Retry explicitly after the server cooldown; no replacement speeds are generated.

Compare two routes

Input: Check your public IP, run a test, change your VPN route, refresh the IP lookup, and run again after the cooldown.

Output: Record each observed IP and its download, upload and HTTP latency estimates. A changed exit IP shows a different observed route, not proof that the VPN alone caused a speed change.

Practical tips

  • Avoid other downloads during a test, but remember that Wi-Fi and background traffic still affect results.
  • Keep this tab visible; switching away interrupts the run.
  • For a comparison, note your network and VPN state, check the public IP, then repeat the test under similar conditions. A different IP does not explain speed by itself.
  • Small bounded samples may not be enough to measure very fast links reliably.

Frequently asked questions

Is this my guaranteed ISP speed?

No. This estimates the route between your browser and the RizzKit hosting server. Server load, routing, proxies, Wi-Fi, and browser conditions can limit the measured rate.

How much data does a test use?

The server permits at most 50 MiB of combined test payload per session and a 30-second lifetime. The normal client uses up to 20 MiB in each direction. Network protocol overhead is additional, so avoid testing on a metered connection unless you accept that usage.

Is latency the same as ping?

This is repeated HTTP request/response round-trip timing, including browser and server work. It is not ICMP ping and should not be compared as if it were.

Are network results stored?

The tool does not save test payloads or results. The server temporarily keeps session and rate-limit state, and hosting infrastructure may process ordinary request metadata.

Related tools and guidance