Performance: Decrease CURL lookups to Google to improve backend speed

Resolved

(@antonynz)

Thanks for this plugin.

I noticed on multiple sites that this plugin is making CURL requests on every page request in the admin area which makes the backend feel sluggish to navigate.

It seems the plugin is looking up a Google API for Google Ad recommendations. Is it necessary to make this request on every page in the dashboard? Is is possible to cache it?

Here is a backtrace:

curl_multi_select() google-listings-and-ads/vendor/guzzlehttp/guzzle/src/Handler/CurlMultiHandler.php:169
tick() google-listings-and-ads/vendor/guzzlehttp/guzzle/src/Handler/CurlMultiHandler.php:206
execute() google-listings-and-ads/vendor/guzzlehttp/promises/src/Promise.php:251
invokeWaitFn() google-listings-and-ads/vendor/guzzlehttp/promises/src/Promise.php:227
waitIfPending() google-listings-and-ads/vendor/guzzlehttp/promises/src/Promise.php:272
invokeWaitList() google-listings-and-ads/vendor/guzzlehttp/promises/src/Promise.php:229
waitIfPending() google-listings-and-ads/vendor/guzzlehttp/promises/src/Promise.php:69
wait() google-listings-and-ads/vendor/google/gax/src/GapicClientTrait.php:780
getPagedListResponse() google-listings-and-ads/vendor/google/gax/src/GapicClientTrait.php:547
startApiCall() google-listings-and-ads/vendor/googleads/google-ads-php/src/Google/Ads/GoogleAds/V20/Services/Client/GoogleAdsServiceClient.php:1785
search() google-listings-and-ads/src/API/Google/Query/AdsQuery.php:113
query_results() google-listings-and-ads/src/API/Google/Query/Query.php:187
get_results() google-listings-and-ads/src/API/Google/AdsCampaign.php:126
get_campaigns() google-listings-and-ads/src/API/Google/AdsCampaign.php:393
get_highest_spend_campaign() google-listings-and-ads/src/Menu/NotificationManager.php:206
performance_max_ad_strength_count() wp-includes/class-wp-hook.php:324
apply_filters() wp-includes/plugin.php:205
apply_filters() google-listings-and-ads/src/Menu/NotificationManager.php:155
display_aggregated_notification_pill() wp-includes/class-wp-hook.php:324
apply_filters() wp-includes/class-wp-hook.php:348

Viewing 7 replies - 1 through 7 (of 7 total)

Plugin Support shahzeen(woo-hc)
(@shahzeenfarooq)

4 months ago
Hi there!

Thank you for bringing this to our attention. I’ve seen multiple user reports about backend performance issues. For testing purposes, could you please try using the following filter.
```
add_action( 'admin_menu', function () {
	remove_all_filters( 'google_for_woocommerce_admin_menu_notification_count' );
}, 0 );
```
Here is the related thread where the user reported a backend performance issue, and they were able to fix it by using the filter mentioned above:
https://ww.wp.xz.cn/support/topic/poor-backend-performance-when-plugin-is-enabled/#post-18814905

let us know if it fixes the backend performance issue?
Thread Starter Antony Booker
(@antonynz)

4 months ago
Yes I saw that post afterwards. This is very likely related removing the admin notifications from this plugin using that filter will stop the code continuing from this line:
```
apply_filters() google-listings-and-ads/src/Menu/NotificationManager.php:155
```
LovingBro (woo-hc)
(@lovingbro)

4 months ago

Hi @antonynz,

I appreciate you digging into this further and sharing that insight from the stack trace. It is helpful to see that removing the admin notification filter effectively stops execution from the NotificationManager hook and prevents the Google Ads query from running.

You are absolutely right in your assessment, the notification count logic appears to be triggering the API call, and removing that filter prevents the backend request cycle tied to it. That gives us a much clearer picture of where the performance impact originates.

In the meantime, could you confirm whether backend navigation performance has noticeably improved after applying the snippet in real usage across the admin area?

Thread Starter Antony Booker
(@antonynz)

4 months ago

Yes, the admin notification removal snippet will save 1.15s here on every admin page view as it will stop the external CURL requests to Google’s API (this could be longer on some servers depending on the latency to Google).

I have also shared the slow log backtrace on the Github thread.

Plugin Support shahzeen(woo-hc)
(@shahzeenfarooq)

3 months, 4 weeks ago

Hi there!

Thank you for providing more information about the issue. Our developers are actively working on this, and we hope to have a fix as soon as possible.

Since you’ve added the slow log backtrace to the GitHub thread, I recommend keeping an eye on that thread, as our developers will post updates there regarding any progress.

We appreciate your patience and for helping us by sharing the additional details. Thank you!

Before you go, If you’re happy with the support you received today, would you consider leaving us a quick review? It really helps us out: https://ww.wp.xz.cn/support/plugin/google-listings-and-ads/reviews/#new-post

Plugin Support Kay U a11n
(@kingsleyinfo)

3 months, 1 week ago

We’re going to mark this thread as resolved, as the issue is now with the developers.
If you have any further questions, please let us know, and we’ll be happy to look into it.

Plugin Support Saravanan S, a11n
(@simplysaru)

2 months, 1 week ago

Hi @antonynz ,

I wanted to reach out to you to update that version 3.6.1 version address the underlying performance issues you raised in your request. So, we urge you to update to this latest version. Thanks for your patience while we worked on this bug.

We’d really appreciate it if you could leave a review for the plugin. Your feedback helps others make informed decisions and helps us continue improving.

Here’s the link to leave a review: https://ww.wp.xz.cn/support/plugin/google-listings-and-ads/reviews/

Thank you for your time

Viewing 7 replies - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.