Both refer to the same concept of Web page but NeoLoad sticks at protocol level: the page response time is the time between when the first Request is sent and the time of the last byte of the response of the last Request. (Like a for browser, requests within a page are parallelized). It means that NeoLoad measurement does not include the rendering time.

If you are interested in getting the full response time for a browser for a sample of calls, then you can integrate with Selenium as described here: http://www.neotys.com/documents/doc/neoload/latest/en/htm...

Yes NeoLoad page response time is close to the page loading and it does not compute the rendering time (works at protocol level) so I you're interested in it you can use a browser-based script with Selenium that is executed in parallel of the load test (Rendering time and page loading events can be sent to NeoLoad through the Data Exchange API for storage and correlation, Neotys Selenium driver does this automatically for you).

Hi Musaffi,

Q1. The EuE / Selenium stuff is supposed to be run in parallel of the load test. If you have a VUPath that executes the selenium when you launch the test, you must also have in your scenario a Population that contains a VUPath that simulates the load at protocol level. (regular Load Testing).

Q2. Comparison for third-party data is not yet available.

Q3. You need the link to Design REST API embedded in NeoLoad. So the host is where the Controller is running. See full path in the preferences "Project settings / REST API"

Hi,

Hard to give you advices without all the settings. You have to make sure that each population runs enough iterations. You may use time-based scenario (ex: run 5mn each population) or increase the duration of the Population linked to the Selenium: add more iteration or check the time.