Configuring the reporting of page-render time

To measure the performance of web applications that rely on external content providers, the system uses page-render time (PRT), which is the time for a page to load all content (whether it is delivered from your origin server or from a caching server):

Page-render time = redirect time + container host time + container network time + web beacon onLoad time

To set up the system to report page-render time

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

  1. Connect the Real User Collector and the Real User Analyzer to the same time synchronization server or make sure that the difference of the system times on these components does not exceed 5 seconds.
  2. Ensure that the Real User Analyzer has Manage configuration box selected for each Collector feed.
  3. Set up the Akamai-instrumentation.
  4. Deploy a page-render beacon on the origin server.
  5. Enable detection of the web beacon.
  6. Edit instrumentation settings to tell the system that you use PRT for your web application pages.

After you configure the system to report page-render time, you can use various dashlets and reports to monitor the performance of applications whose content is delivered to end users by external providers. For example, the Global-Application-Delivery-dashlet offers a visual representation of how the end-user-experience performance of your web application varies by geographic location.

Related topic

Page-service-level-thresholds

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*