boomerang always comes back, except when it hits something
npm install boomerangjsboomerang always comes back, except when it hits something.
boomerang is a JavaScript library that measures the page load time experienced by
real users, commonly called RUM (Real User Measurement). It has the ability to
send this data back to your server for further analysis. With boomerang, you
find out exactly how fast your users think your site is.
Apart from page load time, boomerang measures performance timings, metrics and
characteristics of your user's web browsing experience. All you have to do is
include it in your web pages and call the BOOMR.init() method. Once the
performance data is captured, it will be beaconed to your chosen URL.
boomerang is designed to be a performant and flexible library that can be adapted
to your site's needs. It has an extensive plugin architecture, and works with
both traditional and modern websites (including Single Page Apps).
boomerang's goal is to not affect the load time of the page (avoiding the
Observer Effect)).
It can be loaded in an asynchronous way that will not delay the page load even
if boomerang.js is unavailable.
* Supports:
* IE 6+, Edge, all major versions of Firefox, Chrome, Opera, and Safari
* Desktop and mobile devices
* Captures (all optional):
* Page characteristics such as the URL and Referrer
* Overall page load times (via NavigationTiming if available)
* DNS, TCP, Request and Response timings (via NavigationTiming)
* Browser characteristics such as screen size, orientation, memory usage, visibility state
* DOM characteristics such as the number of nodes, HTML length, number of images, scripts, etc
* ResourceTiming data (to reconstruct the page's Waterfall)
* Bandwidth
* Mobile connection data
* DNS latency
* JavaScript Errors
* XMLHttpRequest instrumentation
* Third-Party analytics providers IDs
* Single Page App interactions
boomerang can be included on your page in one of two ways: synchronously or asynchronously.
The asynchronous method is recommended.
``html`
Note: You must include at least one plugin (it doesn't have to be RT) or
else the beacon will never fire.
Each plugin has its own configuration as well -- these configuration options
should be included in the BOOMR.init() call:
`javascript`
BOOMR.init({
beacon_url: "http://yoursite.com/beacon/",
ResourceTiming: {
enabled: true,
clearOnBeacon: true
}
});
Loading boomerang asynchronously ensures that even if boomerang.js is
unavailable (or loads slowly), your host page will not be affected.
Create a plugin (or use the sample zzz-last-plugin.js) with a callBOOMR.init
to :
`javascript`
BOOMR.init({
config: parameters,
...
});
BOOMR.t_end = new Date().getTime();
You could also include any other code you need. For example, you could include
a timer to measure when boomerang has finished loading (as above).
The build process bundles boomerang.js and all of the pluginsplugins.json
listed in (in that order).
To build boomerang with all of your desired plugins, you would run:
`bash`
grunt clean build
This creates a deployable boomerang in the build directory, e.g. build/boomerang-.
Install this file on your web server or origin server where your CDN can pick it
up. Set a far future
max-age
header for it. This file will never change.
There are two methods of asynchronously including boomerang on your page: by
adding it to your main document, or via the IFRAME/Preload method.
The former method could block your onload event (affecting the measured
performance of your page), so the later method is recommended.
#### 3.1. Adding it to the main document
Include the following code at the _top_ of your HTML document:
`javascript`
Best practices will suggest including all scripts at the bottom of your page.
However, that only applies to scripts that block downloading of other resources.
Including a script this way will not block other resources, however it _will_
block onload.
Including the script at the top of your page gives it a good chance of loading
before the rest of your page does, thereby reducing the probability of it
blocking the onload event.
If you don't want to block onload either, use the following IFRAME/Preload method:
#### 3.2. Adding it via an IFRAME/Preload
The method described in 3.1 will still block onload on most browsers.
To avoid blocking onload, we can load boomerang in an asynchronous IFRAME or via LINK preload (for browsers that support
it). The general process is documented on in
this blog post.
For boomerang, the asynchronous loader snippet you'll use is:
`javascript`
Minified:
`javascript`
Change the boomerangUrl to the location of Boomerang on your server.
The id of the script node created by this code MUST be boomr-if-as (for IFRAME mode) or boomr-scr-as (for
Preload mode) as boomerang looks for those ids to determine if it's running within an IFRAME and to determine the
URL of the script.
boomerang will still export the BOOMR object to the parent window if running
inside an IFRAME, so the rest of your code should remain unchanged.
#### 3.3. Identifying when boomerang has loaded
If you load boomerang asynchronously, there's some uncertainty in when boomerang
has completed loading. To get around this, you can subscribe to the
onBoomerangLoaded Custom Event on the document object:
`javascript`
// Modern browsers
if (document.addEventListener) {
document.addEventListener("onBoomerangLoaded", function(e) {
// e.detail.BOOMR is a reference to the BOOMR global object
});
}
// IE 6, 7, 8 we use onPropertyChange and look for propertyName === "onBoomerangLoaded"
else if (document.attachEvent) {
document.attachEvent("onpropertychange", function(e) {
if (!e) e=event;
if (e.propertyName === "onBoomerangLoaded") {
// e.detail.BOOMR is a reference to the BOOMR global object
}
});
}
Note that this only works on browsers that support the CustomEvent interface,
which is Chrome (including Android), Firefox 6+ (including Android), Opera
(including Android, but not Opera Mini), Safari (including iOS), IE 6+
(but see the code above for the special way to listen for the event on IE6, 7 & 8).
boomerang also fires the onBeforeBoomerangBeacon and onBoomerangBeacon
events just before and during beaconing.
There are several ways of including Boomerang in your project:
1. Boomerang can be downloaded from the official Boomerang Github repository.
2. NPM: npm install boomerangjs
3. Bower: bower install boomerang
Once fetched, see Building Boomerang
for more details on how to include the plugins you require.
Documentation is in the docs/ directory. Boomerang documentation is
written in Markdown and is built via JSDoc.
You can build the current documentation by running Grunt:
`bash`
grunt jsdoc
HTML files will be built under build/docs.
Open-source Boomerang Documentation is currently published at
akamai.github.io/boomerang/.
The team at Akamai works on mPulse Boomerang, which contains a few mPulse-specific plugins and may have additional
changes being tested before being backported to the open-source Boomerang. mPulse Boomerang usage documentation is
available at docs.soasta.com/boomerang/ and mPulse Boomerang API documentation
is at developer.akamai.com/tools/boomerang/docs/.
Additional documentation:
* API Documentation: The BOOMR` API
* Building Boomerang: How to build boomerang with plugins
* Contributing: Contributing to the open-source project
* Creating Plugins: Creating a plugin
* Methodology: How boomerang works internally
* How-Tos: Short recipes on how to do a bunch of things with boomerang
The boomerang source code is primarily on GitHub at github.com/akamai/boomerang.
Feel free to fork it and contribute to it.
You can also get a check out the releases
or download a tarball or
zip of the code.
We use GitHub Issues for discussions,
feature requests and bug reports.
Get in touch at github.com/akamai/boomerang/issues.
boomerang is supported by the developers at Akamai, and the
awesome community of open-source developers that use and hack it. That's you. Thank you!
Boomerang is brought to you by:
* the former Exceptional Performance team at the company once known as
Yahoo!, aided by the Yahoo! Developer Network,
* the folks at LogNormal, continued by
* the mPulse team at SOASTA, ongoing by
* the mPulse team at Akamai, and
* many independent contributors whose contributions are cemented in our git history
To help out, please read our contributing page.
* _Copyright (c) 2011, Yahoo! Inc. All rights reserved._
* _Copyright (c) 2011-2012, Log-Normal Inc. All rights reserved._
* _Copyright (c) 2012-2017 SOASTA, Inc. All rights reserved._
* _Copyright (c) 2017-2023, Akamai Technologies, Inc. All rights reserved._
* _Copyrights licensed under the BSD License. See the accompanying LICENSE.txt file for terms._