Information of Web-Base Development

Many of web development organizations have been taking asking the question "what is the standard response time for a web page?" But none of standards have been generally accepted because every web users has a different personal feeling. That means, we must analyze who are the customers, what their needs are, where there are located, what their equipment and what their connection speed.

The consideration factors for performance expectations can be divide into three broad categories; user psychology, system consideration and usage consideration.

1. User psychology
User psychology plays an important role in perceived performance, which is the most critical part on evaluating performance. How fast is fast enough from a user psychology perspective, it depends on several key factors that determine what is and isn't acceptable performance. The factors are users previous experience, activity type and surfing intent.

2. System considerations
System considerations included the system hardware, network and / or internet bandwidth of system, geographical replication and software architecture.

3. Usage considerations
The usage considerations referring to how web site or web application will be used. " Fast " means something different for different applications. Interactive sites need to be faster than mostly static sites. These considerations are very specific to the site and organization.

Collecting information about performance requirement in three areas. There are user expectations, resource limitations and stakeholder expectations. There's no way to predict user expectations unless users can tell their expectations to us before the requirements are set. When users are made aware of their connection speed, their expectations about performance shift accordingly. Limitations on resource such as time, money, people, hardware, networks and software affected performance requirements. We can easily obtain about stakeholder expectations, Stakeholder expectations generally want the system so fast and scalable that performance become non issue and for the least possible money.

Once we collected as mush information about users and stakeholders expectations as well as resource limitations, we need to consolidate all of information about user and stakeholder expectations as well as resource limitations, we need to consolidate all of information into meaningful, quantifiable, and testable requirements. There are three categories in determining and documenting performance requirements; speed, scalability and stability requirements.

Composite requirements simply means the application is minimally production-ready from a performance standpoint and composite goals means that application is fully production-ready from a performance standpoint according to today assumptions. There's no industry standard for web application performance and its depends on our own judgment to determine how fast is fast enough for our application.