An HTTP request consists of several stages. First, the webserver name has to be resolved into an IP address using DNS (Time for DNS), then an IP port is opened on the server by the client to send the request header (Time to Connect). The server then answers the request (Time to First Byte) and sends all data. When all data is transferred, the request is finished (Click Time).
Also in this graph a line is shown for the “time for local socket” which is the time that Webserver Stress Tool needed to acquire an open socket from the IP stack of the machine it runs on. For ususal test this value should always be in the lower millisecond area (1-30 ms). For extreme traffic tests this value can rise above 50-100 ms which is a sign that the performance limits of the local machine have been reached.
The average value of these five readings are displayed in this graph:

Webserver Stress Tool is a powerful HTTP-client/server test application designed to pinpoint critical performance issues in your web site or web server that may prevent optimal experience for your site's visitors.
Welcome
Introduction: Testing Basics
Performance, Load or Stress Testing?
Calculation of Load and Load Pattern
Webserver Stress Tool Features
How much load can Webserver Stress Tool generate?
Installation
Configuring Webserver Stress Tool
Selecting the Test Type and the Number of Users
Selecting the URLs or Editing the URL Script
Using Custom URL Scripts for Advanced URL Sequences
Performance Tips&Tricks
Running the Test
Reviewing Logfile Results
Analyzing Graphical Results
Graph Click Times & Errors (per URL)
Graph Click Times, Hits/s and Clicks/s
Graph Server and User Bandwidth
Creating Reports
Additional Features
Appendix
Software License and Contact Information