Up or down
Whether the site responded at all, and whether the response was a healthy 2xx/3xx or an error status.
Free Website Response Time Checker
Enter a URL to check whether the site is up right now, what HTTP status it returns, and how long the full response takes — with a fast, moderate, or slow rating.
Start your 7-day trial — no credit card, free plan after.
Check response time
Enter a URL (or domain). NorthDuty requests it once and reports whether it is up and how long it took to respond.
Free check. No signup. Results are not published or indexed.
How NorthDuty website monitoring works
Enter a URL (or domain). NorthDuty requests it once and reports whether it is up and how long it took to respond. Recurring checks are configured inside the NorthDuty app.
What this response time checker reports
A single request tells you if the site is reachable and how quickly it responds.
Response time
How long the full request took — DNS, connection, and response — in milliseconds.
Speed rating
A quick fast / moderate / slow rating so you can tell at a glance if the response is sluggish.
Redirects and server
Whether the URL redirected, plus the reported Server header for quick debugging context.
Why check response time
A slow or failing response costs you conversions before anyone reports it. A quick check confirms the site is both up and responsive.
- Confirm the site is actually reachable
- Spot a slow response before customers feel it
- See the real HTTP status after redirects
- Catch a server that is up but erroring
- Get a baseline before and after a deploy
How the response time checker works
No signup — enter a URL and get the status and timing back.
1
Enter a URL
Provide a full URL or just a domain; NorthDuty defaults to HTTPS.
2
We request the page
NorthDuty makes a single GET request, following redirects safely, and times the full response.
3
You get status and timing
See up/down, HTTP status, response time, and a speed rating — nothing is stored.
4
Keep it monitored
NorthDuty's uptime monitoring runs this check on a schedule and alerts you the moment the site slows or goes down.
How to read the number
This measures time to first byte from one location, on one request. That is a narrow but useful signal.
| Result | What it suggests | What to look at next |
|---|---|---|
| Under 200 ms | Healthy, or a cached response served from an edge | Nothing |
| 200–600 ms | Normal for an uncached dynamic page | Worth checking whether caching is working as intended |
| 600 ms – 1.5 s | The server is thinking too long | Database queries, an uncached homepage, a slow plugin or an origin far from the test location |
| Over 1.5 s | Visitors feel this before anything renders | Hosting tier, a plugin doing work on every request, or an external API called during page build |
| Wildly different between runs | Contention or cold caches | Re-test a few times; a single slow run is not a trend |
What this does not measure
Time to first byte is not page load. A page can answer in 120 ms and still take six seconds to become usable, because the images, scripts and fonts that follow are what fill the screen. For that side of the picture, check page weight and your Core Web Vitals.
It is also a single measurement from a single place. A store whose customers are in Australia learns little from one European check. What a one-off test is genuinely good for is a before-and-after: change the caching setting, test again, keep the change or revert it.
Go Beyond One-Off Checks
Use the tool preview for a quick answer, then move into recurring monitoring for your most important pages and journeys.
Feature
Uptime Monitoring
Monitor uptime every 5 minutes by default with HTTP, SSL, DNS, blank-page detection, broken resources, JavaScript errors, and API call tracking.
Explore Uptime MonitoringFeature
Website Performance Monitoring
Monitor website performance signals, response timing, and rendering context on the pages and journeys that affect revenue, leads, and trust.
Explore Website Performance MonitoringFeature
Alerting
Send NorthDuty alerts to email, Slack, Teams, Discord, Google Chat, webhooks, Telegram, WhatsApp, and SMS.
Explore AlertingArticle
How to Monitor Website Uptime
How to monitor website uptime properly: check intervals, locations, false alarms — and the failures that return HTTP 200 so uptime checks never see them.
Read How to Monitor Website UptimeArticle
Get Alerted When Your Site Goes Down
Set up alerts that catch more than downtime: check frequency, channels, false alarms, and alerting on the checkout, form and page failures that return HTTP 200.
Read Get Alerted When Your Site Goes DownArticle
How Often to Monitor Your Website
How often should you check your website? Monitoring frequency by site type, what 1, 5 and 15-minute checks mean, and how to balance speed against noise.
Read How Often to Monitor Your WebsitePricing
Pricing
NorthDuty plans are sized by how many checkout, signup and login journeys you monitor: Free, $29 Starter, $79 Pro, $199 Business. 7-day trial, no card.
Compare pricing plansFrequently Asked Questions
Answers about this diagnostic preview and when to move into recurring monitoring.
What is a good website response time?
Under 200 ms is excellent and usually means a cached response; 200–600 ms is normal for an uncached dynamic page; over 1.5 seconds is felt by visitors before anything appears on screen.
Is response time the same as page load time?
No. This is time to first byte — how long the server takes to start answering. Page load also includes downloading and rendering everything the HTML references, which is usually the larger share.
Why does the result change every time I run it?
Server load, cold caches and network routing all vary. Run it a few times before concluding anything, and compare like with like — same page, same time of day.
Is this response time checker free?
Yes. It's free and requires no signup. Enter a URL and you get its status and response time immediately.
What does the response time include?
It measures the full request from NorthDuty's server — DNS resolution, connection, and the time to receive the response — so it reflects real-world round-trip time rather than just server processing.
Why might the time differ from my browser?
The check runs from a server, not your location, and does not load images, scripts, or styles. It measures the document response, so it is a clean baseline rather than a full page-load time.
Does it follow redirects?
Yes. It follows redirects safely and reports the status and timing of the final response, and tells you if a redirect occurred.
Start monitoring your website with NorthDuty today.
A one-off check only tells you about this second. NorthDuty watches uptime and response time continuously and alerts you the moment your site slows down or stops responding.
7 days with Pro features and limits, no credit card — then keep one daily journey on the free plan.