Atatus Browser monitoring measures page load time, also known as real user monitoring (RUM), but it goes far beyond that to measure:
- Individual page performance
- AJAX requests performance
Individual page performance
Page load time is a vital metric to understand how fast the web site content is loading for end users. Page load time is represented in two numbers (usually one for the back-end application and network time, and the other for browser rendering and sub-resource loading time). Atatus uses browser’s Navigation Timing API to collect data from most points in the page load process:
We take these timings and graph the deltas between them in a stacked graph. We have an overall graph (below), and we also segment the stats by a few other metrics, like browser (Safari, Firefox, Internet Explorer) and page. Atatus also allows you to view details by page load time distribution, average page load time, and throughput.
AJAX is everywhere. Single page web apps do it and it’s increasingly rare to find a traditional web app that doesn’t have a significant AJAX component. AJAX takes the place of a standard browser navigation, but it’s usually about 1000ms faster. We found that increased visibility into AJAX to be extremely helpful for quantifying the effect that performance problems have on the end user experience.
Atatus wraps the XMLHTTPRequest to capture all AJAX request timings. Atatus help you to visualize response time, throughput requests per minute (rpm), and average data transfer rates per request can help identify timing problems. You also see the error status codes related to the requests provide information about the return behavior from the call
Obviously, we provides the typical reporting information: stack traces, url, browser/OS versions, user agent string, frequency, etc. Along with, we show time line of user actions happened that leads to an error.
At this point, some might ask, Why not just write browser tests, so you can catch errors and regressions before you deploy them? It’s a great question — I definitely don’t see client-side monitoring as a replacement for integration or acceptance tests. But tests almost never capture the variety in real production data or the variety in real users’ browser versions. Atatus Browser monitoring captures all of these by default. Plus, tests only capture errors when you run them, which is usually when you’re committing code changes, but the environment around front end code changes all the time. You always want to know about new errors your users are running into, regardless of whether they come from the deploying new code or from the Google Chrome team rolling out a new browser version.
While our browser monitoring tools give you deeper visibility into our users’ experience of your web app, we’re really excited to bring more features to Atatus. Singe page app(SPA) monitoring is the next step we like to add on our features to gain more visibility into your SPA(e.g. Angular, React, Ember) apps.
Atatus makes performance monitoring and error tracking easier so you can get back to building features for your customers.
Try Atatus Browser Monitoring with free 14 day trial – no credit card required. If you have any questions, we’d love to hear from you.
We recently introduced Node.js Performance monitoring. Checkout our blog about it.