Do profiling of Optimization Detective (e.g. in Blackfire or Xhprof) to identify any bottlenecks

[westonruter]

Since Optimization Detective uses WP_HTML_Tag_Processor to apply optimizations on the response, it is critical that it operate as efficiently as possible. Any slowdowns during optimization largely defeat the point of Optimization Detective since they will lead to increased TTFB and thus a worse LCP, unless of course page caching is active (which it should still be anyway). I haven't done profiling yet so this would be good to do now before we get to 1.0.0 final.

Profiling should be done while Image Prioritizer and Embed Optimizer are active, on pages that are populated with images and embeds which would result in the various code paths of the tag visitors being followed.