Using RUM To Increase Web PerformanceA functional performance use of Real User Monitoring.
Pre-overoptimization is the root of all web development evil...well, it's a part of its larger root structure anyway....
So, in order to start optimizing, you need to know the appropriate place to focus your work. Otherwise, you may be optimizing something that has no bearing on overall real-user performance issues. You likely use various tools, maybe something like WebPagetest, to test your work, get results, and base the quality of your work on those results and call it a day. Although, as mentioned in this article at SteveSouders.com ( http://www.stevesouders.com/blog/2012/11/14/comparing-rum-synthetic-page-load-times/
), they found those synthetic measurement numbers are typically 2x faster than RUM times
. The SteveSouders' page profiles a test that shows RUM times to 3x slower.
There are scant dev details in this posts referenced article, but I thought it provided a simple, quick, and worthwhile overview that shows a different aspect of performance tuning, as RUM is focus on real users' experience
. It's good insight for a web performance audit, aside from strictly closed-review of development, coding, and environment. RUM offers some help on where to focus work on those aspects, which can allow for more efficient optimization.
Posted as a general consideration of a good point for those that may not be familiar with the RUM concept. And those that are a little too comfortable using the same optimal testing settings, and only looking at those optimal test results as quality of web performance.