The page load performance features provide context into the factors affecting the performance of page load timing (sometimes referred to as real user monitoring or RUM). Our approach is to provide you with an aggregate view and opportunities to dig into more granular data around unique pageviews for troubleshooting performance issues.
User Centric Perceived Performance
Web performance teams can use more modern metrics than just page load time to benchmark and improve end-user experience for their dynamic pages. Browser helps developers understand how code impacts customers, answering key questions on page performance. Monitor how long users wait for content to display (paint metrics), how long until users can interact with our page (interactivity metrics), and how long until marquee content renders (largest contentful paint). (see blogpost for more)
Single Page App Route Changes
Traces are snapshots of one user’s experience, surfaced as an outlier due to a longer than average load time. It provides details around when it took place, a segmented breakdown of where load time was spent, browser type, and the user’s geographic location. This report is excellent when dissecting areas of your application which are performing poorly for specific users.
Page Load Time - Segmentation Chart
Page load times capture metrics from the moment a user begins a transaction in the browser until the page completes loading. The reports show average page load time broken down into color-coded segments for: Request queuing, application code, network latency, DOM processing, and Page rendering.
Page Load Time - Histogram and Percentiles
Histograms and percentiles of browser page load times provide a holistic view of the speed of page loads, one that is not focused on averages alone. Histograms and percentiles surface every page load that occurred during a specified time window, providing the ability to drill into outliers that might have been overlooked otherwise.
Understand how your end users’ experience with your site varies by geographical region. Identify if more CDN’s are required, or if high value customers in specific parts of the world are having a negative experience with your site’s performance.
Page-Level AJAX Calls
For a specific page, see all the AJAX calls being made as well as the response time, throughput (rpm), total number of calls, error status codes, and average data transfer made for each one.
Page View Throughput
Throughput is measured in requests per per minute. Throughput metrics help you understand which pages are being called most frequently.
Connect Browser with Backend Performance
From the Page views report, you can select single page URL and see all of the associated backend APM transactions (if you have the APM Agent installed in your application). Quickly view the total call time, average response time, and call count for any individual backend transaction. You can also dive deeper into a particular transaction and see diagnostics within our APM reports.
New Relic's Browser dashboards provide information about your end users' experience based on browser type and version, so you can understand where to focus your time testing and optimizing for performance.
Provides a snapshot of the average number of pageviews received per minute broken down by browser type.
Browser Load Time - Segmentation Chart
For each type of browser, a segmented view of time spent on request queuing, application code, network latency, DOM processing, and Page rendering.
Browser Version Chart
Helps you understand which versions of each browser type your customers come from based on throughput.
If your applications use AJAX to update parts of a webpage after the initial page load, our AJAX dashboards will provide you with the level of visibility you need to understand how those requests are performing and ultimately affecting your users’ experience.
The main AJAX dashboard surfaces your site’s most resource intensive AJAX requests, filterable by time consumption, response time, throughput, callback time, and data transfer. From here you can drill into a particular call for detailed analysis.
Calls by Page View
Shows which page views are calling a particular server side controller, with page level detail around throughput, response time, total number of calls, and data transfer.
Request Status Codes
The status codes reporting indicates the return behavior from an AJAX call. A large number of non-200 status codes may indicate a problem with your AJAX endpoints.
Data Transfer Per Request
This shows data transfer which is requested and sent. Use this to look for correlations between high callback times and data transfer rates.
Errors by Browser
For each type of error, this chart shows you which browsers are being impacted by the error and the relative contribution it is making to your total error volume.
Percentage of Page Views with Errors
For each type of error, this chart shows you the percentage of page views affected by it. This allows you to quickly assess the reach and impact a particular error has on your end users.
Error Instance Details
Source Map Support
Best-in-class Customer Experience Monitoring
Crash analysis in New Relic Mobile lets you analyze the most impactful crashes and fix them faster. Source map support in New Relic Browser gives you more actionable visibility into front-end JS errors by showing you exactly where in the original source the error occurred, even if your code is minified.
The following features are used throughout New Relic’s product suite to help make our products easier to use and fit seamlessly into your existing workflows.
Quickly View App Health
New Relic uses color coded status indicators throughout to help you quickly spot performance issues.
Keep an eye on your most critical performance metrics quickly by adding them to a custom dashboard.
Understand how your end users’ experience with your site varies by geographical region, down to the city level. Identify how a CDN or ASN/ Internet Service Provider is performing in different regions.
New Relic is committed to helping customers make their applications fast and secure. We take protecting our customers' data seriously, here's an overview of how we do it.
U.S. and EU Data Regions
Our global data-hosting structure consists of two regions: European Union and United States. You can select your preferred data region during the account setup process, regardless of your physical location. (Note: We do not support migration or aggregation of data across regions.)
New Relic has successfully completed a SOC 2 audit of processes and controls relevant to security and availability. This audit reviews our security process and controls and provides both ourselves, and more importantly our customers an independent, third-party assurance that we are taking the appropriate steps to protect our systems and our customer’s data.
Secure Data Center
The infrastructure that runs the New Relic service and stores our customer’s data resides in a Tier III, SSAE-16 certified data center. Customer data is backed up on a regular basis.
New Relic employs both internal and third-party services to perform continuous security scanning on both our network and applications to ensure that our applications and servers remain secure.
Secure by Default
We strongly believe in the concept of “secure by default”. Customers have to explicitly enable settings within New Relic to authorize the sending of sensitive data. We want to make sure that you are not accidentally exposing anything that you don’t want to.
New Relic can be configured to operate securely in regulated environments such as PCI, HIPAA, or SOX. In addition we are Swiss and EU Privacy Shield certified.