Web pages

The web page is the page as rendered by a web browser. It consists in the HTML page and all its sub-components, such as image files and CSS style sheets.

Name	Name of the web page in NeoLoad.
URL	URL of the first HTTP request forming the page is displayed here for information purposes.
Description	Description of the web page here if required.
Think time	Interval before a web page is accessed. This corresponds to the time a real user would spend reading the page displayed by the browser before clicking on a link or filling in a form before submission. Use this box to set the think time for this page or click on the link to the runtime settings pane to set a global think time for all pages. The default policy is to use the think time defined for each page (to change this policy, click on the same link).

In the User Path definition, you will find several ways of managing think times (add a factor to all think times, vary the think times by a random amount, etc.). See Think time.

Page screenshot	Screenshot of the browser content at the instant the web page was recorded. Please note that this function is only available in Windows and is merely a reminder of what was displayed in the browser window when the web page was recorded. Screenshots are only available for web pages with an HTML content. If the screenshot does not mirror the actual web page, it may be deleted. Automatic screenshots during recording may be turned off by changing the value of the recorder.screenshot.enabled key in the [GUI] section of the <NeoLoad>/conf/Controller.properties file to false.
SLA	The service level agreement profile linked to the page. See Link a User Path element to an SLA Profile.
Advanced	Request playback The NeoLoad default setting is to play back requests in compliance with the HTTP protocol with the browser using several parallel connections to retrieve a page resources. For specific needs, we may force NeoLoad to play the requests sequentially and according to their order in the page definition contained in the User Paths. Dynamically execute the page resources By default, NeoLoad executes a page resources as they were recorded. If the resources are dynamic, NeoLoad always executes the recorded resources. By checking this option, the page resources (excluding module requests) are disabled and NeoLoad will analyze the HTML response to the first request and dynamically execute requests to the server to load the resources.

Warning: NeoLoad retrieves resources present in the HTML code. Resources referenced by CSS style sheets and JavaScript scripts are ignored.

If the first response is a redirect, NeoLoad automatically sends the request to retrieve the HTML page. So, if the number of redirects has changed between recording and playback, NeoLoad automatically handles the redirects.

Dynamically-executed requests do not provide detailed statistics. In Runtime and Results views, their statistics are grouped together in a specific request named <dynamic resources> under the page.

If the page contains requests that are not resources—for example a request originating from client-side code (JavaScript, Flash, and so on)—these requests can be flagged as being non-dynamic. The Enabled command in the action pop-up menu must be selected to make the action active. The action is no longer grayed-out and NeoLoad can execute it as a standard request.

When checking the validity of a User Path containing dynamic pages, the grayed-out requests (to be executed dynamically by NeoLoad) do not show up in the User Path tree. However, the dynamic results are displayed in the table.

Home