Skip to content
NR1 Nerdpack for exploring the business value of performance on Browser applications.
JavaScript CSS
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE chore: moving the issue templates. Oct 22, 2019
component chore: Remove unnecessary Link reference. Oct 22, 2019
nerdlets chore: Close #4 + linting. Oct 22, 2019
screenshots chore: updated screenshots. Oct 24, 2019
.gitignore Closes unreported issues on the header sparklines in the details page. Aug 31, 2019
.prettierrc.js Updated project to match Nerdhack standards Sep 6, 2019
.uuids README and repo prep, including screenshots. Aug 30, 2019 Updated project to match Nerdhack standards Sep 6, 2019
LICENSE Updated project to match Nerdhack standards Sep 6, 2019 Update Readme Oct 16, 2019 chore(3rd party notices): Including 3rd party notices Sep 17, 2019
package-lock.json fix: Fix for the issues with infinite issues + consolidation of the i… Sep 19, 2019
package.json chore: advance senver. Oct 22, 2019
third_party_manifest.json chore(3rd party notices): Including 3rd party notices Sep 17, 2019


GitHub release (latest SemVer including pre-releases) Snyk


nr1-browser-analyzer uses the PageView events in New Relic to interrogate and categorize the performance of a web site. You can explore the performance of individual pages, and forecast how improving performance impacts KPIs like bounce rate and traffic. This analysis is based on moving individual browsing sessions from Tolerated and Frustrated into Satisfied (as defined by the apdex value for a given New Relic Browser application).

Screenshot #1 Screenshot #2

Note that this NerdPack is not served as a launcher on the homepage of New Relic One. Instead, you'll have to navigate to a Browser app via the Entity Explorer in New Relic One.

Open Source License

This project is distributed under the Apache 2 license.

What do you need to make this work?

  1. New Relic Browser agent(s) installed and the related access to New Relic One.
  2. See step 1. 😁

Getting started

First, ensure that you have Git and NPM installed. If you're unsure whether you have one or both of them installed, run the following command(s) (If you have them installed these commands will return a version number, if not, the commands won't be recognized):

git --version
npm -v

Next, install the NR1 CLI by going to this link and following the instructions (5 minutes or less) to install and setup your New Relic development environment.

Next, to clone this repository and run the code locally against your New Relic data, execute the following command:

nr1 nerdpack:clone -r
cd nr1-browser-analyzer
nr1 nerdpack:serve

Visit, navigate to the Nerdpack, and

Deploying this Nerdpack

Open a command prompt in the nerdpack's directory and run the following commands.

# If you need to create a new uuid for the account to which you're deploying this Nerdpack, use the following
# nr1 nerdpack:uuid -g [--profile=your_profile_name]
# to see a list of APIkeys / profiles available in your development environment, run nr1 credentials:list
nr1 nerdpack:publish [--profile=your_profile_name]
nr1 nerdpack:deploy [-c [DEV|BETA|STABLE]] [--profile=your_profile_name]
nr1 nerdpack:subscribe [-c [DEV|BETA|STABLE]] [--profile=your_profile_name]

Visit, navigate to the Nerdpack, and


New Relic has open-sourced this project. This project is provided AS-IS WITHOUT WARRANTY OR SUPPORT, although you can report issues and contribute to the project here on GitHub.

Please do not report issues with this software to New Relic Global Technical Support.


New Relic hosts and moderates an online forum where customers can interact with New Relic employees as well as other customers to get help and share best practices. Like all official New Relic open source projects, there's a related Community topic in the New Relic Explorers Hub. You can find this project's topic/threads here: (Note: URL subject to change before GA)

Issues / Enhancement Requests

Issues and enhancement requests can be submitted in the Issues tab of this repository. Please search for and review the existing open issues before submitting a new issue.


Contributions are welcome (and if you submit a Enhancement Request, expect to be invited to contribute it yourself 😁). Please review our Contributors Guide.

Keep in mind that when you submit your pull request, you'll need to sign the CLA via the click-through using CLA-Assistant. If you'd like to execute our corporate CLA, or if you have any questions, please drop us an email at

You can’t perform that action at this time.