Internet Quality – HTTP Connection Check

Start a bounded connection check to the fixed Vitali endpoint. Inspect successful probes, partial errors and timing variation before repeating.

Network access after your requestFree · No account needed

Your connection to Vitali Web Tools
Check how consistently this website responds. This is not a speed test: the browser, connection, hosting and protective checks all affect the measured time.

Allow up to 60 seconds and keep this tab visible. No large upload or download is performed.

Conditions for this run (optional; kept locally)

Starting sends small requests to Vitali Web Tools. Its hosting service receives the connection data needed to answer them. Your notes and results stay in this page.

Start these requests deliberately. I understand this checks the path to one endpoint and is not a speed test or a diagnosis of my provider.

Measurement method and data limits

Target: https://vitaliwebtools.com/api/internet-quality. Shared limits: 180 requests per minute and 3,000 per UTC day; each repeat counts. Busy or unavailable service responses do not prove a connection problem.

A deliberate start sends one start request, two warm-up probes and twenty measured probes to this website. One request at a time, 250 ms pause after each completed probe; up to two seconds per request and sixty seconds per run. Warm-ups are excluded from the statistics but do not guarantee a warmed connection.

Under 20 KiB application request/response bodies per run; HTTP headers, transport and platform overhead are additional. No large upload or download. Notes stay in this page and are not sent to the endpoint. No account required.

Preparing your tool…

A visual example

What this check actually measures

A response time belongs to a particular request and route.

Your browser
Vitali Web Tools
HTTP request + response
Browser to this website
The test requests a small response from Vitali Web Tools, including its hosting and protective checks.
Request 1
40 ms
Request 2
44 ms
Request 3
160 ms
Compare response times
In this example, the third successful request takes longer. That alone does not identify the cause.

Read the timings and failed requests separately; a timeout is not proof of IP packet loss.

Illustrative example. Illustrative values, not a live test. No download-speed, Wi-Fi or Internet-provider diagnosis.

How to use it

Read which path is measured and deliberately confirm the requests; opening the page starts no measurement.
Start the bounded HTTP check to Vitali Web Tools. Only fully read, verified responses contribute a time value.
Review successful and failed requests, median, P90 and the stated variation measure.
Repeat under comparable conditions and inspect the optional report before downloading it.

A timeout is a failed HTTP request, not proof of a lost IP packet. A slow response can also result from hosting or protective quota checks.

Details & limits

One start, two warm-ups and twenty probes; 250 ms pause, two seconds per request and sixty seconds per run. Under 20 KiB application bodies, excluding headers and transport. Times include hosting and protective quota checks. No speed test, IP packet-loss, Wi-Fi, router or provider diagnosis. Shared request limits apply.

Does this identify a problem with my Internet provider?

No. It measures the browser-to-Vitali-Web-Tools HTTP path, including browser, server-location, hosting and quota-check influences. It compares verified round trips, not Wi-Fi signal, speed, IP packet loss or the cause of a difference. Shared limits can make the service temporarily unavailable.

Browser to this website

Compare response times

How to use it

Details & limits

What this check measures

Related tools