Hello,

Thank you for the clarification about get_bloginfo and wp_load_alloptions already using WP cache.

Following up on your suggestion to check for elements making callbacks to the server – I’m wondering if there’s a way to disable AJAX calls that might be impacting page load times?

We’ve noticed that avia_deep_decode and wp_load_alloptions are appearing in AJAX requests on our site. Is it safe to disable theme functionality within these particular AJAX calls, or would doing so potentially break site?

Best regards,
Andraž

Thanks for this answer.
We’re unfortunately experiencing unusually large overhead due to that function and need to optimize it. New Relic is showing 15s+ loading times. Each call invokes wp_load_alloptions which seems redundant. Perhaps those can be saved as some variable or context.
I’m attaching a short loom video in the private content area going through New Relic.

Our server resources are strong and we’re already using strong page caching, optimized images, etc. but we’re a high-traffic store and therefore wish to optimize even those instances.

Looking through New Relic, I’m noticing a humongous amount of calls to avia_deep_decode, which is okay. However, one redundant thing is within it, which calls get_bloginfo (and wp_load_alloptions). Tracing get_bloginfo, it only seems to retrieve the charset. Could that somehow be cached on a global level without the need for a function call?

I’m looking to learn if these can somehow be further optimized as to primarily reduce our expensive dedicated server load as well as improve cached performance.
Regards,
Neven