State	Total time
wait4resolve	0.39 s	2%
queue	9.8 s	41%
resolve	1.1 ms	0%
connect	1.20 s	5%
headers	6.2 s	26%
body	6.1 s	26%

Bytes
4	css	17 897 B
2	html	53 381 B
3	image	18 491 B
24	image(css)	28 545 B
22	script	135 864 B

Request states description

Resolving hostname: To make a connection to some host, its domain name must first be resolved , i.e. converted to network IP-address. This process takes some time, thus adding more hosts to page may slowdown its loading.
Hint: You may avoid resolving delay, using IP-address instead of domain name.
Waiting other thread for host resolve: Requests in that state can not be processed because its IP-address is still not known, but resolving is already started.
Hint: Place URL where some domain name appears first in html-document as top as possible. You can even try to place URL to fake needless image in <HEAD> section, so browser will start resolving at early stage of page loading.
Request is waiting in queue: Usually, browsers do not begin to process http-request as soon as it is enqueued, preventing web-servers from overloading. There are per host limit of simultaneous connections, and total limit of all connections. These limits vary from browser to browser, and today are common values of 8-10 parallel requests per host and 32-128 total.
Hint: If you see that many requests spend much of its time in browser queue, you could consider increase number of hosts that will serve these requests. You even can create domain aliases which point to same IP and are served from the same directory, because browsers looks only on domain names, not its IPs when applying connect limits. But remember, that each additional domain will add corresponding resolving and connecting delays, so 3-6 such aliases are quite enough.
Connecting to server: Hint: Enable Keep-Alive feature on your web-server and keep number of different hosts low enough. Place your server closely to your customers, at least on the same continent. If you see that some connections takes abnormally long time, it may mean that server experience problems with accepting new connections.

Sending request and receiving http-headers from server: This stage reflects the time spent on delivering http-request to server and http-headers of response from server. It is usually equal to connect time, but there are many factors influencing how much time will be added to this: how fast server will accept new connections, how many different modules will be initialized before beginning to process the request, how long .php or .cgi application will initialize itself before preparing http-headers of response, how fast OS will fetch requested file from disk... Also you should remember that each http-request includes all domain cookies that has been set previously, which directly affects the size of http-request.
Hint: Don't compile/load needless modules into apache or php - they will consume resources even if they aren't used at all. Use appropriate software for each task - nginx or lighttpd for static content, apache without mod_ssl for dynamic content and separate apache with mod_ssl for secured pages. Keep size of cookies low to decrease size of http-request, don't use cookies if they aren't really needed, use session cookies instead of persistent cookies.
After headers received, waiting for document data: Usually web-server send data after http-headers without delay, but may be you will happen upon situation when web-application prepare http-headers much before page itself.
Receiving all document data: This is final stage and depends mostly on page size and network quality.
Hint: Compress your data. There are many tools which help to decrease the size of images and movies. Optimize html markup, clean css files, remove out comments from .html and .js files.

URL
Host
Test-point	Select test-point here .. AdvancedHosters.com TeleCity (Amsterdam, Netherlands) AdvancedHosters.com Equinix (Ashburn, VA, USA) AdvancedHosters.com Pilosoft (New York, USA) Softec S.p.A. I.NET (Florence, Italy) AdvancedHosters.com TeleCity (Amsterdam, Netherlands) AdvancedHosters.com Equinix (Ashburn, VA, USA) AdvancedHosters.com Pilosoft (New York, USA) Softec S.p.A. I.NET (Florence, Italy) >>> Would you like to see your server in this list?
Max threads per host	Hide options ..
Link control	Bandwidth: Packet loss (%): Delay (ms): +
Rate control	Packets to send: Packets per second:
Options	Protocol: Type-Of-Service:
Support for	HTTP-compression: Keep-Alive: Referer:
HTTP-Auth	Login: Password:
DNS override	IP: Domain: + IP: Domain: IP: Domain: IP: Domain: IP: Domain: IP: Domain: IP: Domain: IP: Domain: IP: Domain: IP: Domain:
Anti-bot protection

Start time (GMT)	2010-02-04 15:17:02
Download time	4.2 s
Connects	13
Requests	55
Not found	1
Documents total size	254 178 B
Headers total size	17 308 B
Compressed objects	24
Compressed bytes	45 011 B
Average compress ratio	47 %
Effective compress ratio	84 %
Average download speed	510 Kbit/s
Effective download speed	595 Kbit/s