How to troubleshoot the performance of a Web application
- What should you do?
- What patterns should you look for?
First make sure you are getting the right data!
- Page response times
- Hit response times
- Error indicators
What are the most common patterns of performance leaks
Let's take a look at the pattern you need to identify to troubleshoot the performance of your application and pinpoint where the performance leaks are.
Slow page load times
- The number of hits integrated in the page
- Scripts which are too heavy or slow
- Scripts provided by external services (e.g. tracking services etc.)
- Slow server processing: your web server is taking too long to process the response.
- Slow transfer: the response takes too long to be transferred from the server to the client through the network.
In this case, you should investigate:
- The response size (is that 2MB image truly necessary?)
- Is the network offering a performance which is good enough (network latency, retransmission / packet loss rates)?
- Are the client and the server slowing down the transfer? (you learn more on this by reading this article on the impact of TCP events on application performance)
- Client errors (4xx errors): the clients may be directed to an invalid URL.
- Redirections (3xx errors): some element in the chain may redirect to other resources and generate delay and errors.
The network traffic is proper source to create performance analytics on all the users activities and for all the applications hosted in your datacenter in a 100% non-intrusive way.
Discover how you can get an end-to-end application performance visibility with Wire data from network layers up to the application transactions: