Show Menu


This plug-in operates by using the Navigation Timing JavaScript API for accurately measuring performance on the web. This provides a native method to get accurate and detailed timing statistics for page load events & asset load times. Previously, measurements of this sort have either utilized the JavaScript Date object for timing metrics, or a rudimentary extrapolation of the Navigation Timing metrics. Both methodologies, even though they provide some trended data for page load times, are unreliable.

What This Plug-In Does

This is a beta version of the plugin, and additional updates may be forthcoming.
This plug-in utilizes the following detailed events to track the individual timing components of a page load:
Calculated From
Redirect Timing
fetchStart - navigationStart
App Cache Timing
domainLookupStart - fetchStart
DNS Timing
domainLookupEnd - domainLookupStart
TCP Timing
connectEnd - connectStart
Request Timing
responseStart - connectEnd
Response Timing
responseEnd - responseStart
Processing Timing
loadEventStart - domLoading
onLoad Timing
loadEventEnd - loadEventStart
Total Page Load Time
loadEventEnd - navigationStart
Performance Instances
The following graph illustrates the timing attributes defined by the PerformanceTiming interface and the PerformanceNavigation interface with or without redirect, respectively.
Full details on the Navigation Timing object can be found here:
In addition, the plugin can optionally use the performanceEntries object to record the asset name, asset load time start, and asset load time duration details for each individual asset loaded on a given page. A large amount of information is recorded with this plugin, and as such it requires that the DOM storage object is enabled in order to store the page load information between page views. Please be sure that your company's privacy policy allows for the use of the DOM storage object before enabling this functionality. It also requires the use of a listVar to track all assets.

Required Supporting Plug-Ins

  • appendList
  • getPreviousValue

Plug-In Code and Implementation

The following instructions require you to alter the data collection code on your site. This can affect data collection on your site, and should be done only by a developer with experience using and implementing Adobe Analytics. This plugin is compatible only with AppMeasurement tracking libraries.
Config Section (before doPlugins):
s.pte : Comma-separated list of events containing the 10 events you wish to use - the individual timing event components (events 1 - 8), the total page load time (event 9), and total performance instances (event 10) - in that specific order.
s.ptc : Set to determine whether or not to execute the plugin within doPlugins. Always set to false.
Sample Calls
s.pte = 'event10,event11,event12,event13,event14,event15,event16,event17,event18,event19' 
//[--------------------------- 1 to 8 ---------------------------][-- 9 --][- 10 -] 
s.ptc = false; 

doPlugins Section:
To initialize the plug-in, one line of code is required in the doPlugins section of your s_code, preferably after you have designated the s.pageName variable. If you wish to utilize the asset load time functionality within the plug-in, you must pass in the name of the list variable to be used. Otherwise, only the performance timing entries will be tracked in the events you previously specified in the s.pte variable.
In order to correlate performance timing entries with pages on your site, you must also initialize the getPreviousValue plug-in. We recommend comparing these performance entries with either the previous page name or the previous page URL value.
Sample Calls
/* Performance Timing */ 
s.eVar9 = s.getPreviousValue(s.pageName,'gpv_v9','');  //Record the previous page name in the designated eVar of your choice 

Plugins Section:
Lastly, add the plug-in itself to your JavaScript implementation.
/* Plugin: Performance Timing Tracking - 0.11 BETA */ 
s.performanceTiming=new Function("v","" 
+"var s=this;if(v)s.ptv=v;if(typeof performance!='undefined'){if(perf" 
s.performanceWrite=new Function("","" 
+"var s=this;if(performance.timing.loadEventEnd>0)clearInterval(s.pi)" 
+"var pt=performance.timing;var pta='';pta=s.performanceCheck(pt.fetc" 
+"v!='undefined'){var pe=performance.getEntries();var tempPe='';for(v" 
+"ar i=0;i<pe.length;i++){tempPe+='!';tempPe+=pe[i].name.indexOf('?')" 
s.performanceCheck=new Function("a","b","" 
+"ed(2);}else{return 600;}}"); 
s.performanceRead=new Function("","" 
+"var s=this;if(performance.timing.loadEventEnd>0)clearInterval(s.pi)" 
+";var cv=s.c_r('s_ptc');if(s.pte){var ela=s.pte.split(',');}if(cv!='" 
+"'){var cva=s.split(cv,'^^');if(cva[1]!=''){for(var x=0;x<(ela.lengt" 
+"[s.ptv]='sessionStorage Unavailable';}s.ptc=true;"); 
/* Remove from Events 0.1 - Performance Specific,  
removes all performance events from once being tracked. */ 
s.rfe=new Function("","" 
+"var s=this;var ea=s.split(,',');var pta=s.split(s.pte,',');" 
+"try{for(x in pta){,pta[x]);s.contextData['ev" 
/* Plugin Utility - RFL (remove from list) 1.0*/ 
s.rfl=new Function("l","v","d1","d2","ku","" 
+"var s=this,R=new Array(),C='',d1=!d1?',':d1,d2=!d2?',':d2,ku=!ku?0:" 
+"if(L[i]!=v&&C)R.push(C[1]);else if(L[i]!=v)R.push(L[i]);else if(L[i" 
+"]==v&&ku){ku=0;if(C)R.push(C[1]);else R.push(L[i]);}C='';}return s." 


  • Always test plug-in installations to ensure that data collection is as expected before deploying in a production environment.
  • Because the plug-in passes the performance data as they are associated with the previous page, data is not collected for the final page view of the visit.
  • If you are tracking asset timing, this plug-in relies on the ability to set DOM storage values in the user's web browser. If the user does not accept cookies and have DOM storage enabled, the plug-in will not pass data into Analytics.
  • A very small percentage of users will not pass navigation timing data due to browser limitations, and logic is contained within the plugin to ensure that the data is not skewed as a result - particularly with a small portion of mobile browsers. However, this plug-in has been successfully tested in IE, Firefox, Chrome, and Safari.
  • Calculated Metrics should be created to aid in summarizing and understanding visitor behavior associated with these metrics:
    • Average Redirect Timing (Redirect Timing/Performance Timing Instances)
    • Average App Cache Timing (App Cache Timing/Performance Timing Instances)
    • Average DNS Timing (DNS Timing/Performance Timing Instances)
    • Average TCP Timing (TCP Timing/Performance Timing Instances)
    • Average Request Timing (Request Timing/Performance Timing Instances)
    • Average Response Timing (Response Timing/Performance Timing Instances)
    • Average Processing Timing (Processing Timing/Performance Timing Instances)
    • Average onLoad Timing (onLoad Timing/Performance Timing Instances)
    • Average Page Load Timing (Total Page Load Time/Performance Timing Instances)