I do advise on never installing the plugins that require optimization detective.
Care to elaborate on your concerns?
optimization detective does save for every url visited by anyone, this is just what I noticed (url_metrics I think is the meta), this creates a lot of db hits for no reason.
The way it is designed is that it collects URL Metrics for 3 different visits for a given viewport size, and then once it has the three it stops requesting or allowing new metrics to submitted for that viewport. There are 4 different viewports by default, so this means it is intended that there would be 12 requests coming from visitors per URL per week. But since only the desktop and mobile viewport sizes generally have visitors, then this means 6 requests per week per URL.
Granted, more URL Metrics submissions can end up being made in the case of race conditions of two visitors landing on a page at the same time when URL Metrics are needed. This can also happen if the page was cached when the samples of URL Metrics haven’t been fully collected. But once the URL Metrics have been collected, it is intended that no requests would be collected for a week, or until the page is changed.
We’ve also have an issue open to consider an alternative approach where the URL Metrics are not collected from visitors, but rather as part of a logged-in user process, like collecting URL Metrics from the editor after a post has been saved, or kicking off a site-wide URL Metrics collection as part of a batch process. See https://github.com/WordPress/performance/issues/1311
ah, thank you for the insight, I am a WP CLI Fan also, so if that can be added it would be great!
