Fact Finders: Sorting out the truth in Real User Monitoring


News: Fact Finders: Sorting out the truth in Real User Monitoring

  1. The falls claim of 100% Coverage

    What all vendors claim to do is capture data from 100% of your users. When looking closer you see that many of these solutions – especially the β€œFreemiumsβ€? – rely on the W3C Navigation Timings. So my question is: How can I cover ALL Users with W3C timings when these timings are NOT AVAILABLE on all browsers?

    W3C timings are only available on new browsers. So –what about the IE6, IE7, IE8, the whole Safari Browser family, older Firefox and Chrome instances? Looking at current statistics they sum up to 35% of the overall market share (http://www.w3counter.com/globalstats.php). The statements of vendors that rely on these timings to capture all users experience are simply not accurate.

    The performance impact of monitoring

    After finding that out I just asked myself: β€œAre there anymore deficiencies that can be found?β€?

    Continue reading the blog ...

  2. obvious questions not addressed in this article because it would not in anyway further the marketing agenda

    1. what typical % of users leave a website because of errors compared to...(a) the content is not relevant, (b) the layout & styling looks ugly, (c) there is nothing new I am interested in, (d) there are two many ads on the site, (e) could not wait for the page to load because of ADD, (f)....blah blah... Are we spending huge amount of user time, bandwidth, company money & resources on <1%

    2. what % (sample population) of users do I need to really monitor to actually determine the user experience with the typical causes beyond the browser (which could be realistically determined in a test lab) such as underlying network issues which incidentally are probably not under your control

    RUM is so new and the products are so dumb (all or nothing) it is a wonder there is some tangible benefit obtained from their usage but maybe that is a reflection of a more fundamental problem with web clients, backend services and the underlying infrastructure which has failed to come up with scalable ways to observe across execution and transmission boundaries. 

    Well lets hope that changes in how execution is distributed and migrated dynamically from service end points that we will have less and less need for such stools.