| Forum Home | ||||
| PC World Chat | ||||
| Thread ID: 80858 | 2007-07-07 00:21:00 | Useful Web Optimisation Tips | TGoddard (7263) | PC World Chat |
| Post ID | Timestamp | Content | User | ||
| 566663 | 2007-07-07 00:21:00 | I just came across a site with some very good tips for optimising web page content here: www.die.net There was even a reference to NZ: Regularly use your site from a realistic net connection. Convincing the web developers on my project to use a "slow proxy" that simulates bad DSL in New Zealand (768Kbit down, 128Kbit up, 250ms RTT, 1% packet loss) rather than the gig ethernet a few milliseconds from the servers in the U.S. was a huge win. We found and fixed a number of usability and functional problems very quickly. Telecom is obviously world famous, and not only in New Zealand! |
TGoddard (7263) | ||
| 566664 | 2007-07-07 00:44:00 | Note the reference to pipelining: 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. Firefox pipelining can be modified through the "about:config". Dunno about other browsers. Edit: I think FasterFox turns on pipelining. And for *nix users, consider installing a web proxy-filter. I use polipo, which does all the pipelinig, caching and filtering. You will notice the speed, especially on slow access like dial-up. |
vinref (6194) | ||
| 1 | |||||