Det var som 7 Søren ...
I'll be damn ...
The scripting language is one of several culprits that slow Web site loading
Nowadays, even regular Web surfers know some of the things to do when designing a Web site for fast performance. Cut the number of requests to the Web server. Shrink JPEG sizes. Enlist the services of a content delivery network vendor like Akamai Technologies Inc. or Limelight Networks Inc.
Problem is, according to Steve Souders, steps like those, which are aimed at optimizing the Web server, make only a tiny impact.
"We used to tear apart the Apache [Web server] code to figure out what Yahoo was doing," said Souders, who was Yahoo Inc.'s chief performance engineer for several years before moving to Google Inc. in the same role.
But after performing a detailed analysis, Souders discovered something startling: Only 10% to 20% of the time it took to load a Web site could be attributed to the Web server.
The vast majority was the result of code executing inside the Web browser, said Souders at a talk on Tuesday at Microsoft Corp.'s Tech Ed conference in Los Angeles (download PowerPoint here).
That might have made sense a decade ago, but in today's era of PCs powered by dual- and quad-core CPUs, it doesn't. And the cost of the delays created can be high.
Google has found that a 500-millisecond delay results in a 20% decrease in Web traffic, while Amazon.com Inc. has seen a 100-millisecond delay cutting its sales by 1%, Souders said. [...]
Read more: http://www.computerworld.com/action/article.do?command=printArticleBasic&taxonomyName=Web+Site+Management&articleId=9133056&taxonomyId=62