Legacy Trigger Code (<18x) - Performance Optimization

How the code runs

  • The JavaScript files are loaded on the first page load and cached by the browser.
  • Files that are not needed during the initial page load are loaded asynchronously.
  • The execution of the code occurs on the DOM READY event after all the client’s content has been loaded.

Code delivery options

  • GZip static content before delivering┬áto the browser.
  • Set caching headers to expire after one day or so, to ensure assets are not being downloaded again on every page the user visits.
  • Use alternate implementation with the foresee-alive.js file at the top of the page and the foresee-trigger.js at the bottom.

Other articles in this section:

  1. Implementing ForeSee for Web
  2. Implementation Steps
  3. Testing & Troubleshooting
  4. Survey Options
  5. Code File Library
  6. Performance Optimization (current article)
  7. Trigger Specifications
  8. ForeSee Replay Specifications
  9. Replay Privacy Options
  10. 508 & WCAG Compliancy