Speed up Chrome's network stack by enabling HTTP Pipelining. Pipelining issues multiple requests over a single connection without waiting for a response.
Response headers must have the following properties:
Pipelining does not begin until these criteria have been met for an origin (host and port pair). If at any point one of these fail, the origin is black-listed in the client. If an origin has successfully pipelined before, it is remembered and pipelining begins immediately on next use.
Pipelining is disabled by default. There are known crashing bugs and known front-of-queue blocking issues. Until these are resolved, it's recommended nobody uses pipelining.
Pipelining is available on all platforms starting with Chrome 18 by adding --enable-http-pipelining. It is disabled by default.