Adobe Web Browser Technology Performance

Web performance discussions seem to heat up every few years and they normally focus on various advances in browser capabilities, rehashes of old studies, or the demands of some hot new JavaScript implementation. For a number of years I’ve been an active participant in the design and distribution of global enterprise level JavaScript libraries. A portion of my efforts during that time has gone into the optimization of Adobe’s client-side browser technologies for the Adobe Experience Cloud and Platform. I’ve explored how Adobe can affect the construction and delivery of web browser-based technology in a positive way. In an effort to pull together some of the issues that I’ve dealt with in relation to user experience and the JavaScript that Adobe deploys, I’ve put together an overview white paper that summarizes a number of our findings. Starting with a review of common performance questions, the paper works through the goals of web browser optimization, the most essential performance metrics, the problem of perception, and Adobe specific solutions to these issues. More than anything this is simply a status report in an ongoing discussion that attempts to identify the current optimization state of Adobe Experience Cloud client-side technologies. I will be writing additional papers in the future to help identify Adobe’s best practices that relate to the web performance topic and further extend the discussion.

I’m also going to attempt a series of blog posts that dig into the technical details behind the generalities that are provided in the overview paper. All of the opinions and errors in the paper are my own, but I’ve tried to represent the lessons that we’ve learned as a team in readable format. Here is the high level outline of the paper.

  1. End Goal: Optimize Customer and Visitor Experience
  2. Adobe’s Role in Performance Optimization
  3. Working with Performance Budgets
  4. Optimization Principles for Highly Performant Client-Side JavaScript

I hope you will find it helpful as a starting point in your investigation of Adobe client-side JavaScript performance, or as an addition to your ongoing conversations.

You can get the whole paper here: