ampproject
Pixi: how can publishers find out how much an AMP Page delivered on Cache vs Origin on Pixi?
Hi all, I am wondering if it would be possible to specify in Pixi an AMP URL page traffic split between AMP Cache and Origin traffic. Having this information available would be beneficial to understand perhaps whether there is an issue on the AMP CDN resources or the Publishers server response time etc.
The data source for the field data section of Pixi is a blended version of Cache and Origin. They are not able to be unblended (we don't own the data source). There are few situations in which the CDN would be at fault, since the data source is over all traffic over the course of a month, there wouldn't have been a failure and any load would have to be at a country-wide ban of a CDN to likely have much impact.
That's a great point, I am wondering if it would be possible to highlight this info to some level of extent to point developers to the right source.
chrome-ux-report.materialized.country_summary dataset would allow publishers to get a sense whether some specific country traffic may be suffering overall on LCP for example hinting for specific GEO distribution optimizations on Origin, but of course this would include AMP and non AMP blending I guess...
this sort of feels like using a hammer on a screw to me. Site owners should be using their own analytics for that information. Page Experience should be confirming information, not providing it