Slashdot Mirror

← Back to Stories (view on slashdot.org)

Optimizing Page Load Times

Posted by ryuzaki0 on

John Callender writes, "Google engineer Aaron Hopkins has written an interesting analysis of optimizing page load time. Hopkins simulated connections to a web page consisting of many small objects (HTML file, images, external javascript and CSS files, etc.), and looked at how things like browser settings and request size affect perceived performance. Among his findings: For web pages consisting of many small objects, performance often bottlenecks on upload speed, rather than download speed. Also, by spreading static content across four different hostnames, site operators can achieve dramatic improvements in perceived performance."

1 of 186 comments (clear)

  1. Re:4 hostnames and security by suv4x4 · · Score: 0, Offtopic

            Nice trick with 4 hostnames, but this means 4 security contexts for your content, which may make a lot of development hard (especially client based with JavaScript).

    Why? Doesn't your javascript explicitly state document.domain to the common root?

            Not to mention the management issues of having to link to content on 4 different domains in an efficient enough manner.

    You mean creating four hostnames for the same address? Or do you mean changing a few src="" attributes?

            This leaves us with pipelining on the client, which could results in much worse load peaks on the servers though.

    Wrong. It leaves us with nothing. Didn't you read the article? HTTP Pipelining isn't enabled in the big two web browsers, so as far as "reality" is concerned it doesn't exist. It's like IPV6- who cares how much "better" it is if no one is using it?


    From your tone I assume it was very important part of your day arguing with someone on Slashdot for the hell of it. If I were you, I'd take measures QUICK.