Rapid CTRL compiles all data gathered by the Yottaa script, breaking it down and displaying the data. This data can be used to identify optimization opportunities, problematic scripts, and provides suggestions how to correct potential issues.
Catalog – Rapid JS will automatically pull all Third Party data from your site and bucket the tool based on categories defined by type and purpose of third party.
Page Categories – Rapid allows for breaking down the Catalog section by page type. By compartmentalizing the third party data you are able to get narrow view catered to the different stages of customer engagement.
Export – Transfer the third party information from the portal to a CSV for your convenience. You can then manipulate the data in your favorite spreadsheet editor.
Sort By filter – Configure the data table using the filters. You can sort the data by colums (ie. Third Party, Date Discovered, Category, etc).
Note: Violations are a concept introduced by Yottaa and are available throughout the portal, even as a column to filter by. Violations use the Real-user data to identify third parties that either impact a visitor’s experience, or a potential performance risk.
Violations are measured in the amount of issues caused by that specific third party within 1000 requests. By clicking the details dropdown you’ll display each type of violation and count per 1000 requests.
The trend line graph provides different industry standard metrics for measuring performance. This data is not sampled, but direct results from user sessions.
Page Load – There are four page load measures you can filter this data on.
Onload – Default: Time taken for the page and all assets to have been completely loaded in the DOM.
Complete – The point when all static content has loaded. The DOMContentLoad is complete and all sub-resources have finished loading.
Content Loaded – Displays timing of when the initial HTML is loaded and parsed without waiting for stylesheets, images, and subframes to finish loading.
Interactive – The page has loaded enough content for the user to move around on the page without anything preventing or resetting those movements.
After selecting the page load type you can break the data down by Optimization State, Device Type, browser, and page category.
Violations are designed to classify or bucket any 3rd party that currently or can potentially impact the load time of a website. We separate violations by immediate issues, known as Visitor Impacting, and potential risks.
Visitor Impacting – These all manifest in real browsers with real users.
Delays page load – When a 3rd party takes too long to load and delays rendering of the page. Default is 750ms.
Load Failure – When a 3rd party fails to load. Can happen for a few different reasons, but most commonly due to ad blockers or other security plug-ins.
JS errors – When 3rd party executes incorrectly within the browser. Simply a bug in the code.
Potential Risk to Business – These don’t currently impact user experience, but are indicative of potential issues.
Performance Risk – 3rd party takes a long time to load, but takes place after the “on load” event. Since if loads late in the page the impact is not perceived. However the impact may be to site engagement since some of these types of scripts may be related to value-added services to the visitor (customer service or chat).
Size – When a 3rd party is large in size can signal a future performance issue. The default is 1MB.
Page Views - The amount of requests resulting in a page load in the given timeframe