The golden rule of web performance states that for most web pages, less than 10–20% of the end-user response time is spent getting the HTML document from the web server to the browser while 80-90% of the end user response time is spent on the frontend.
When we talk about performance testing, the most common activity that we do is to load test our backend servers. We come to a realisation that once we have optimised our servers and databases, that our application is now performant. However, this should not be the case. There are many factors affecting frontend performance as well and it’s equally important to test to make sure that our users have the best user experience.
In this talk, I want to introduce you to both frontend and backend performance testing and why a hybrid approach to performance testing is needed to make sure that your website is performant. I’ll also give a quick walkthrough as to how tools such as k6 and xk6-browser can help with running both protocol-level (how performance testing is normally run through concurrent interactions at the protocol layer) and browser-level tests (testing with real browsers to provide a more realistic performance test).By the end of this talk, you should be equipped with new knowledge regarding frontend and backend performance testing which you can apply to your work projects.
About The Author