Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support from Boomerang #14

nicjansma opened this Issue Feb 25, 2019 · 0 comments


None yet
1 participant
Copy link

nicjansma commented Feb 25, 2019

We at Akamai help drive the development behind Boomerang, a Real User Monitoring (RUM) library.

We're interested in this proposal for two reasons:

  1. As a third-party library that measures the performance of websites, we're acutely aware of our own cost of doing performance measurement, and have an active drive towards improving hotspots in our own code. A lot of our performance audit was done via browser developer tooling on our dev machines and local devices, and our findings are probably skewed by what we tested on. RUM profiling data of Boomerang seems like a great compliment if it was easily attainable (and could be turned on for X% of users), to better understand our true cost across real devices and all loading scenarios.

  2. Boomerang measures a lot of aspects of performance on the page, getting data from NavigationTiming, ResourceTiming, etc. But a lot of the "true cost" of loading sites these days is in the front-end, especially with large 1P and 3P scripts (besides Boomerang itself, hopefully). If we could use something like this to sample performance data across millions of RUM page loads, we could help users of Boomerang (and customers of Akamai) find scripts that have the highest cost. Specs like LongTasks are a step in that direction, but so far the attribution data from LongTasks isn't sufficient enough to point directly to the problematic line of code. We understand there may be additional security/privacy concerns around measuring 3P scripts though.

Looking forward to the evolution of this idea!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.