App server requests greatly outnumber Browser PageView transactions

Problem

Often the number of app server transactions (requests per minute or rpm) is larger than the number of browser transactions (pages per minute or ppm) for the same application. Even sites where all pages are web-facing (no API or back-end-only components) may have between two and ten times more transactions than recorded browser page views.

Cause

Some common reasons that this can occur are:

App requests (rpm) vs. browser transactions (ppm) Possible reasons for differences
Instrumentation You do not instrument every page of your app, or not every page uses auto-instrumentation.
Webpage format Webpages are not text/html. (To avoid harming data, Browser does not instrument non-html pages, because they are not intended to be parsed by a browser.)
AJAX requests

Some requests to your backend are made through AJAX. AJAX throughput is tracked separately in New Relic Browser's AJAX page.

Note: AJAX tracking depends on your New Relic subscription level(Pro and higher).

Request source Some requests do not come from fully functional web browsers. For example, they are API calls, or they come from devices that do not interpret JavaScript, such as RSS feed readers or search engine indexers.
Browsers Some requests come from very old browsers (earlier than IE 7), or they come from browsers that block cookies or JavaScript. For example, the Ghostery extension for Firefox will block page load timing.
Cache A cache exists between your app server and your end users. Depending on whether cached pages are properly instrumented, this may cause balance to skew the other direction, with more browser throughput than app server.
User behavior

Users navigate away from the page before it finishes loading or before it hits the window.onload() event.

Your New Relic weekly performance report includes the number of page views. This is the total number of page loads that have been recorded with New Relic over the time period. After an end user's browser loads a page that includes page load timing, the JavaScript loads and reports its timing data. If the user navigates away from the page before the JavaScript executes, data is not sent for that page, and it is not included in the total page views report.

For more help

If you would like to ensure all your pages are being instrumented, try troubleshooting your browser monitoring installation.

Discuss Browser monitoring in the New Relic Online Technical Community! Troubleshoot and ask questions, or discuss JavaScript error reporting or AJAX timing in detail.

If you need additional help, get support at support.newrelic.com.