Web Performance Report feature allows user to compare RBU and Light House average data in a single UI. It consists of two reports:

1. Web Vital Average Report
2. Page Average Report

### Web Vital Report

The Web Vital Average report provides information about the performance of your web site by collecting real world usage data. Using the Web Vital Average metrics, you can optimize the user experience, measure the loading performance, interactivity, and visual stability of your web site.

The following metrics are tracked in the Web Vital Average report:

- Page name: Displays the page name that is being analyzed.
- Group: Specifies the group name that has been used in the scenario.
- Session Count: The Session count field provides a record of the number of times a user visits your website within a given time frame.
- First Meaningful Paint (FMP): The First Meaningful Paint (FMP) field provides information about the user interactivity on a web page. The FMP value should be 100 milliseconds or less.
- Time to Interact: Time to interact is the point when a user can interact with a web page element once the page has been rendered. After a shopper clicks on the add-to-cart button, for example, TTI measures the time it takes for the interactive element on the next page to become usable, such as the checkout button.
- Speed Index: The Speed Index field measures the visual completeness of a web page. It enables you to analyze whether the visual content is loading on the screen quickly or not.
- Total Blocking Time: The Total Blocking Time field measures the load responsiveness of a page. It calculates the amount of time taken by a page to become responsive to a user input.
- Largest Contentful Paint (LCP): The Largest Contentful Paint (LCP) field provides information about the loading performance of a web page. It measures the time taken by a web page to display the largest amount of content on the screen.
- Cumulative Layout Shift (CLS): The Cumulative Layout Shift (CLS) field provides information about the visual stability of a web page. The CLS value of pages should 0.1. or less.

### Page Average Report

Using the Page Average Report, you can analyze the details of a user session, such as the average page detail, session details, DOM content and page loading time, number of user requests, and page loading time.

The following metrics are tracked in the Page Detail Average report:

- Action: Clicking the information icon in the Action field provides additional information about the selected page.
- Page name: Displays the page name that is being analyzed.
- Host name: Shows the hostname of the URL.
- Group: Specifies the group name that has been used in the scenario.
- Browser: Shows the name of the browser, such as Chrome or Mozilla Firefox, in which the RBU test is run. You can select the browser as per your needs from the RBU settings of the scenario.
- Screen Size:Provides the screen size, such as 1920 x 1080. You can also configure the screen size as per your requirements in the User Profile settings of the scenario.
- Session count: Displays the number of sessions that have analyzed this page.
- DOM content load time(sec):Time taken to load the HTML structure of the document. It does not include the time to download the images, CSS files, JS files, iFrames, and other third-party scripts like Adsense, Analytics, etc.
- Onload time(sec): On load time is the amount of time it takes for a web page to fully load. It is calculated from the moment you click on a link or type in a website’s address to the moment when all the elements of the page are displayed on the screen.
- Page load(sec): Displays how much time it takes for the browser to parse and execute the document and render the page to make it available for user interaction. The default page load time is 4 seconds. For calculating the page load time, you can configure the URL time gap in the RBU settings of the scenario.
- Time to interact(sec): TTI refers to the time taken by a webpage to become interactive for the user. It measures the time from when the page starts loading to the point where the user can actively interact with the page, such as by clicking on links, buttons, or input fields.
- Start Render Time(sec): The initial instant that something appears on the user's screen is known as the start render time. The web page goes from a blank white screen to one that changes. It doesn’t necessarily have to be content, it can be a logo or text, it could be a colored background, or a search box.
- Visually Complete Time(sec):Specifies the time from the start of the first request to the time when the page is completely rendered. A point-in-time metric measures when the visual area of a page has finished loading. In RBU, this is calculated by capturing a clip of the page loading in the browser and comparing the size of each clip.
- Requests: Shows the total number of requests excluding the browser cache-type request. This is equivalent to the sum of all resource type counts. For example, if a page has one HTML file, one CSS file, and three images, the request count would be five.
- Browser cache: The browser cache refers to the number of HTTP requests that are served from the browser's cache rather than being sent to the server.
- Bytes received(kb):The total size of response data in bytes that is downloaded/received when a web page or its resources (such as HTML, CSS, JavaScript files, images, etc.) are retrieved from a server. It includes the size of the response headers, the HTML content, and any additional resources requested by the page, such as images, scripts, stylesheets, and other media files.
- Bytes sent(kb): The total size of request data in bytes that is uploaded/sent when a user interacts with a web page or submits data to a server. This can include sending form submissions, making API requests, uploading files, or any other data that needs to be transmitted from the client to the server.
- First Paint(sec): First Paint measures the time taken by the first pixel of content to be rendered on the screen of a web page. It represents the initial visual response of the page and indicates when the user first sees something meaningful displayed in their browser.
- First Contentful Paint(sec): First Contentful Paint measures the time taken by the first meaningful content to be rendered on the screen of a web page. First contentful paint occurs when a browser first renders any content from the document object model (DOM). It typically includes the rendering of text, images, or other significant elements that are part of the page's main content.
- Largest Contentful Paint(sec):"Largest Contentful Paint measures the render time of the largest and most significant content element on a web page.The largest contentful paint element is typically a large image, a video, or a block-level text element that carries the most visual weight on the page. Elements outside of the viewport and background images are not included. ."
- Cumulative Layout Shift: Measures the visual stability of a web page as it loads and becomes interactive. It is based on the amount of movement of elements on the page during the loading process.
- Total Blocking time(sec): Time for which a page is blocked from responding to user input, such as mouse clicks, screen taps, or keyboard presses. The sum is calculated by adding the blocking portion of all long tasks between First Contentful Paint and Time to Interactive.
- Speed index: Speed Index shows how quickly the content of a page is loaded and visible to the user. It measures the time taken by a web page to visually appear on the screen and become usable.
- Request before onload: Request Before On Load refers to the HTTP requests made by a web page before the onload event is triggered. When a web page is loaded, various resources are typically requested from the server to render and display the content properly. These resources can include HTML files, CSS files, JavaScript files, images, fonts, and more. The onload event indicates that all these resources have been fetched and processed, and the page is ready for interaction.
- Backend Response time: The amount of time taken by the server to process a client's request and generate a response. When a user interacts with a web page, such as submitting a form, clicking a button, or requesting data, the client-side code sends a request to the server. The server processes the request, executes any necessary operations or computations, and generates a response. The backend response time measures the duration of this process, from the moment the server receives the request to when it completes generating the response.
- DOM Element: Refers to the total number of individual elements present in the Document Object Model (DOM) of an HTML document. The DOM element count represents the number of HTML tags and their corresponding elements that make up the structure of a web page. It includes elements such as <div>, <p>, <span>, <img>, <a>, <input>, and many others.
- Request before DOM Content: The number of HTTP requests made by the web page before the DOM (Document Object Model) content is fully loaded and parsed. The DOM content refers to the HTML structure of the web page, including its elements and their relationships. It represents the parsed and organized representation of the HTML document.These requests could include fetching the initial HTML, critical CSS needed for rendering, JavaScript files necessary for functionality, and other resources.
- Bytes Received before Dom Content: The total size of response data in bytes that is downloaded/received before the Document Object Model (DOM) content of a web page is fully loaded and parsed.
- Bytes Received Before On load: Refers to the total size of response data in bytes that is downloaded/received before the onload event is invoked on a web page.