This article relates to Web and Transaction tests using the Chrome and Mobile monitors. It describes the behavior you will see when you are receiving error 50011 – Connection Failure, or 50010 – DNS Failure
In both cases, Chrome now displays a page after the failure occurs. This page looks like this.
This indicates that the timings reported by the browser appear as Webpage Response, as we will reach DomContentLoaded and Document Load (which is shown by a blue line and a red line in Chrome Developer tools). The browser doesn’t report a request time, as it is blocked. We therefore see the time until the Document Complete.
For the Connection Failure error, two entries will display. One is the initial request, and the second is the webpage being displayed at approximately the 21 second mark after the connection failure occurs.
Chrome actually tries to automatically reload the page five minutes, ten minutes, and then every thirty minutes after these timeouts.
For the DNS Failure, two entries will also display. The first is where the initial DNS lookup takes place, and the second is where the webpage appears after the lookup has failed.
Take note of these timing metrics as the errors are correct, but due to browser behavior, the timings are sent as a Webpage Response.