Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
Managing an application’s performance, and specifically keeping it in good condition, is one of the hardest challenges in software development. That’s true for virtually any programming language and platform.
Real User Monitoring (RUM) is the ability to measure the performance of your website/web application as seen by your end users. Some of the measurements are well-supported, some are browser-specific, and a few standards allow observability by letting you decide the measurement parameters. In the plethora of tools, it is hard to understand the differences. With this post, I would like to provide you a firm foundation on the minimum supported provided by the RUM solution for some solid measurements.
In the old days of the wild-wild west, the performance measurements were instrumented using custom JavaScript code. The challenge was the measurement would begin only after the base HTML was downloaded and the JS code executed.
Every online business owner has woken up in cold sweat from this nightmare at least once in their life: you see your perfect customer, they are in their office, it’s after-lunch hours, and they are entering your website ready to spend a few hundred dollars. But… your website isn’t loading. They get a 503 error, close the tab, and flash-forward 3 minutes later, they purchase from your competitor and forget about your existence.
What could have saved you from losing a client? “Web performance monitoring!” – we say.