How to interprete the page response time?
I have a quick question regarding the page response time in the test report. I understand the way how loadComplete measures page load time is different from staring at the browser and count until th...
Forum Discussion
Hi Sergel
Thanks for the clarification. That shall help us understand the test result better moving forward.
The KPIs we currently focus on is the page load time. The web app is a dashboard-type of app which contains lots of client side js scripts, images, videos, and flash. The page load time from the initial test was much higher than we thought because the way loadComplete operates. That is why I asked whether loadComplete can emulate as an real browser and measure performance based on that fashion. Given the fact that loadComplete emulates requests sequentially and then aggregate those number at the end, how do people usually interpret the page load time from the report and correlate that number with web app's performance matrix?
Thanks for the clarification. That shall help us understand the test result better moving forward.
The KPIs we currently focus on is the page load time. The web app is a dashboard-type of app which contains lots of client side js scripts, images, videos, and flash. The page load time from the initial test was much higher than we thought because the way loadComplete operates. That is why I asked whether loadComplete can emulate as an real browser and measure performance based on that fashion. Given the fact that loadComplete emulates requests sequentially and then aggregate those number at the end, how do people usually interpret the page load time from the report and correlate that number with web app's performance matrix?