According to Alberto Savoia, the (Photoshop web design) Director of Software
According to Alberto Savoia, the Director of Software Research at Sun Microsystems’s Laboratories, there are four behavioral laws that make web page performance critical to an organization’s success: The Law of Stickiness This law states that web users are sticky, but not loyal. If they find a web site that serves their needs, they tend to continue to use that site. If the web site begins to respond slowly and cause the users to wait, they will move to another site that fulfills their same needs. The point is to strive to keep the performance of the application strong in order to keep the users coming back. The Law of User Perspective This law states that you should always measure the performance of your application from the user’s point of view, not from your own. The point here is that, for example, while your environment may have a 100-MB network with an otherwise light load on it, the user may be using a modem with a much smaller bandwidth capability. Always keep in mind what the user’s environment and network capabilities will be and test accordingly. The Law of Responsibility This law states that the users don’t care what or who is at fault for poor web site performance; they will always blame the application. The problem might be their ISP or another nonapplication issue, but most users will not be able to isolate the problem to that level and instead will blame the application or site. You must be aware of all the factors that may impact the performance of your application. The Law of Expectations This law states that users’ satisfaction is based on their expectations, which are set by their personal experiences with other, similar web sites. When measuring the performance of your application, don’t rely just on arbitrary numbers to indicate what’s slow or fast; compare your results with those of your competitors. These simple, common-sense laws explain the human-behavior aspects of web site performance. In general, however, slow is slow and fast is fast, and generalizations can be made across applications and business domains. But before we discuss how to detect whether performance problems exist in an application, a distinction must be made between the types of performance testing that should be conducted. 17.2 Performance Versus Load Testing There are many different types of software testing: functional, unit, integration, white box, black box, regression, and so on. Performance and load testing are among the most important types of testing, but they usually get the least amount of attention. There are two general reasons for this neglect. The first reason is that developers typically wait until the very end of the development cycle to start testing the performance of the application, and the end of the cycle is when you have the least amount of time for testing. It is true, however, that it’s not always practical to conduct performance testing during every phase of development. Early phases tend to focus on the architecturally significant pieces, and there may not be enough of the application built to test its performance. You should, however, gather some preliminary performance measurements as early as possible.
Note: In case you are looking for affordable and reliable webhost to host and run your j2ee application check Vision J2ee Web Hosting services.