First of all thanks for getting back to me so soon after and please excuse me for not getting back to you sooner.
I'm just gonna list the headings and add comments:
> "Share of cacheable and non-cacheable resources" and "Cached vs uncached resources"
I agree with you... However, maybe for response header headers, you could sample requests, e.g. map all the included resources and check them randomly. Alternatively, this could be offloaded to server side checking of headers, so it's not the client testing the server response headers.
Next, for browser cache, maybe this could be used as well?:
>Resource download size? How else would I know how performance is? Timing alone is not enough, is it?
Great news. Looking forward to this!
>Improved resources reporting, enabling exploration of requests and headers
Regardless of what you say, your RUM resource reporting, exploration options and so on can definitely be improved. Exploration also extends to actually being able to filter requests - However, I fully understand that you cannot base it on client side reporting as this information is not available in the browser.
>Use filtering/segments such as device type. There's a Device Type report, but it's very basic, Page groups and filtering
First of all, I'm looking forward to seeing your improvements.
I will elaborate on my requirements: Instead of having separate reporting views such as device type, geo, etc. as the turning point for reporting, please consider the scenario where I want to inspect certain resources such as all resources served via cdn.example.com and the performance of the served files in different markets. Being able to filter, explore and analyze in a flexible manner will help me evaluate different vendors, pinpoint slow vendors, bottle necks, resource hogs, etc.
I hope it makes sense... otherwise, please contact me.
>Recordings, maybe? Snapshots are near useless
I think the usefulness of snapshots boils down to some of the issues mentioned above. E.g. It's difficult to use the snapshots to pinpoint what causing a slow. I'll give you an example:
Regardless of which snapshot I explore, I see only 5 domains in the "Domain And Resources Info" even though the page is requesting resources from many more domains.
In order for snapshots to be truly useful, it should be a waterfall view and include all requests in a sortable, filterable manner.
Additionally, the snapshots lists pages viewed. Now, let's say I want to find out if the page is slow because it's being loaded by users in a "slow" country vs having elements which are slowing the page vs a combination of these 2 factors, I can't. If I go into the page report (yes, I have to switch views/reports as well) and try to find the URL using copy/paste - I can't find it (in this case, even though the time period is the same)! This leads me to believe that the two reports are not in sync. Anyway, I can then explore a similar page but I can't see what's going on on that page... the summary gives an high level overview which is nice, ajax calls is the next tab which is empty and if I'm lucky, there might be a few snapshots available on the snapshot page. However, I want to see a detailed breakdown of that page... and yes, I know it'll change over time so depending on the time frame I want to explore, some resources are likely to be different.
How can that be handled? Well, I guess you could create a general overview where content types can be explored, another where it can be explored by domain, an aggregated view of all resources that have been loaded over the time frame (with percentages of how many times each resource was requested) and a view where all variable resources have been filtered out.
I have tons of ideas for improvements. It's really up to you to view the challenge in a new light and start taking your own poison, because I bet you wouldn't find your RUM tool very useful either.
I understand. Hope you'll find a way because it would be very helpful in detecting deprecation warnings, etc.
>In the section "Performance affected by various factors"
I've seen it but it doesn't help. I can't explore the resources. E.g. "First Party Resources", if I select a domain to explore, I can't see what resources were requested from that domain :'(
In essence, the Site24x7 RUM is reporting on a very superficial level. I do understand and respect that granularity might lead to slower interface and a poor user experience, so I'll leave it up to you to prioritize the level of detail.
All I'm saying is that your RUM has potential to be really really useful, acting as a tool to track down and eliminate requests which are slowing down the apps.
I'm looking forward to seeing my pain points being addressed ;-)
Thanks for listening.