Tracking Site Speed in Adobe Analytics — The Quick Way

Tracking Site Speed in Adobe Analytics — The Quick Way

There are more than enough ways to set site speed tracking on your web property. I’m going to share a quick and easy way to implement this to get broadly accurate data to support your analysis and user experience.

Install the plug-in

  • Go to the Extensions tab of your property
  • Install and Publish the Common Analytics Plugins extension.
  • Once published, create a rule to load the library with the following configuration:
  • Event: Library Loaded (Page Top)
  • Condition: None
  • Add an action to the newly created rule:
  • Extension: Common Analytics Plugin
  • Action Type: Initialize getPageLoadTime
  • Save to the library and publish the rule

If you are more tech savvy then you can explore couple of more options described here:

Setting up events

Before you can use any success events in your reports, you would need to set them up in the Admin section of Adobe Launch.

Using the plug-in

The getPageLoadTime method sets s._pltLoadTime which captures the time in seconds that the previous page took to load. If you do not already have an eVar for Previous Page then the same method also sets s._pltPreviousPage so you can reference both of the values together in your reports.

Now on to how to make use of this.

Where you apply depends on your requirements. No one wants multiple server calls — especially in this case. So if you already have an existing rule which is triggered on page load then add the following custom code block into the Actions. I set these on a rule with an event of Onload (window load).

If you already have existing calls which you do not want to touch with the same rule then you can always use Adobe’s plug-in called apl (appendToList) which allows you to safely add new values to list-delimited variables, such as events, linkTrackVars, list, and others.

Your success events would look something like this in that case:

This will set event105, which would be a custom numeric event (which we created/set earlier), equal to the load time of the previous page. Using a custom event in this case would allow you to get the total amount of time for all page loads of the previous page (from all visitors/visits).

You would need create a calculated metric to get the average page load time for each page which should look something like this:

Read more

Some really great and helpful resources: