What does the Cloud HTTP sensor measure as Response Time

Document load is the time it took to load the entire page without it's linked assets (i.e. css files). Wikipedia defines the Time-To-First-Byte like this:

---

Time To First Byte

...is a measurement that is often used as an indication of the responsiveness of a webserver or other network resources.

It is the duration from the virtual user making an HTTP request to the first byte of the page being received by the browser. This time is made up of the socket connection time, the time taken to send the HTTP request, and the time taken to get the first byte of the page.

Link to full article

---

What other metrics were you talking about? :)

May, 2015 - Permalink

Hi Stephan,

Thanks but I know what TTFB and Document Load mean, the question is:

The Cloud HTTP Sensor [...] is returning a "Response Time" channel. What is the measure behind this ["Response Time"] metric?

Thanks Thomas

May, 2015 - Permalink

Well you asked for it :)

The response time represents the time the server took to fully process the requested page (i.e. deliver it to the client) until a response code is sent to the client. More on that can be found here.

May, 2015 - Permalink

Thanks Stefan, that's what I was looking for: the time between the request sent and the document is fully downloaded. Can you confirm that the test doesn't load extra elements, just the main page? (e.g. CSS, JS, etc.)

I'm looking for equivalence between the Catchpoint metrics and the PRTG cloud HTTP sensor.

I realise that my question was confusing, sorry about that.

May, 2015 - Permalink

As far as I know, assets are not loaded - I'll ask the developer just to make sure :)

Update
Just asked the developer - all assets are loaded, just like when you load the file in a browser. The only exception are javascripts, they're not executed. Additionally, the request has to be completed within 5,000ms :)

May, 2015 - Permalink