The Transaction Overview page enables you to compare transaction duration and transaction throughput under various network conditions.
Baseline—the minimum amount of time to run the transaction without a virtual location
Network impact—the time it took to run the transaction with and without
analyze transactions based on duration and throughput
examine the impact of different network conditions across all transactions in your test
drill down to a specific transaction to view analysis results and get recommendations on how to improve your application's performance
View transaction details
|Duration||The total time in seconds it took to run the transaction.|
A graphical representation of the difference between the time it took to run the transaction with and without
For more details, see See the network impact.
The total amount of data transferred during the transaction.
Upload traffic. Total throughput for data traveling from the client to the server.
Download traffic. Total throughput for data traveling from the server to the client.
|Go To Transaction Analysis||
Drill down for more details
To drill down to view recommendations on how to improve your application's performance and analysis results for a specific transaction run:
For details about the analysis results pages, see
Transaction status shows the total number of transactions that did not run (were skipped).
A skipped transaction is a transaction that ran successfully (regardless of the pass/fail status) on at least one network, but did not run on at least one other network. For example, a transaction may have run successfully both without network emulation and over 4G, but did not run over 3G, for some reason.
Review the sidebar to assess overall network impact on each transaction. Network Impact shows the effect of the network conditions on transaction duration.
Baseline selection control
Lets you select a network scenario to use as the baseline scenario.
The transaction durations in the baseline scenario are shown in all transaction duration graphs on the page. (The actual value that is used as a baseline is different for each transaction, and the network impact is recalculated accordingly.)
Network Impact donut
Hover over or click a piece of the donut to see the number of transaction runs in the range, and how the transactions compare to the baseline. The associated transaction runs are highlighted on the page.
Is your application optimized?
Check the Optimization Grades to quickly identify weak spots in your application's compliance to best practices. An optimization grade is a letter indicating the level of compliance with the best practices. A represents the highest level of compliance, and F represents the lowest level of compliance.
When you hover over or click an optimization grade bar. The associated transaction-scenario runs are highlighted on the page.
Click the mode toggle to switch between displaying information for desktop browsers or for mobile devices.
For more details, see Optimization Recommendations.
Change the view settings
Use Group by to group the data in the graphs by transaction or by network scenario.
The bar charts display transaction time (top row) and throughput (bottom row), under various network conditions. Each bar in a graph represents a single test for a specific transaction-scenario combination.
- Hover over the bar of any transaction to view more details about the transaction in a popup.
- Click a bar of any transaction to drill down to view more details about the transaction.
Use the Group by control to group the data in the graphs either by transaction or by network scenario.
|Transaction duration (sec)||
The time (in seconds) that it took to run the transaction under each set of network conditions.
The horizontal line that crosses each group represents the transaction duration for the baseline scenario for that transaction. (The actual value that is used as a baseline is different for each transaction.)
Use the controls in the sidebar of the report to select the baseline scenario.
Each color represents a different network scenario or transaction, depending on the view. The graph enables you to compare duration times for an individual transaction run under different network scenarios.
|Total throughput per transaction (KB)||
The total amount of data (in KB) transferred during the transaction, under each set of network conditions.
The throughput traffic can be up, down, or both.
The Grid View enables you to see a more detailed view of the transactions.
Each row in the list represents a run of the test for a specific transaction-scenario combination.
Click any transaction (row) in any list to drill down and display pages that show more details about the transaction.
Use the Group by control to group the data in the lists either by transaction or by network scenario.
|Network / Transaction||
Depending which view you selected, displays one of the following:
|Duration||The total time in seconds between the transaction start and end.|
|Network Time||The total time in seconds between the start of network activity and the end of network activity.|
The fastest iteration for each transaction when run without a
Hover over a baseline value to see the actual baseline for that specific transaction/
The total amount of data in kilobytes transferred during the transaction.
Upload Bandwidth. Total throughput for data traveling from the client to the server.
Download Bandwidth. Total throughput for data traveling from the server to the client.
A letter indicating the level of compliance with the best practice rules for programming websites, with A representing the highest level of compliance, and F representing the lowest level of compliance. For more details, see Optimization Recommendations.
Filter the display
Filter the displayed data by clicking the Filter button . You can:
Search for what you want to filter.
- Press Enter to apply the filter.
Clear parts of the filter or the entire filter by clicking Clear, Clear All in the open filter, or by clicking the green X on the Filter button.
The header displays the name of the test from which the NV Insights Report was generated.
When you drill down into the report, the name of the specific transaction-network scenario combination appears in the header. You can click the down arrow to select a different network scenario or transaction (according to what is currently displayed).
Test summary information:
The value for Runs indicates the total number of transactions that ran in the test multiplied by the total number of network scenarios.
- In Chart view, Runs = the total number of bars.
- In Grid view, Runs = the total number of rows.