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.

[dilipom13]

Hello @westonruter
I have searched the current performance repository and found that all instances of get_mime_types() have already been replaced with wp_get_mime_types().
There are no remaining usages of get_mime_types().

So, no further updates are needed right now.

Thank you!

[westonruter]

@dilipom13 hi. I'm not sure how that relates to this issue?

[dilipom13]

@dilipom13 hi. I'm not sure how that relates to this issue?

Hello @westonruter, no, I have no issue, I am just sharing my thoughts here.
I am just reviewing this point and sharing my opinion here, no confusion.

Thanks for asking the Question.

[westonruter]

@dilipom13 ok, please don't do that as it does create confusion. It's a distraction from the topic that the issue is about. If you have a performance-related matter to investigate, please create a new specific issue for it. In any case, I'm not sure how what you shared is related to performance. Thank you.

[dilipom13]

ok, please don't do that as it does create confusion. It's a distraction from the topic that the issue is about. If you have a performance-related matter to investigate, please create a new specific issue for it. In any case, I'm not sure how what you shared is related to performance. Thank you.

Okay @westonruter, Sorry for the confusion.
I will keep these things in mind.