Tag Load Time Report

Long tag load times contribute to high premature exit rates. Long-loading tags may degrade the quality of the user experience by preventing other content from displaying until they load.

The top level of the report shows the average load time, sorted descending from the longest to shortest in milliseconds. Click on the name of the tag to see an additional breakdown of load times for that tag.

The tag load detail shows the number of URLs grouped by millisecond ranges. The total number of URLs could be more than the total number of pages in the audit because a page may be counted more than once if there is more than one instance of the tag on the page. For example, a page may have a two Facebook Like Buttons on a page, one loads in under 50 ms and the other loads in 250 ms. The same URL will be counted in both groupings.

Click the  View Pages button at the top right from either level of the report to see the Page Details report for each URL.

Export

The export for this report can email a .CSV file to the user showing load times for each tag on each page. Open the report, filter on any tag (or none) and click View Pages in the top right header bar. This will take you to a list of all the pages available from the filter. Click the Export icon:

After clicking the export button, choose Tag Load Time.

The export shows the following columns:

URL

• The URL of each page in the audit repeated once for each tag load.

Tag Name

• The name of the tag. If a tag loads more than once on a page, it will show up in two separate rows.

Account

• The account name or number for each tag.

Load Time

• This shows the total milliseconds it took for the tag to load.

Load Start

• The time in milliseconds when the tag began loading.

Load End

• The time in milliseconds when the tag finished loading.

Status Code

• The code returned from the server. Most often the server returns a 200-level code, meaning the tag was received by the server and returned a response. A 200-level code means the tag was received and a response was sent. A 302 code likely indicates the tag was sent insecurely and was redirected with a secure protocol (https).