Website Response Time Checker

Why response time decides whether an enquiry becomes a customer

Most websites are judged on how fast they load. That matters, but it is not the number that decides whether a visitor becomes a customer. The number that decides it is how long they wait between asking a question and getting an answer — and on most small business websites, that wait is measured in hours, because the only way to ask is a contact form that lands in an inbox nobody is watching at 9pm.

The gap is easy to miss because it never shows up in analytics. A visitor who fills in a form and waits until morning looks identical to one who was answered instantly. A visitor who wanted to ask something, found only a form, and left is invisible entirely — no bounce reason, no event, nothing. The enquiries you lose this way are the ones you never learn about.

What a good result looks like

Server response time is the part with a published benchmark. Google's guidance for Time to First Byte is to stay under 800 milliseconds, with anything over 1.8 seconds treated as poor. TTFB is not itself a Core Web Vital, but it is an upstream cause of a bad Largest Contentful Paint — every millisecond the server spends thinking is a millisecond before rendering can even start.

Contactability has no official benchmark, so this tool grades it against a simple, stated standard: how quickly could a visitor get an answer with what is on this page. A page with live chat can answer in seconds. A page with a visible phone number can answer in a minute, during opening hours. A page with only a contact form cannot answer at all until a human reads it. A page with none of these cannot be contacted without leaving the site.

• A — an answer in seconds is possible, and there is a fallback channel
• B — instant answers with no fallback, or a real-time channel plus a way to leave a message
• C — one route only: a phone number in office hours, or a message and a wait
• D — any of the above, on a server too slow for the channel to help
• F — no contact channel on the page at all

How to improve the result

If server response time is the weak half, the usual causes are shared hosting, an uncached database query on every request, or a redirect chain in front of the page. Serving cached HTML from a CDN edge fixes most of it, and removing a single unnecessary redirect hop often removes 100-300 milliseconds on its own.

If contactability is the weak half, the fix is to add a channel that can answer without a person being available. Put the phone number in the header rather than only in the footer. Make sure it is a tel: link so it is tappable on a phone. Then add something that answers outside office hours — that is the whole reason an AI agent on a website is worth having: it turns the overnight enquiries that currently go unanswered into conversations that get a reply within seconds.