Sign up in 30 seconds.
No credit card.
No risk.
No download.
Web Performance Testing
There is a difference between performance testing of a traditional client server application versus a web application.
Web performance testing involves primarily HTTP traffic. There are latencies involved with Internet technologies that you shouldn't encounter on an internal software implementation.
Web performance testing can be the measuring and analysis of a single web page. Taking apart the download times of each individual resource such as an image, an HTML document, or a stylesheet. Web performance testing should also involve measuring the DNS lookup times and how long it takes to get a connection to the server.
Rendering is a key element of understanding the performance of a web page. Specifically, how long after the user makes a request does the browser start to paint something.
It is also critical to measure the actual server processing time for a request. The browser side perspective of the end user is important, and that is where large images or too many files can cause poor user experience. Additionally, if the database is a bottleneck that results in 5 seconds to put together a dynamic page, that is a performance problem.
Bookmark/Search this post with:
