ZebraTester results can come in handy when diagnosing problems. The results can help pinpoint issues not only for full response time of an object or page, but for the actual timings of the request which isn't shown by default. 

After running a loadtest you'll be presented with this screen: 

To see the result details click on the load test name. In this case it's "test".

The response time average here is an average built from all the samples of the requests made, #1 GET https://www.zebratester.com/ - which is the example that we will be looking at here - had a quick response time of 36 ms on average but where can you find the values that was used to calculate that?

To gain access to this information we can access an alternative view with more details around each request, this is done by clicking the test number for the specific request, in this case we want to click on Test 1 which represents GET https://www.zebratester.com/, it can be found to the far left on the same row as the request.

The new view we are presented with now contains the following columns:

Av DNS How long did DNS resolution take
Av Net How long it took to establish a connection
Av TLS/SSL How long it took to perform a TLS/SSL handshake
Av Req Trm How long it took to send request headers and content
Av Wait How long it took until time to first byte
Av Header Rcv How long it took to receive header responses
Av Content Rcv How long it took to download the response content

All of these timings added up translates into Av Time in the result meaning average response time both in ZebraTester and in the LoadTest portal, this can be leveraged in many ways by just observing where the response time is spent in between these.

**If the most time is spent in Av Net, Av Header Rcv and Av Content Rcv then the issue is most likely based on latency or network issues, if the time is instead spent on Av Wait and Av SSL/TLS it is possibly a problem with a server being overloaded depending on the setup.

There are many more ways these timings can be useful for debugging performance issues with your website or application but i hope this helps.