IE, Firefox, and Safari ship with HTTP pipelining disabled by default; Opera is the only browser I know of that enables it. No pipelining means each request has to be answered and its connection freed up before the next request can be sent. This incurs average extra latency of the round-trip (ping) time to the user divided by the number of connections allowed. Or if your server has HTTP keepalives disabled, doing another TCP three-way handshake adds another round trip, doubling this latency.
serving small objects might mean the page load is bottlenecked on the users' upload bandwidth, as strange as that may sound. By default, IE allows only two outstanding connections per hostname when talking to HTTP/1.1 servers or eight-ish outstanding connections total Turn on HTTP keepalives for external objects. Load fewer external objects.
Minimize HTTP request size. Regularly use your site from a realistic net connection |
I consigli della nonna, efficacissimi come sempre.
Nessun commento:
Posta un commento