Ideas

[Kanti]

• top and flop list on basis of page attributes. eg. Backend/Frontend Layout
• save some Requests with this: https://github.com/treosh/web-vitals-reporter

[pixeldesu]

Saw your extension, as I thought about making something like this myself! But I'll just drop some of my architectural thoughts as ideas here.

Regarding the first open question:

what about Sites with a lot of Traffic?
after 1_000_000 requests MySQL gets pretty slow (1,2s on my Laptop)

Considering the Web Vitals Metrics are just numbers, there could be an (optional) Scheduler task that combines and averages the values in tx_webvitalstracker_measure for a page. The more traffic an instance has, the more frequent they could run the task.

Another way of limiting requests would be a "percentile-threshold" kind of configuration, where an admin could define a threshold of (for example) 0.25, meaning that only every 4th request would actually be counted for measuring and the rest would be silently dropped. If someone wanted to count everything, they could just set it to 1, equaling all requests.