For a website check it includes the DNS lookup, connecting, the TLS handshake, the server’s processing (the wait for the first byte) and downloading the response. Splitting it into these phases shows where the time goes: a slow server phase points at the application or database, slow DNS or TLS at infrastructure.
Report response time with percentiles. The median is the typical experience; the 95th percentile shows the slow tail that an average hides.
Response time from a monitoring check isn’t page load time in a browser, which adds images, scripts and rendering. It is the part the server controls, and a rise is often the first sign of trouble before an outage.
Formula
Response time = DNS + connect + TLS + server wait + download
Example:
38 ms DNS + 21 ms connect + 44 ms TLS + 182 ms server + 15 ms download = 300 ms.