With the onset of HTTP 2.0, there are lot of implications seen in web performance.
Web application development (based on Web 2.0 & Web 3.0 standards) carrying more & more client-side functional logics to make it more dynamic, controversial & intelligent, the need for web performance (clients-side browser performance) has started becoming very essential piece during in web application performance assessment.
Other than focusing only on server-side performance to handle multi-user concurrent load, its important to understand the performance impact caused at the client-side (browser) to render the web page.
Remember! Your Performance testing tool (Example : JMeter) is not a browser. The tool reported response times metric (during your load tests) doesn't include realistic browser rendering time. So, do plan to include 1 user test to measure client side browser rendering performance on the recommended browsers.
Hence metrics like page component loading time, first byte time, page weight, etc became very important. Static files (like CSS, JS, Images, etc) requires several optimizations to ensure the page loading time is kept minimal.
It is the responsibility of Performance Tester to ensure web performance analysis is included in the Performance Test Strategy for certifying the web system performance.
There are several tools available to measure the web performance. The choice of the tool depends on factors like are you interested in measuring performance across mobile devices or browsers or locations, are you interested in page speed score & optimization recommendations, are you interested in quantitative scores in different aspects of web performance, are you assessing web performance during SDLC or need web performance monitors on ongoing basis, etc.
Here are some of the popular tools that i have used to meet different type of client requirements& found very helpful & effective.
Happy Web Performance Testing !!