Today we are releasing Snapshot History Graphs, a new feature that allows you to see how critical KPIs such as defects, performance score, and content size are changing over time. This insight is essential when updating or rolling out new versions of your site, because it enables you to see if performance is getting better or getting worse over the course of a development cycle, and from release to release. Specifically, Rigor Optimization allows you to track two broad categories: performance defects and content sizes. In this post, we will use real world examples to see how tracking both can reveal the source of performance slow downs.
Performance problems often trace back to specific defects, like not caching your content or resources that are blocking the rendering path for a page. Our new Snapshot History Graphs provide several ways to visualize your performance problems and how they change over time. Let’s use a real life example of how one of our customers used these snapshot history graphs to track down the source of a performance problem. It all started when the customer noticed a small dip in their overall performance score.
To investigate further, they switched over to the Defects by Severity view:
Here we can see the performance defects, broken out by severity, as they change over time. We see an increase in the number of medium severity defects. This means that a number of new performance defects were introduced, leading to the lower score. Rigor Optimization allows you to view differences between snapshots. By clicking a snapshot, and then on our comparison view, the customer could see the specific performance problems that were added to the site.
As is often the case, these performance problems came from a bad ad. Rigor Optimization enabled our customer to drill in on the exact bad ad, and provided details to allow our customer to escalate the issue to their ad operations team and get the issue resolved.
Beyond looking for specific performance problems, organizations often want to track how the content on their site changes over time. This is especially helpful to enforce performance budgets. It also helps detect when a large amount of content is added, even if that content is well optimized. Let’s use another example to see how Snapshot History Graphs can help surface problems with content.
Here, I can see the Total Content Size for a page, trended over time, for both first-party content and third-party content (3PC).
Wow! Looks like a huge spike of 3PC was introduced on February 10th. To get more data, we switch over to the Content By Type view and filter to only show 3PC.
Turns out the page is now loading a 6.6 MB document from Google Sheets! Digging further our customer determined that someone in marketing had added a new chart to the page, which pulled in the entire Google Sheet! The customer was able to find and address this, all because of our new Snapshot History Graphs.
Rigor: Powered by Customers
Snapshot History Graphs were the direct result of feedback we got from our customers.
Are you a Rigor user? Do you have ideas on ways we can improve the product? We want to hear from you! There are 2 ways to reach out:
- Book a call. Use this super fast and easy Calendar link to schedule a time that works for you to speak directly with Rigor Product Management. Tell us what you like and what we can do better. While we’re on the call we’ll share a sneak peak of some of the new features we’re working on now.
- Post on our Rigor Idea Exchange. See what other users are asking for, vote up suggestions, and share your own requests. When Rigor Engineering picks up a feature for development from the Idea Exchange, everyone who submitted or voted on a suggestion will get an email notification, so this is a great way to stay on top of the development progress of the features that matter most to you.
Do you care about performance optimizations?