How long does it take for a test to load?
I get a
403 response when rerunning the website analysis?
Check your WAF custom rules to make sure that you are not blocking traffic from Observatory to request your site.
Why might users not see any Real User Monitoring (RUM) data on the map in Observatory?
There are several reasons why users might not see any Real User Monitoring (RUM) data on the map in Observatory:
Limited Traffic to Specific URL Paths: When users see the map in Observatory, they are filtering data by a specific URL path. If there is no traffic to that particular path, there will be no corresponding RUM data available to display on the map.
Time Required for RUM Data Population: Populating the RUM database takes some time. It means that newly enabled RUM might not have immediate data available, and users may need to wait for some time before RUM data starts appearing on the map.
Progressive Sampling: RUM data is progressively sampled, which means that not all requests are captured. Some requests may pass through the sampling period, resulting in incomplete or missing data points on the map.
What are the potential reasons for discrepancies between RUM analytics and traffic analytics in Observatory?
Differences between Real User Monitoring (RUM) analytics and traffic analytics in Observatory can occur due to the following reasons:
Adblockers Impact on RUM Data: Similar to the previous point, RUM data collection can be thwarted by adblockers, leading to missed data. Since traffic analytics typically rely on server-side data collection, they may not be as affected by adblockers as RUM.
Progressive Sampling in RUM: RUM data is collected through progressive sampling, which means that not all user requests are captured. This sampling method could result in slight variations in analytics when compared to traditional traffic analytics that record every server request.