Performance tests in Rigor Optimization enable you to scan your site and analyze content in a few different ways. These test types govern what content we scan and how the information is organized. Advanced settings for Optimization tests enable you to tweak how the content is scanned with three major categories:
- Scanner Options. Customize the behavior of the performance scanner.
- Browser Configuration. Customize the browser configuration used for your performance scan.
- Authentication. You can test password protected pages by specifying basic HTTP Authentication or configuring a login script.
|Scanner Options||Browser Configuration||Authentication|
From the New Test window, click Advanced > + Add Scanner Options to customize the behavior of the performance scanner.Scanner Options
Defect Check Policy: Limit which Defect Checks your performance test runs. This is useful for ignoring known defects or testing specific scenarios. For example, you could ignore all lossless image optimizations. Learn more about defect check policies from our blog.
Third Party Content Identification: Use this option to determine how Third Party Content (content not owned by your team) is identified with two options:
- Use All content not from a whitelisted domain to classify any content not from your start URL domain or whitelisted domains as Third Party Content. This is the recommended setting if you scan a relatively few number of sites repeatedly.
- Use Auto-classify using database to classify Third Party Content using an internal database of known third parties. This is the recommended setting if you are frequently scanning different sites and don't want to maintain a whitelisted domain list.
Resource Requesting Behavior: Specify which resources are analyzed based on how they're linked from the page with two options:
- Displayed resources only includes only those resources loaded for page rendering, but may miss defects from older browsers. Note: this option must be selected to view waterfall charts.
- All linked resources includes all possible defects for all browser types but may include defects some site users do not see.
From the New Test window, click Advanced > + Add Browser Configuration to customize the browser configuration used for your performance scan.
Cookies: Pass specific cookie values (one per line) to test logged in pages or other test scenarios.
Custom HTTP Headers: Pass custom HTTP headers (one per line) to your site to analyze specific test scenarios.
DNS Overrides: Add DNS override rules (one per line) to customize how page resources are requested. This is useful for testing your production site against page resources loaded from a development site or a specific CDN edge node. Learn more about testing optimizations with DNS overrides and single points of failure from our blog.
From the New Test window, click Advanced > + Add Authentication to test password protected pages.
From this window you can handle login forms with two forms of authentication:
Login Script: used to test password protected pages by configuring a login script common for logins to web interfaces
HTTP Authentication: used to test pages with basic HTTP authentication common for pre-production sites and development environments
- Login Page URL. This is the URL of your login page where the user/password form fields are located.
- Login Form Name (optional). This is the name attribute of the form HTML tag that surrounds your user/password login form fields. Leave blank to auto-match the first form tag found on the page.
- Login Credentials. Field Name is the value of the name attribute of the form input tag for which the login script should enter a value. Typically this is just the literal text email or password but could be different depending on your site design.
Value is your actual email, password, etc. value that should be submitted with the form (e.g. firstname.lastname@example.org).
Using the settings below, you can customize what gets posted to the login page URL and even add additional fields to post. To maximize your security, we recommend supplying a test login with limited permissions.
See example below using Rigor Monitoring's login page.
- Use HTTP Authentication Headers to specify each HTTP authentication header you want to send in a separate line using this format: username:password@domain
- Example: http://bobsmith:email@example.com
- As an added security measure, the user/password pair will only be sent for requests matching the specified domains.