Analytics – Working With Left Menu (NetVision)

This section contains analytics on Real User Monitoring (RUM) and Form. RUM reports consist of page performance reports based on various parameters, such as channels, user segments, device type, location, and so on.

Real User Monitoring (RUM)

RUM reports are basically the page performance reports on various factors, such as channel, user segment, device type, location, page ID, operating system, and so on. A user can include/exclude the filters based on the requirements. User can generate reports for the last provided time or the specified time. There are two sub-sections within this section – Page Performance Overview and Page Performance Details.

Page Performance Overview

This feature provides user a brief overview of all the pages of an application. Here, user can view the page count, timing data, and exit rate of all the pages of an application.

To view page performance overview, click the Page Performance Overview link. A filter section is displayed at the top. Based on the filter values, user can view the page performance overview.

There are following filters:

  • Time: This contains filters, such as last duration (such as 15 minutes, 1 hour, 1 week, 1 day, 1 week, and so on) and specified time (date and time range).
  • Page: It is the entry page from where the session is accessed.
  • Channel: It is the channel from where the site is accessed, such as Dotcom, mobile, POSF, or all.
  • User Segment: It is a group of users having some common behavior or attributes.
  • Device: It denotes the device, such as PC, mobile, tablet on which the session is accessed.
  • Operating System: It denotes the operating system used for accessing the site.
  • Browser: It denotes the browser used while accessing the site.
  • Advanced Filters: This contains some advance level filters to include/exclude in the results.

After applying filters, click the Done button. The Page performance overview is displayed in tabular and graphical format. The information is categorized in various tabs, such as Page, Device, Browser, Browser (versions), Connection, Location, Region, Operating System, OS (versions), and Browser & OS. By default, the Page tab is displayed.

Page Performance Overview – Tabular Format

The tabular format displays information around pages, such list of page name, page count, onLoad time, Time to DOM interactive (TTDI), Time to DOM load (TTDL), Server Response Time, Perceived Render Time (PRT), First Byte Time, DNS lookup time, Secure connection time, Cache lookup time, main URL download time, connection time, and exit rate.

Page Performance Overview – Graphical Format

This displays page performance information, such as Onload time, DOM interactive time, time to DOM content download, and other information in graphical format. On the Y-axis, there are pages, and on the X-axis, value is define in seconds.

In the same manner, information about other tabs, such as Device, Browser, and rest is displayed.



Browser Version(s)




OS (versions)

Browser & OS

Export in CSV

User can download the tabular view of the information in csv format by clicking the Export button.

Print/Download Graphical View

User can print the graphical view format of the information and can download it in various formats, such as PNG, JPEG, PDF, or SVG vector image.

Page Performance Details

This section displays the detailed view of the page performance. User can drill to any session causing spike in the dashboard from a single page. User can also find the root cause for that spike using page performance details as it enables us to view all the details of the sessions. To access this, click the  icon at the top-left corner, go to Rum Analytics section and click the Page Performance Detail link.

A window displays with various sections:

  • Page Performance

This section displays information of various aspects:

    • Avg OnLoad: Onload time is the total time consumed in the processing of page and loading all the resources (images, CSS, etc.). This is the same time when DOM complete occurs and the JavaScript window.onload event fires.
    • Avg DOM Time: DOM time is total time spent in processing DOM and rendering the page. It is time from main URL (last non-redirect) response received to window.onload event.
    • Avg TTDI: DOM interactive time is the point at which the browser has finished loading and parsing HTML, and the DOM (Document Object Model) has been built. The DOM is how the browser internally structures the HTML so that it can render it.
    • Avg TTDL: DOM content loaded time (DOM loaded or DOM ready for short) is the point at which the DOM is ready (i.e. DOM interactive) and there are no stylesheets blocking JavaScript execution. If there are no stylesheets blocking JavaScript execution and there is no parser blocking JavaScript, then this will be the same as DOM interactive time.
    • Avg First Byte: Time to First Byte (TTFB) is the total amount of time spent to receive the first byte of the response once it has been requested. It is the sum of “Redirect duration”, “Connection duration”, and “Backend duration”. This metric is one of the key indicators of web performance.
    • Avg Unload: Time spent in unloading the previous document (if any).
    • Avg Redirect: It is the time taken by browser to fetch all redirect URLs, if there is any redirection in fetching the main URL.
    • Avg CacheLookUp: It is the time taken by browser to look up the main URL in browser cache.
    • Avg DNS: It is the average time required to resolve a host name.
    • Avg TCP: It is the average time required for TCP handshake. It does not include SSL/TLS negotiation.
    • Avg SSL: Time required for SSL/TLS negotiation.
    • Main URL Wait time: Server response time is wait time of main URL. It is time from main URL request (last non-redirect) start to time when first byte of response is received.
    • Main URL Download time: Total time taken in downloading the main URL (last non-redirect) response.
  • Performance Detail: From​ ​Performance​ ​details​ ​dashboard, user​ ​can​ ​find​ ​the peak. Here, Yellow line shows the peak. Hover on it to get the overall details at that particular time.

  • Page Performance Trend: This displays Page detail in tabular form with all parameters.

  • Domains by Duration: This displays all the domains with their duration. User can identify which domain is taking the maximum time.

  • Domains by Request Count: This displays the domains by request count.

  • Domain Aggregate: This is the tabular representation of the domain by request count.

Clicking the Domain Trend  button  enables the user to view the domain timing over time.

