Web performance testing is effective if done where the end users are actually present
the web.Testing also need to be done at different geographic levels, a big discrepancy in the page response times from different locations may point to the latency issues related to some backbones or the ten worst performing pages as the load level is increased indicating the pages causing performance bottlenecks.
When assessing Web user experience, two major questions arise: what group of users will be studied, and what kind of data will be collected? The answers to these questions are interdependent, as well as dependent on the resources available to the researcher. This interdependence usually results in a trade-off between the quantity of data collected and the quality of that data.
Two questions arise when we are assessing web user experience: The group of users that needs to be studied, and the kind of data that needs to be collected. These two questions along with their results are interdependent. This inter dependency also depends between the quantity of data which was collected and the quality of that data. The data samples can vary, but we would need a large data sample to get an overall representation of the target population. This provides more support in prioritizing the importance of issues and to determine the usability changes to improvise on performance.
Web monitoring is essential, and we need to make changes based on the results and statistics from web monitoring services. Our sites need to be ready to take good loads and need to work at optimum levels at all times in order to look forward for business benefits.