--- title: Page views: Examine page performance source: https://docs.newrelic.com/docs/browser/new-relic-browser/browser-pro-features/page-views-examine-page-performance --- The **Page views** page in browser monitoring provides insight into the performance of your site's pages and user experience. Sort options help you find details about percentage of page load time, average page load time, or throughput. You can also view user frustration signals and performance impact metrics, access session replays, and explore detailed information about the top webpages viewed. Our browser capabilities include [single-page app (SPA) monitoring](https://docs.newrelic.com/docs/browser/single-page-app-monitoring/get-started/welcome-single-page-app-monitoring). If you have opted in to SPA monitoring, your SPA **Page views** UI will be different. You can toggle between which view (SPA or standard browser) you want. ## View summary information [#dashboard] Browser monitoring lists page views as [URLs](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/url-whitelists-grouping-browser-metrics). This makes it easy to identify specific frontend page views; for example, `/browse/plans`. ![A screenshot of the Page views UI in New Relic](https://docs.newrelic.com/images/browser_screenshot-full_pageviews-overview.webp "Page views UI overview") **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > (select an app) > Page views**: This page provides detailed information about page load time, throughput, top transactions, and traces. To view detailed information about which pages the end users are viewing for your app: 1. Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > (select an app) > Page views**. 2. Toggle the page view for SPA or standard browser apps as applicable. 3. Select the type of view for page load timing information as a [chart (default), histogram, or percentile](https://docs.newrelic.com/docs/apm/apm-ui-pages/monitoring/response-time-chart-types-apm-browser/). ## Understand user impact metrics [#user-impact-metrics] The Page views page includes user impact pane that help you understand how performance issues affect your users' experience. ### Frustration signals [#frustration-signals] The **Frustration signals** shows the percentage of user sessions containing frustration indicators in the selected time period. Frustration signals include: - **Rage clicks**: Users rapidly clicking the same element 4 or more times within 1 second - **Dead clicks**: Clicks that don't result in any detectable change within 2 seconds - **Error clicks**: Clicks followed by a JavaScript error within 2 seconds ### Performance risk [#performance-impact] The **Performance risk** shows the percentage of user sessions affected by performance issues in the selected time period. It displays unhandled exceptions and application errors for JavaScript errors. ### Session Replay sampling considerations [#sampling-considerations] The user impact cards adapt based on your Session Replay configuration: **Session Replay enabled with standard sampling** When Session Replay is enabled with sampling rates at or above default thresholds (10% for general sampling, 100% for error sampling), both cards display full metrics with session replay counts and direct links to replay sessions. **Session Replay enabled with low sampling** When sampling rates are below recommended thresholds, the cards display a notice suggesting you increase your sample rate. Click the "Increase your sample rate" link to navigate to your browser application settings. **Session Replay disabled** When Session Replay is disabled, the cards show only session counts without replay data. A notice appears with See where your users are struggling and a Turn on session replays link to enable the feature. ## Examine performance details [#view_details] From the page view summary, click a URL to view performance details about page load, frontend and backend timing in [APM](https://docs.newrelic.com/docs/apm/apm-ui-pages/features/request-queuing-tracking-front-end-time/) or in [distributed tracing](https://docs.newrelic.com/docs/distributed-tracing/ui-data/understand-use-distributed-tracing-ui), throughput, [types of browsers](https://docs.newrelic.com/docs/browser/new-relic-browser/additional-standard-features/browsers-problem-patterns-type-or-platform), and [session traces](https://docs.newrelic.com/docs/browser/browser-monitoring/browser-pro-features/session-traces-explore-webpages-life-cycle). ![A screenshot of the page view details UI in New Relic](https://docs.newrelic.com/images/browser_screenshot-full_page-load-performance.webp "Page view details") From here you can also: - Compare page load and throughput performance with yesterday and last week. - View response time for app response time for web transactions. ## Examine timing details for page loads [#page_load_timing] The [page load timing process](https://docs.newrelic.com/docs/browser/new-relic-browser/page-load-timing-resources/page-load-timing-process) shows colored-coded details: | Page load timing process | Description | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Request queuing | Wait time between the web server and the application code. Large numbers indicate a busy application server. | | Web application | Time spent in the application code. | | Network duration | The network latency, or the time it takes for a request to make a round trip over the internet. For apps that have been deployed using the [copy/paste method](https://docs.newrelic.com/docs/browser/new-relic-browser/installation-configuration/adding-apps-new-relic-browser), browser monitoring includes web app and queue time in network time. | | DOM processing | In the browser, parsing and interpreting the HTML. Measured by the browser's `DOMContent` event. | | Page rendering | In the browser, the time to display the HTML, run the inline JavaScript, and load images. Measured by the browser's `Load` event. |