Configuration Workflow: Performance Rules

We recommend that you start with a basic initial setup, monitor performance, and then adjust or add rules as needed. Your final configuration will depend on your individual site's performance.

Workflow - Creating Rules

Every time you create a new rule or set of rules, test for quality assurance before making the changes live on your production site, following this workflow: 

  1. Set your site status to bypass.
  2. Create rules.
  3. Validation test using our quality assurance checklist or your own.
  4. Set your site status to live.

Workflow - Refining Performance Rules

After you create the initial rule set, wait at least 24 hours for the data to populate. Then use the homepage and dashboards to monitor how Yottaa is improving your site. If site performance is still not at the level you want, investigate which services are having the biggest impact on performance. You can do this on the Performance Inventory or Service Flow page:

  • On the Performance Inventory page, by default, the service causing the highest number of page delay violations appears at the top of the list. These violations indicate that the service is impacting site performance.
  • On the Service Flow page, click the Impact column heading twice to sort the list by the number of milliseconds that each service delays page loading. Click the arrow to the left of the third party name to look at details, including the most viewed pages where the third party is running and the potential impact of delaying the third party.

Once you identify the third parties causing problems, investigate why the third party is having an impact. For example, the spread rule might not be capturing the third party, or the third party might be having an impact on page load times despite being delayed until after onload. You can address some of these issues in your site's source code. Others you can fix through creating additional rules.

Here is a list of common reasons why a third party may still be causing delays, even if it is captured by the spread rule: 


Potential Solution

The third party executes in the body of the HTML document, rather than the head.

Add the third party to the head section, or insert Yottaa's API into the body using the following code:

Copy Yo.sequence.node(document.body);

The third party is loaded through a development package manager.

Remove the third party from the package manager, and load it with a tag manager or with Yottaa.

A tag manager is causing the third party to be synchronously loaded.

Change the tag manager to load asynchronously

The third party loads after onload, but is still slowing down your site.

Create a sequencing rule to defer the third party for several seconds. If the third party appears below the fold, you can also set it to lazy load.

The third party is source-injected.

Contact support to validate your script before changing any source-injected third parties on your production site.

Use the following code, replacing "" with the source-injected third party's URL: 

<script type="yo/sequence/defer/0" data-yo-src=""> </script>

After a few days, check the homepage and dashboards again. If performance is still not where you want it to be, repeat the process of investigating and sequencing until your site speed and performance are optimized to your satisfaction.