I hope you will consider adding caching details to RUM reporting.

• Share of cacheable and non-cacheable resources
• Cached vs uncached resources
• Resource download size? How else would I know how performance is? Timing alone is not enough, is it?
• Improved resources reporting, enabling exploration of requests and headers
• Use filtering/segments such as device type. There's a Device Type report, but it's very basic
• Page groups and filtering
• Recordings, maybe? Snapshots are near useless
• Javascript warnings?

In general I'd say this:

Site24x7 RUM should enable us to pinpoint areas of improvement, issues and report on improvements. It doesn't live up to that.

Adding a bit more to the feature request by quoting blogs.akamai.com/2015/12/cdns-performance-and-monitoring---part-2.html

Now let us look at the KPIs from your front end (RUM) monitoring:

• Performance affected by various factors - load time across various dimensions
  • By page - how long each web page took to render on the browser
  • By mobile devices - on mobile you have less bandwidth, are pages smaller?
  • By various browsers
  • By geography
  • By Edge cache hit or cache miss  (might require integration with your CDN metrics)

• Error frequency and types of errors, by page

• Performance of various steps in the browser's functionality
  • Download time - how long did it take the browser to suck in all the content
  • DOM time - once data is sucked in, how long to parse and build the parse tree
  • Render time - once all the data was read in and parsed, how long to actually render it

• Size of content - ensure pages are not too heavy

Quoting another site:

Benefits of RUM

RUM can help identify how page visitors are using a site or app. It also provides page metrics such as load time for analysis of a page, objects and even individual visits.

• Measure service level targets easily. It offers real-world measurement of key targets by tracking actual visits and delivering top-level data on actual use cases.
• Easily identify problems and better prioritize issues. It can replay user sessions and track transaction paths to surface hidden problems.
• Determine hitches at the network and page level. Problems at the lower levels of a website can hide like needles in a haystack. It can spotlight these problems even when they’re intermittent in nature or based on rare conditions.