How to Check How Fast a List of Company Websites Responds

To check how fast a list of websites responds, request each home page once and time it. The bulk website response time checker does that for up to 100 sites (500 after a free Google sign-in) and labels each one Fast, Moderate or Slow, with the exact time, the status and the number of redirects.

It reads the server's answer. It does not render the page, so it is not a full speed test.

The by-hand way

Time one request with curl. curl -o /dev/null -s -w "%{time_total}\n" https://example.com prints the total time in seconds. For another site, change the URL. Add -L to follow redirects, as a browser would.

That works for a handful of sites. For a list of company domains it means a loop, a decision about http versus https, and a spreadsheet of results. Reading the same figure in a browser's network panel is accurate for one visit and slow for many.

Step 1: paste the websites

Paste one site or a list, one per line. Emails and URLs work too, and the domain is taken from each. You can also upload a CSV. No account is needed for up to 100 sites a run; sign in with Google for up to 500.

Step 2: run the check

Each home page is requested once, over HTTPS and then plain HTTP if HTTPS does not answer, five sites at a time. The clock runs from our request to the last byte read, up to 128 KB of the page.

Step 3: read the result as a signal

Result	What it means	What to do
Fast (under 1 s)	The server answered quickly	Nothing to flag
Moderate (1 to 3 s)	Acceptable, not quick	Usually nothing
Slow (over 3 s)	The first response took a while	Run it again to confirm

The time includes DNS, the TLS handshake and every redirect, so a site that goes http to https to www takes longer than one that answers directly. If HTTPS failed and HTTP answered, the failed attempt is counted too. The CSV carries the domain, the result, the time, the evidence, the final URL and the HTTP status.

Why a company's site might be slow

• Cheap shared hosting or an overloaded server.
• A heavy page builder or an unoptimised image on the home page.
• Several redirects before the real page.
• An unpaid hosting account, which sometimes shows as very slow answers or none at all.

For background on what the first byte measures, see MDN on Time to First Byte and web.dev on TTFB. To see the redirects and headers behind a row, read checking the HTTP headers of a website.

Using it on a lead list

A slow row is a talking point if you sell web or hosting services, and a caution if you are cleaning a list. A site that is slow or silent often belongs to a company that has stopped maintaining it. For the live-or-down read of every site, see how to check if a list of websites is online and the broader lead list quality check.

What this check cannot do

• One request per site, so a reading is a signal, not a benchmark.
• The time is measured from our server, not from your visitors.
• The page is not rendered; only the server's answer is timed.
• The limit is 100 sites a run without an account and 500 signed in.

If the company is still alive, check the contact emails

A site that answers does not mean a given mailbox exists. Once you know which companies are still around, check the addresses on your list on the verify page: the first 100 email checks are free with a Google sign-in, no card. Each comes back valid, risky or invalid with a reason, and nothing is sent to anyone on the list. To confirm every site still answers first, run the list through the bulk website status checker. For larger or recurring lists, see bulk email verification, list cleaning and pricing.

Time your list now

Paste your sites into the bulk website response time checker.