---
title: Browser summary: RUM, core web vitals, and more
source: https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-summary-page
---

Our browser monitoring **Summary** page helps you troubleshoot issues with the real user browser performance of your app. Use the **Summary** page to:

-   Get core web vitals at a glance, including largest contentful paint (LCP), interaction to next paint (INP), and cumulative layout shift (CLS).
-   View trends in an app's browser-side performance.
-   Quickly troubleshoot page load timing issues.
-   Go directly to other browser UI pages to examine problems and issues in more detail.
-   Add recommended alert conditions.

## View the Summary page [#viewing]

To view a summary of a browser app's performance:

1.  Go to **[one.newrelic.com](https://one.newrelic.com) > All Capabilities**.
2.  Click **Browser**
3.  Select a browser app.

![Screenshot of the New Relic browser monitoring summary page](https://docs.newrelic.com/images/browser_screenshot-full_browser-summary.webp "Browser monitoring summary")

## Use core web vitals data to improve SEO [#core_vitals]

Use the **Core web vitals** charts to understand how your browser performs according to [Google's Core Web Vitals](https://web.dev/vitals/#core-web-vitals). These include:

-   LCP: Largest contentful paint, which measures loading performance
-   INP: Interaction to next paint, which measures interactivity between user input and browser response
-   CLS: Cumulative layout shift, which measures visual stability in the browser page

Higher scores can help your organization save money and influence SEO. Lower scores can affect your users' perceptions of your organization's website, which could result in dissatisfied customers or lost business opportunities.

To learn more about monitoring core web vitals, see our [Guide to core web vitals](https://docs.newrelic.com/docs/browser/new-relic-browser/guides/guide-to-core-web-vitals).

## Evaluate user experience [#user_time]

In addition to the charts with core web vitals data, evaluate your users' experience with your app by using the following data:

-   **User time on the site**
-   **User-centric page load times** and **Longest interaction to next paint by URL**: To get more details about the [page load timing process](https://docs.newrelic.com/docs/browser/new-relic-browser/page-load-timing-resources/page-load-timing-process), click the chart's title to go directly to the [**Page views** UI](https://docs.newrelic.com/docs/browser/new-relic-browser/additional-standard-features/page-views-examine-page-performance).

## Locate browser performance problems [#performance]

Use these charts to help identify performance problems that are related to the browser:

-   **Initial page load and route change**: This chart shows the load time of a traditional URL change stemming from a load or reload of a URL. To get more details, click the chart's title to go directly to the [**Page views** UI](https://docs.newrelic.com/docs/browser/new-relic-browser/additional-standard-features/page-views-examine-page-performance).
-   **Throughput**: This chart shows browser throughput as pages per minute (ppm). If applicable, this chart also shows single-page app (SPA) data. To get more details, click the chart's title to go directly to the [**Page views** UI](https://docs.newrelic.com/docs/browser/new-relic-browser/additional-standard-features/page-views-examine-page-performance).
-   **Page views with JavaScript errors**: To get more details, click the chart's title to go directly to the [**JS errors** UI](https://docs.newrelic.com/docs/browser/new-relic-browser/browser-pro-features/javascript-errors-page-detect-analyze-errors).

## Examine issues caused by something else [#other-issues]

Performance problems may be related to the browser, or they may be related to something else. To get more details about other issues that may be affecting browser performance, examine the following:

-   **Frontend vs. backend**: This chart links to the connected APM service application. To get more details about [distributed traces](https://docs.newrelic.com/docs/browser/new-relic-browser/browser-pro-features/browser-data-distributed-tracing/), click the chart's title.
-   **First interaction by device type** (desktop, tablet, or mobile) and **First interaction by user agent**: To get more details, click the chart's title to go directly to the [**Page views** UI](https://docs.newrelic.com/docs/browser/new-relic-browser/additional-standard-features/page-views-examine-page-performance).
-   **Related entities**: This widget can help you determine whether performance problems may be caused by issues with [entities](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/core-concepts/what-entity-new-relic/) that have connections to the browser.
-   **View synthetic monitors**: [Synthetic monitoring](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/getting-started/get-started-synthetic-monitoring/) can simulate user traffic. This link can help you proactively detect and resolve outages and poor performance related to critical endpoints before your customers notice.

## Add recommended alert conditions [#recommended-alert-conditions]

Through the browser monitoring **Summary** page you can add recommended alert conditions to your entity.

See the [Alert coverage gaps and condition recommendations](https://docs.newrelic.com/docs/alerts-applied-intelligence/applied-intelligence/alert-coverage-gaps/) page if you want to see more uncovered entities.

Follow these steps to add recommended alert conditions:

1.  Open the browser monitoring **Summary** page.

2.  Click **Add recommended conditions**.

    ![Screenshot of the New Relic browser monitoring Summary page](https://docs.newrelic.com/images/browser_screenshot-full_browser-alert-conditions.webp "Browser monitoring summary")

3.  Choose a number of recommended alert conditions.

    ![Browser monitoring recommended alert conditions](https://docs.newrelic.com/images/browser_screenshot-crop_browser-add-alert.webp "Browser monitoring recommended alert conditions")

4.  Click **Next**.

5.  Select a policy to get notified. You can select an existing one or [create a new one](https://docs.newrelic.com/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/create-edit-or-find-alert-policy/#alert-policy-name).

6.  Click **Activate conditions**.