The Catchpoint WebPageTest test examines a webpage and supports advanced analytics options including Lighthouse scores, run comparisons, and device emulation.
WebPageTest Properties |
|---|
| Name | A name used to identify this test. |
| Description | Optional additional information about the test |
| Run From: | Specifies the Date/Time Range during which the test should be active. By default the Start Date/Time is the time of test creation, and there is no specified end date, meaning the test will run indefinitely. |
| Index: | Optional benchmarking index to associate results from this test with. |
| Labels: | You may add one or more labels to a test to make it easier to locate the test or its results when performing analysis. |
| URLs: | Add one or more webpages to be tested. For each entry, include the following:
- Page Name: a friendly name to easily identify the page being tested (e.g. "Catchpoint Home Page")
- Page URL: the complete URL of the page to be tested (e.g. "https://www.catchpoint.com")
- Page Index: optional benchmarking index to associate results for this particular URL with.
- Page Label: optional label(s) to make it easier to locate results for this particular page when performing analysis.
|
| Authentication: | Settings and credentials for authenticating with the specified URLs, if needed. Select the authentication type and then input a username and password. |
| Time Zone | Specifies the time zone used when defining test scheduling. |
| Run Between | Specifies the hour(s) of the day during which the test will be run. Click "Add Schedule Window" and make a selection for each hour that you want the test to run. |
| Run per test | Specifies the number of times during each schedule window that the test will run. |
| Run From | Specifies the WebPageTest Node that will execute the tests. WebPageTest nodes are distinct from Catchpoint's fleet of public nodes for running the other test types. |
Supported Metrics |
|---|
| # CSS | Total number of CSS files downloaded during the test. |
| # Flash | Total number of Flash files downloaded during the test. |
| # Font | Total number of font files downloaded during the test. |
| # Html | Total number of HTML files downloaded during the test. |
| # Image | Total number of image files downloaded during the test. |
| # Items (Total) | The total number of files included on the webpage. For Object monitor tests, this value is always one. |
| # Media | Total number of media files downloaded during the test. |
| # Other | Total count of all files not defined otherwise. |
| # Script | Total number of JS files downloaded during the test. |
| Blocking CSS | The amount of time that the loading of an element was blocked while waiting for CSS |
| Blocking JS | The amount of time that the loading of an element was blocked while waiting for Javascript |
| CSS Bytes | Total size of CSS files downloaded during the test, in bytes. |
| Cumulative Layout Shift | Measures the unexpected shifting of webpage elements while the page is still loading. CLS looks at the proportion of the viewport that was impacted by layout shifts and the movement distance of the elements that were moved. |
| DNS (ms) | The time it took to resolve the domain name to an IP address. |
| Document Complete (ms) | The time it took from the initial URL request being issued until the browser triggered the "onload" event. Any inline requests or requests inserted via "document.write" must complete loading before the event is fired. Document Complete does not account for dynamic requests that may be generated later via JavaScript and/or DOM manipulation. |
| DOM Interactive (ms) | The time at which the page first became interactive (capable of recognizing input of some kind from the user) |
| First Contentful Paint | The time when the browser rendered the first bit of content from the DOM. (May be text, image, SVG, or even a <canvas> element.) |
| Flash Bytes | Total size of Flash files downloaded during the test, in bytes. |
| Font Bytes | Total size of font files downloaded during the test, in bytes. |
| Fully Loaded CPU Time | Measured as the time from the start of the initial navigation until there was two seconds of no network activity after Document Complete. This will usually include any activity that is triggered by javascript after the main page loads. |
| Html Bytes | Total size of HTML files downloaded during the test, in bytes. |
| Idle | The amount of time during the page-loading process that the system was idle (not actively loading an element) |
| Image Bytes | Total size of image files downloaded during the test, in bytes. |
| Largest Contentful Paint (ms) | The time when the largest image or text block (by screen area) visible within the viewport was rendered. |
| Layout | CPU time spent on layout |
| Loading | CPU time spent on loading |
| Media Bytes | Total size of media files downloaded during the test, in bytes. |
| Other Bytes | Total size of all files not defined otherwise. |
| Painting | CPU time spent on painting |
| Render Start (ms) | The time from initial navigation until the first visual content is painted to the browser display. |
| Response (ms) | The total time from the initial request until receiving the last packet of response data. It is the sum of DNS + Connect + ssl + Send + Wait + Load for all elements. |
| Script (ms) | Total time spent loading JS files, in milliseconds. |
| Script Bytes | Total size of JS files downloaded during the test, in bytes. |
| Speed Index | A calculated metric that represents how quickly the page rendered the initial user-visible content above the fold. A lower Speed Index indicates faster rendering of visible content. |
| SSL (ms) | The time it took to complete the ssl handshake with the server. |
| Time To First Byte (ms) | The total time from the initial DNS request to receiving the first response packet from the server. This is calculated as: |
| Visually Complete (ms) | The time when the visual area of a page has finished loading, meaning that all visible elements of the web page are 100% loaded. |