User can apply time filters and can download this chart too.

  • Resource Performance: Resource performance table provides​ ​an​ ​aggregate​ ​view of  ​the ​resource ​timing​ across all domains.​ ​This​ ​helps​ ​in​ ​identifying​ ​the​ ​page​ ​bottlenecks.

User can view the domain trend in graphical format by clicking the  icon. Now, user can analyze the resource trend to check why the duration time is high for this Domain.

User can view the resource trend in graphical format by clicking the  icon. Here, user can see highest duration for this particular resource (/tag) due to which corresponding domain took high time.

  • Content Type Distribution: This section displays content type distribution, such as images, scripts, documents, stylesheets, and so on.

  • Page Drill Down: This section displays page scatter map with various attributes and filters. User can select parameters, such as onload, TTDL, TTDI, DOM time, and so on. Based on the selection, user can also select the maximum time and bucket size.


Pages with resource timings are denoted with blue dots and pages without resource timings are denoted with black dots.

To view the details of any instance, mouse hover to it. A pop-up is displayed with details.

To open a session from this dialog box, click the “Click top open session” link. Session with that page is displayed.

Now, from resource timings tab, user can identify which file is taking more time to load.


This section displays the form analytics report where the user can see total number of views on each page along with various stats on the form, such as form name, total form interactions, total successful submits, total failed submits, and conversion rate.

On clicking a form name, the form analytics report is displayed with the following details:

  • Overall Report: This displays the overall summary of user actions on a form, such as name of form, how many successful submits, number of page views, number of interactions, number of submits, number of drop off from page, and from field, and number of failed submits.

  • Conversion Report: In Conversion Report, the user can review the step-by-step conversion analysis to see the user interaction with the form of the webpage.

  • Time Report: This report explains average time taken by a user to fill that field and average duration to fill the form completely. This report contains two sections – form summary and field wise report.

  • Hesitation Report: It is similar to Time report. Instead of fill time, it represents hesitation time for each field.

  • Refill Report: This report explains how frequently a visitor refill form fields to resubmit the form. This report contains two sections – form summary and field wise report.

  • Drop Report: This report explains from which field user is abandoning the form and moving to next page. It also contains two sections – form summary and field wise report.

  • Blank Report: This report explains how frequently a user is leaving a field blank. It is similar to a drop report. It contains two sections – form summary and field wise report.


This helps in understanding the correlation between page performance and revenue. It helps in predicting the Revenue gain by improving the page performance.

To access the Revenue Analytics section, click the  icon on the NVSPA window.

Now select Revenue Analytics from the following section:

This displays the Revenue Analytics window:

This window displays Page performance Vs Revenue that contains Page views /sessions / Order total / order count/ Conversion Rate  Vs  Onload time.

Estimate the Event impact on revenues

You can also analyze the impact of an event on the revenues by using the Impact of Event option. This option displays the Even Impact Card window that enables you to perform the impact analysis of events by providing information such as the estimated revenue loss and conversion rate.

To estimate the impact of an event on the revenues:

  1. Click the icon in the Events column. The event options are displayed:

2. Select the Impact of Event The Event Impact Card window is displayed:

3. Click the Filter icon to specify the time filter details:

4. Click Done in the Time Filter window. You can analyze the impact of the event on your revenues.

Navigation Summary and User Flow Report

Navigation path analysis is all about analyzing different user flow in a website. Every navigation path is a series of web pages that define a visitor or task. It includes the steps that a user performs to complete the task, during a website visit or other UX process. The “top path” is the most common navigation path. It is the series of pages seen by your typical visitor.

Every site has these common or popular navigation paths. Path analysis can help understand the deviation in navigation from expected navigation to the actual navigation that’s happening with in the website.

This second path clearly shows that user is facing some issues on shipping page from where deviation from the expected popular path is happening resulting in zero conversion through this path.

You might also discover something like an unusually high drop-off from a new page you’ve introduced, like a new home page or new product page. Investigate whether the design of the new page might be obscuring the links or controls that lets traffic flow to the pages you want them to see next.

In order to identify these navigation paths, related issues and further analyse it path analytics reports can be used. Following are the reports which visualizes in details and provides information about each navigation path.

  • View Flow Report
  • Navigation Flow Report

These components belong to Path Analytics, which helps in understanding the flow of users (traffic) on an application. Pages, which have high exit rate, can be easily identified as well as it is easy to spot most taken path or least taken path.

To access the Path Analytics section, go to Analytics > Navigation Summary or click the  icon on the NVSPA window.

This section contains links to View flow report and Navigation flow report.

View Flow Report

Visualize traffic on the website with different dimensions, as the entry point, such as OS, Browser, Location, Device type, Referral. The capabilities of View path are:

  • Identify most preferred flow and least preferred flow, also identify most converted flow and least converted flow. Improve the exit rate from such flow and increase the conversion rate.
  • Multilevel drilldown to understand the flow in more details.

Click any Node for further drilldown. Path associated to that node is highlighted. In above example, highlighted flow for Windows OS and Welcome page as entry page.

View Flow Report – Filters

There are following filters:

  • Time
  • Channel
  • User Segment
  • Dimension – OS, Browser, Location, Device Type, Referrer.

Navigation Flow

Navigation flow helps to visualize how users are interacting to a particular page. The following outcomes can be anticipated with the Help of navigation Flow, how:

  • Users are coming to a particular page
  • Users are proceeding further from that page
  • % of users exiting from that page

Navigation Flow- Filters

There are following filters:

  • Time
  • Channel
  • User Segment
  • Dimensions – OS, Browser, Location, Device Type, Referral.