YOTTAA Product Updates: April 2021
With the demand for faster eCommerce sites and great online shopping experiences at an all-time high, we understand the importance for us to simultaneously provide the leading eCommerce acceleration solution in the industry. To accomplish this, our solution experts are constantly finding new and innovative ways to make our leading products stronger, better, and faster.
Check out the latest product enhancements released this month:
Violations and JavaScript Errors Dashboard
Troubleshooting your eCommerce site has never been easier. Users can now review page delay, performance, and size violations, as well as JavaScript errors by key dimensions and trending over time, all in one place. Users can also drill down even further into page resource level, or see the most recent violations in the Diagnostics section of the dashboard.
Updates to Core Web Vitals: Diagnostics
With a leading edge on helping brands measure Core Web Vitals and other key page load time metrics, YOTTAA’s Diagnostics can help troubleshoot issues across metrics. Diagnostics provide the ability to identify problem areas and drill into Core Web Vitals and other performance metrics from the page category level down to individual pages and resources. The Diagnostics feature was built with flexibility in mind to streamline the workflow for site developers and help pinpoint issues causing slowdowns across various metrics. Stay tuned for more enhancements coming soon!
Split Origin Support
As eCommerce brands continue to replatform, A/B test, or adopt different routing strategies, testing the traffic being routed to different platforms or origins becomes vital to ensure a smooth shopper experience during peak traffic times.
YOTTAA’s traffic processing system uses criteria-based matching for routing traffic to the origin based on the original request. For example, all /blog requests can go to blog.something.com or new.blog.something.com. Therefore, if the request is sent to new.blog.something.com, then the request will stick to that origin. This process can now be configured to control your origin choice based on a previously chosen origin in the https:// session or to a matching criterion.
Optimizations can also now be conditionally applied based on other optimizations used in the current request. For example, Geographic location can be used as a criterion for choosing an origin server for routing (e.g., traffic from Massachusetts can be routed to origin.mass.com while all other traffic is routed to salesforce.mass.com)
The origin server itself can be used as a matching criterion for optimizations, allowing origin servers with different content to be optimized separately. (i.e., in A/B testing)
The feature is available to use with the help of our support team. The UI support for this functionality will be out soon.