I'm running a test for one of our production website. The test has total 6 steps.
The response time of the test is always 13 to 14 seconds. But when actually I access the website from my browser it's really quick.
Not sure why there is difference in my test response time and the real browsing.
Answer by Gary S. ·
A few things here - are you viewing response time by step, or by test? If you are viewing by test then this 13 to 14 seconds is the average adding all of these steps, so end to end from step 1 through step 6.
I have a test with 3 steps, the default display will show me response time calculated for all of the steps.
If I change this to be response time by step:
Then I can view the response time for each step that makes up the transaction.
Otherwise, maybe there are some objects preventing the page from appearing as complete, like some network requests preventing that from happening or third parties can often be the case. But I would expect to see that take longer and on a step level than for the entire journey.
Let us know if this works :)
Answer by Roushan K. ·
Hello @Gary S., Thanks for such descriptive response. That really helps.
I receive alert for high response time( ~40 sec) for any of the step of my test. But at the same time when I really try that step on my browser it appears to pretty quick to me (~3 sec). Any idea for such difference.
browser screen size on replay 1 Answer