Unanswered question

Response time in NeoLoad Report is different from response time captured in browser's console

Response time for transactions is coming different from the time displayed when checked through browser's console.
E.g For a JPG file, we are getting 119.1 secs in NeoLoad report but in browser's console it is showing 1.0 secs for that particular JPG, so there is a very large gap.

Ankur S.
Ankur S.

Ankur S.

Level
1
115 / 750
points

Answers

Ankur S.
Ankur S.

Ankur S.

Level
1
115 / 750
points

Any updates on this?

When did you get those statistics in the browser and NeoLoad? Was it during a load testing from browser installed in the load generator machine?

Did you check if the JPG file was not from the browser cache? Also 119.1 was it an average on multiple executions or a maximum?

Ankur S.
Ankur S.

Ankur S.

Level
1
115 / 750
points

JPG file was not from the browser cache and 119.1 is the average response time, have executed the NeoLoad script for 1user.
I have checked in the browser's console by Inspect Element, have attached the screenshot for your reference from where I have checked it manually.

On NeoLoad side if you run a simple checkvu of your user path what is the response time of that same request? Is it really the same one with the same parameter that we can see in your browser?