Metric | Description |
|---|---|
Request Components | |
| DNS (ms) | The time it took to resolve the domain name to an IP address. |
| Connect (ms) | The time it took to establish a TCP connection with the server. |
| SSL (ms) | The time it took to complete the SSL handshake with the server. |
| Send (ms) | The time it took to send the request to the server. |
| Wait (ms) | The time from when the request was sent to the server until the first response packet was received. *(Known as "First Byte" in some tools)* |
| 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: DNS (ms) + Connect (ms) + SSL (ms) + Send (ms) + Wait (ms) For tests where the primary URL has a redirect chain, TTFB is calculated as the sum of the TTFB for each domain in the redirect chain. |
| Load (ms) | The time from the first packet to the last packet of data for the response. (Other tools might call this metric “Receive” or “Receiving”) |
| Base Response (ms) | Sum of DNS and Server Response |
| Redirect (ms) | Time from the start of navigation to the end of the last Redirect. |
| Server Response (ms) | The time from when DNS was resolved to receiving the last response packet from server. (This shows the server response exclusive of DNS times) |
| File Size | The size of the content received from the host for a specific element, in bytes. |
| Downloaded Bytes | The total number of downloaded bytes from the primary URL of the test(s). |
| Total Downloaded Bytes | The total number of downloaded bytes for all elements of the webpage, including from the primary URL server and any redirects. |
| Throughput (KBps - Kilobytes per second) | Measures how efficiently the system was able to retrieve all elements in kilobytes per second. Throughput is calculated as follows: Throughput = Size / Time where: Size = (FileSize + HeaderSize)/1024 *converts from bytes to KBs Time = (Wait + Load)/1000 *converts from ms to seconds |
| Get (ms) | The time it took to connect to the FTP server and query it for the file size. |
| Upload (ms) | The time it took to upload the specified file to the FTP server. |
| Download (ms) | The time it took to download the entire file from the FTP server. |
| 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. |
| Delete (ms) | The time it took to delete the specified file from the FTP server. |
| Download Throughput(KBps - Kilobytes per second) | Measures how efficiently the system was able to retrieve the file from the server. This is calculated as: Download File Size / Download (ms) |
| Download File Size | The size of the downloaded file. |
| Helo Time (ms) | The time it took to establish a connection with the SMTP server by sending a HELO command. |
| Authentication (ms) | The time it took to authenticate with the SMTP server. |
| Message Size (bytes) (SMTP) | The size of the SMTP message sent. |
| Initial Buffer (ms) | The time from making the initial request for the webpage until making the initial request to buffer. “Buffering” means downloading a certain amount of stream data before playing the stream. |
| Total Buffer (ms) | The total time spent buffering, including the initial buffering process and any additional buffers that occurred during the test. |
| Play (ms) | The time when the browser first displayed the stream content. |
| Buffer Count | The total number of buffers that occurred during the test. |
| Positive Offset (ms) | The estimated amount of time that the client clock is behind the server. |
| Negative Offset (ms) | The estimated amount of time that the client clock is ahead the server |
| Round Trip Delay (ms) | The total amount of time that the NTP request packet and response packet were traveling between the Node and the NTP server. |
| Root Delay (ms) | The estimated delay between the local system clock and the root clock. |
| Root Dispersion (ms) | The estimated error in the local system clock since it was last synchronized with the upstream clock. |
| Logout (ms) | The time it took to log out from the IMAP server. |
| Search (ms) | The time it took to search for messages. |
| List (ms) | The time it took to list folders. |
| Fetch (ms) | The time it took to fetch the message from the IMAP server. |
| Message Size (bytes) (IMAP) | The size of the message fetched from the IMAP server. |
| Publish Time (ms) | The time it took to publish the MQTT Message. |
| Publish Size (bytes) | The size of the MQTT Message published. |
| Subscribe Time (ms) | The time it took to retrieve the MQTT message. |
| Subscribe Size (bytes) | The size of the retrieved MQTT message in bytes. |
| Handshake (ms) | The time it took to complete the SSL handshake with the server. |
| Days To Expiration | The number of days remaining until the SSL Certificate will expire. |
Webpage | |
| DOM Load (ms) | The time it took to load the Document Object Model (DOM) for the webpage. |
| Content Load (ms) | The time it took to load the entire content of the webpage after the connection was established with the primary URL server. This is the time from the end of Send (ms) until the final element, or object, on the page was loaded. Content Load excludes DNS, Connect, SSL, and Send time. For Object monitor tests, this value is equivalent to Load (ms). |
| 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. |
| Test Response (ms) | The time from initial navigation to receiving the last byte of the final element on the page. For Web tests, the agent will wait for up to 2 seconds after Document Complete for no network activity to end the test. |
| Lighthouse Score | Google’s Lighthouse Score, which represents how well a webpage utilizes various performance-optimization techniques. |
| 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. |
| Wire Time (ms) | The total amount of time where at least one request was on the wire, from the start of the test or step to Document Complete. |
| Client Time (ms) | The total amount of time where no request was on wire, from the start of the test or step to Document Complete. |
| Render Start (ms) | The time from initial navigation until the first visual content is painted to the browser display. |
| Time to Title (ms) | The time from initial navigation until browser displayed the title of the page. |
| Webpage Throughput | Measures how efficiently the system downloaded the content of the entire webpage. Webpage Throughput is calculated as: (File Size + Header Size) / Webpage Response (ms). |
| # Connections | The total number of TCP connections established during the test. |
| # Hosts | The total number of unique external hosts referenced by elements on the page. |
| # Zones | The number of defined Zones containing hosts that were accessed during the test. |
| First Paint | The time when the browser first rendered anything visually different from what was on the screen prior to navigation. |
| 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.) |
| Time To Interactive | The time when the page first became interactive. TTI marks the point at which the webpage is both visually rendered and capable of reliably responding to user input. |
| 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. |
| Frames Per Second | Measures the performance of animations. |
| Interaction to Next Paint (ms) | This Web Vital metric measures the time from a user interaction (e.g. clicking a button) to the next frame being drawn. It is intended to measure the responsiveness of a web page after it has initially loaded, and this it is captured for RUM interactions only. |
| Largest Contentful Paint (ms) | The time when the largest image or text block (by screen area) visible within the viewport was rendered. |
| 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. |
| # Items (Total) | The total number of files included on the webpage. For Object monitor tests, this value is always one. |
| % Self Bottleneck | The percentage of Document Complete time that hosts in the "self" zone were a bottleneck for. |
| % Third Party Bottleneck | The percentage of Document Complete time that hosts in the "third party" zone were a bottleneck for. |
| Self Downloaded Bytes | Total file size in bytes (including headers) downloaded from hosts in the "self" zone. |
Requests | |
| # Redirect | Total number of redirects on the webpage. |
| # Html | Total number of HTML files downloaded during the test. |
| Html Bytes | Total size of HTML files downloaded during the test, in bytes. |
| Html (ms) | Total time spent loading HTML files, in milliseconds. |
| # Image | Total number of image files downloaded during the test. |
| Image Bytes | Total size of image files downloaded during the test, in bytes. |
| Image (ms) | Total time spent loading image files, in milliseconds. |
| # Script | Total number of JS files downloaded during the test. |
| Script Bytes | Total size of JS files downloaded during the test, in bytes. |
| Script (ms) | Total time spent loading JS files, in milliseconds. |
| # Css | Total number of CSS files downloaded during the test. |
| Css Bytes | Total size of CSS files downloaded during the test, in bytes. |
| Css (ms) | Total time spent loading CSS files, in milliseconds. |
| # Flash | Total number of Flash files downloaded during the test. |
| Flash Bytes | Total size of Flash files downloaded during the test, in bytes. |
| Flash (ms) | Total time spent loading Flash files, in milliseconds. |
| # Xml | Total number of XML files downloaded during the test. |
| Xml Bytes | Total size of XML files downloaded during the test, in bytes. |
| Xml (ms) | Total time spent loading XML files, in milliseconds. |
| # Media | Total number of media files downloaded during the test. |
| Media Bytes | Total size of media files downloaded during the test, in bytes. |
| Media (ms) | Total time spent loading media files, in milliseconds. |
| # Font | Total number of font files downloaded during the test. |
| Font Bytes | Total size of font files downloaded during the test, in bytes. |
| Font (ms) | Total time spent loading font files, in milliseconds. |
| # Other | Total count of all files not defined otherwise. |
| Other Bytes | Total size of all files not defined otherwise. |
| Other (ms) | Total time spent loading all files not defined otherwise. |
| # Sends | The total number of times the agent sent data to the server. |
| Send Data Bytes | The total size of data sent in bytes. |
| # Receives | The total number of times the agent received data from the server. |
| Receive Data Bytes | The total size of data received in bytes. |
Ping | |
| % Ping Packet Loss | The percentage of pings packets sent which did not receive a response. Calculated as: (# packets received / # packets sent) * 100 |
| Ping Round Trip (ms) | Average time between sending a ping packet and receiving a response. |
Availability | |
| % Availability | The percentage of test runs where the primary URL server was reached and the test was completed (i.e. there was not a Test Error.) Availability is calculated as: (# Test Runs - # Test Errors) / # Test Runs |
| % Downtime | The percentage of test runs where the primary URL server was unavailable, unreachable, or otherwise failed (i.e. there was a Test Error.) Downtime is calculated as: (# Test Errors) / # Test Runs |
| # Test Errors | The total number of test runs that failed. This is the sum of all of the following types of test failures: · # DNS Failures *· # Connection Failures *· # SSL Failures *· # Response Failures *· # Timeout Failures *· # Test Limit Errors |
| # Test Failures | The total number of elements that Catchpoint was unable to connect to, receive a response from, or load on the page. |
| % Content Availability | The percentage of time that all the elements on the webpage were available. Content Availability is calculated as the number of times the test ran successfully with no loading errors, divided by the total number of times the test ran. If at least one object failed to load during testing, that test run is regarded as having content that failed to load properly. |
| Test Time (ms) | One cohesive metric that applies to all test types and indicates the total duration of the test run. Test Time is equivalent to Response, Test Response (Transaction and Web tests) and Ping RTT (Trace Route tests), and is used when calculating Apdex. Test Time is not available for Request, Host, or Zone charting. |
| Apdex | A scoring mechanism that translates performance metrics of diverse applications into generic “User Satisfaction” levels using predefined response time thresholds. You can use default Apdex thresholds or configure your own on a per-test basis. For more details about Apdex, visit http://www.apdex.org/ |
| % Satisfied | The percentage of test runs that completed in less time than the Apdex “Satisfied” threshold. |
| % Tolerating | The percentage of test runs that exceeded the Apdex “Satisfied” threshold but completed in less time than the “Frustrated” threshold. |
| % Frustrated | The percentage of test runs that exceeded the Apdex “frustrated” threshold. |
| % Not Frustrated | The percentage of test runs that completed in less time than the Apdex “frustrated” threshold. This is equivalent to: % Satisfied + % Tolerating |
| # JS Errors per Page | The average number of JavaScript errors on each webpage. |
| # Content Load Errors | The total number of elements on the webpage that the test was unable to load or that generated errors during loading. |
| # Tests with JS Errors | The number of individual test runs that resulted in at least one JavaScript error. |
| # DNS Failures | The number of times the system was unable to resolve the domain from the primary URL to an IP address. |
| # Connection Failures | The number of times the system was unable to establish a TCP connection to the primary URL server. |
| # SSL Failures | The number of times a secure connection to the server for the primary URL could not be established. |
| # Response Failures | The number of times no response was received from the server for the primary URL. |
| # Timeout Failures | The number of times a test failed because a server process did not complete and it returned a timeout. |
| # Test Limit Errors | The number test runs that surpassed one of the following system boundaries: · Test takes longer than 30 seconds. · Test contains a URL that redirects more than 5 times in a row. · Test references more than 2,000 URLs. · Test references more than 255 different hosts. |
| # Runs | Total number of test runs for the defined time period. |
| % Adjusted Availability | Ignoring any purged runs, the percentage of test runs where the primary URL server was reached and the test was completed (i.e. there was not a Test Error.) |
| # Purged Runs | The number of test runs manually excluded from calculation for purposes of SLA accuracy. |
| % Step Content Availability | The percentage of individual steps for which all the elements on the webpage were available. Step Content Availability is calculated as the number of steps that ran successfully with no loading errors divided by the total number of steps. If at least one object failed to load during a step, that step is regarded as having content that failed to load properly. |
| # A | The number of DNS requests to #A servers |
| # AAAA | The number of DNS requests to #AAAA servers |
| # Cname | The number of DNS requests to #CName servers |
| # Ns | The number of DNS requests to #Ns servers |
Wifi | |
| Signal Quality | Measures the quality of the WLAN connection in terms of data transfer speed. It indicates what percent of the available network are you using to move data (upload / download). 99% is as good as it gets in terms of signal quality. |
| Signal Strength (dBm) | This number represents the power the clients device is receiving from the Access Point / Wi-Fi router. A number of -30 dBm indicates excellent while a number of -70dBm indicates very poor signal strength. |
Traceroute | |
| % Packet Loss | Note: Wi-Fi Signal Strength does effect Wi-Fi Signal Quality as the perceived available bandwidth will drop as Wi-Fi Signal Strength drops. |
| # ASs | The total number of Autonomous Systems traversed during the test |
| # Cities | The total number of Cities traversed during the test |
| # Countries | The total number of Countries traversed during the test |
| # Hops | The total number of Hops in the route. |
Insights | |
| Indicator | Custom metric; numerical value captured in header or response content |
| Tracepoint | Custom metric; string captured in header or response content |
Host/Zone | |
| Bottleneck Time | Time that the Host/requests of the Zone were the only requests occurring on the wire |
| % Bottleneck | What % of Document Complete for the page was the Host/Zone a bottleneck for |
RUM | |
| # BOUNCES | # of users who visit site and don’t navigate to other pages on site |
| # JS ERRORS PER PAGE | # of JavaScript errors per page |
| # PAGE VIEWS | Overall # of page views |
| # PAGES / VISIT | # of pages users viewed when visiting site |
| # REDIRECT | # of redirects on the root request. |
| # VISITS (UNIQUE) | # of unique visits (a visit ends after 30 minutes of no activity) |
| % BOUNCES | % of users who visit site and don’t navigate to other pages on site. [#Bounces / #Visits(Unique) * 100] |
| CONNECT (MS) | Time taken to establish a connection with the server for the root request. Does not include connect time for redirects. (not supported by IE9 and IE10 for sites with SSL) |
| CONTENT LOAD (MS) | The time it took to load the entire content of the webpage after connection was established with the server for the root request. |
| CONVERSION ITEMS | # of items sold |
| CONVERSION RATE | # of conversions over unique visits |
| CONVERSION SALES | # of sales |
| CONVERSIONS | # of conversions |
| DEAD CLICKS | User interactions on a webpage or app where the user clicks or taps an element, but no visible response or expected behavior occurs. |
| DNS (MS) | Time taken for the client to resolve the DNS for the root request. Does not include DNS time for redirects. |
| DOCUMENT COMPLETE (MS) | Time elapsed from sending the request to onload event |
| DOM INTERACTIVE (MS) | Time elapsed from request being issued to immediately before the user agent sets the current document readiness to "interactive". |
| DOM LOADED (MS) | The time it took to load the Document Object Model (DOM). |
| ENTRY TO ONLOAD(MS) | Time elapsed from initiating the request to onload event. |
| EXIT TO ENTRY (MS) | Time elapsed from unload event to starting the rendering of the content from the next page. This is similar to Response. |
| EXIT TO ONLOAD (MS) | Time elapsed from unload event to onload event of the next page. This is close to Document Complete time. |
| FIRST ENGAGEMENT TIME | The time it took between a user navigating to a page and the user first interacting with the page content. |
| FIRST INPUT DELAY | The time from when a user first interacts with the site (i.e. when they click a link, tap on a button, or use a custom, JavaScript-powered control) to the time when the browser responds to that interaction. |
| FIRST PAINT & FIRST CONTENTFUL PAINT | The point, immediately after navigation, when the browser renders the first bit of content. |
| FULL CONNECT (MS) | Time taken to establish a connection with the server for the root request including SSL. Does not include connect time for redirects. |
| INSIGHT INDICATORS | The list of indicators and available values associated |
| INTERACTION TO NEXT PAINT | Assesses the time it takes for a browser to respond to a user interaction (like clicking, tapping, or pressing a key) and visually update the page in response. |
| LOAD (MS) | Time elapsed between loading the first byte to the last byte of the root request. Does not include load time for redirects. |
| RAGE CLICKS | The multiple rapid clicks on the same area of a webpage or app within a short period, indicating user frustration with unresponsive or confusing elements. |
| RESPONSE (MS) | Time elapsed from the request being issued to the server responding with the last byte for the root request. Includes response time for redirects. |
| SSL (MS) | Time taken to establish the SSL handshake with the primary URL. (not available for IE9 and IE10 for sites with SSL) |
| THRASHED CURSOR | A user behavior pattern where the mouse is moved rapidly and erratically across the screen, often signaling frustration or confusion. |
| TIME ON PAGE | The total time the page remains in focus in the user’s browser or app window during a session. |
| TIME TO INTERACTIVE | Time it takes for a page to become interactive |
| TOTAL ENGAGEMENT TIME | The total time the user was interacting with the page content. |
| VISUALLY COMPLETE (MS) | Time taken for the content in the viewport to appear complete to an end user. Calculated by listening to viewport elements until the timestamp difference between two elements loading is greater than 500 ms. Any mouse events that happen stop Catchpoint from listening to mutations. When the Mutation Observer API is not available in the browser, we use resource load times to calculate. |
| WAIT (MS) | Time elapsed from sending the request to receiving the first byte of response from the root request. Does not include wait time for redirects. |
Catchpoint Metrics
- 17 minute(s) read
Was this article helpful?