The success of the Web performance movement shows that there is increasing interest and value in fast websites. That faster websites lead to more revenue and reduced costs is a well proven fact today. So being exceptionally fast is becoming the dogma for developing web applications. But what is exceptionally fast and how hard is it to build a top performing web site?

Read the full article

Seriously ..

Looks like some kind of DynaTrace whitepaper.

The top-level TSS introduction to this is terrible. The article it points you too is a decent summary of the overhead to delivering Web content to users.
As a TSS reader and Java person I can take this in a bunch of directions:
1) Alois' blog points us to the book "Designing and Engineering Time: The Psychology of Time Perception in Software". I'd like to know how we can appy page loading time to JSF and any of the *faces libraries out there?
2) His blog points us to the HTTP Archive (HAR) project. TestMaker repurposes HAR files to be functional tests, load and performance tests, and Web page loading service monitors. A tutorial is at http://www.pushtotest.com/web-application-tests-using-http-archive-har-test. I'd like to know if TSS readers are really using HAR?
3) His blog says "It seems like two seconds is the magic number for a web site to load." dynaTrace is for functional testing. How do you bridge the gap from functional to load testing? I'd like to see what the TSS community is doing for that. And, did you notice TIBCO's "2 Second Advantage" strategy (http://ovum.com/2011/07/25/where-should-the-two-second-advantage-take-tibco-next/) It's basically about delivering NoSQL and Big Data Solutions. Seems to challenge Oracle and others.
All interesting topics masked by a terrible introduction. :-)
-Frank

Re point 2, we've started to use the HAR format. It's still early days but it's useful. Tim Morrow mentioned it in his talk at Velocity EU.