WC Admin Pages slow, unresponsive and return “Error retrieving settings”
-
Several WooCommerce page loading issues
Page load times in WooCommerce Admin are generally a minimum of 30 seconds and sometimes fail to load.
I have taken numerous usual steps to identify the root cause that I can explain as required.
The initial issue that caused me to begin troubleshooting, is that Elementor page builder is slow to load a page when opened for editing, or more often, fails to load completely. On occasions this causes the whole site to become unresponsive for a few minutes before returning. When this happens, an increase in memory use is observed (on the recently upgraded infrastructure).
After various attempts to identify the cause, I noticed the Elementor issue is significantly worse when WooCommerce is enabled. That is, without Woo, the page loads slowly (eg 30 seconds), with Woo it usually fails (eg page load of 90 seconds or greater or failure to load at all).
This lead me to further review WooCommerce and related plugins (Payments, Shipping, Square) where the following issues have been observed.
Theme in use is ‘Bridge’ by Qode Interactive – and yes, I can reproduce the error on twenty twenty-three. I’ve also checked in with them first to make sure there’s nothing obvious from a Theme point of view. They have cart.php page to update soon but say that will not be related to this issue. Issues can also be reproduced on a clean install of WP and minimal suite of plugins.
I realise there may be some other underlying root cause for the slow performance, and that the various issues mentioned may be unrelated, but I’m starting here with WooCommerce as there are several broken items and the performance is significantly worse with it enabled.
WooCommerce related issues
Menu item: WooCommerce / Home
“There was an error getting your inbox. Please try again.”
Of course, trying again yields the same result
Menu item: Customers
Long page load time around 60-90 seconds, customer table outline renders then page fails with error “There was an error getting your stats. Please try again.”
Menu item: Payments, Payments Tab, WooPayments, Manage
Error briefly pops up in black box at lower left of screen
“Error retrieving settings”
Page renders but no settings are populated. Re-populating and saving them does not fix the error
Menu item: Payments, Overview
Page sometimes does not render or slowly renders with these errors
Errors briefly pops up in black box at lower left of screen
“Error retrieving all deposits overviews”
“Error retrieving all deposits”
Menu item: Analytics
All charts fail with error
“There was an error getting your stats. Please try again.”
I’ve have a status report available and can load that up if required
WP version 6.3
PHP Version 8.1.19
-
Hi @simplysaru,
Apologies, I was unclear in that last comment, the Mini Cart warnings are indeed all in the front end, not admin. It was just an observation about another Woo-related component that seemed to be generating junk. More of a rant than a root cause for this issue.
In the Admin area, when loading the WooCommerce home page, after initially getting the same console errors as production in local, they have now gone, which is good right, but I’m not sure why.
These are the only two items showing, one a warning, the other some jetpack remnant.
[Warning]positionprop in wp.components.Dropdown is deprecated since version 6.2. Please usepopoverProps.placementprop instead. Note: Note that thepositionprop will override any values passed through thepopoverProps.placementprop. (deprecated.min.js, line 2)[Error] Failed to load resource: the server responded with a status of 403 () (data, line 0)
https://guychapman-prd-local2.local/wp-json/jetpack/v4/connection/data?_locale=userI have been doing everything I can to make the local instance as close to the production one, not all settings are possible to get identical but it’s close. I had been making sure the php settings in local matched production but putting them back to vanilla on local didn’t cause the errors to return.
Those two errors appear with all plugins enabled or with only WooCommerce enabled.
Cheers,
GuyHi Sean,
Thanks for the reply. Yes, I’ve never seen that welcome page work, ever. In perhaps 10 installations over time on this site. I’ve always had to use the skip link in the top right. Although today I went to the link to it in > Settings > Help > Set up wizard, and did manage to get it to work that way.
Everything from my last post is from the hosted site where I did the clean install.
In the local instance, when I first set it up I got the same errors but not since. Just this one error on the local instance ~.local/wp-json/jetpack/v4/connection/data?_locale=user
Locally, page load time to open a page for editing is about 6 seconds, the local instance has the same setup as production with the Bridge Theme, Elementor and the suite of plugins. As expected.
The fresh hosted Test instance is also fast to open a page for editing as it has none of the heavy theme and page builder stuff. Opening WooCommerce Home page is slow though. The blank page loads then it takes about 60 seconds for those console errors to come up. Once they appear some parts of the page render. Usually not the inbox, but it did fully render just now… so inconsistent
Cheers,
Guyedit to say just reloaded the WooCommerce page again on the hosted test site and got the full suite of console errors again :-{
Hi @wpnomad,
In the comments somewhere above I mentioned that I set up a local instance that at first had the errors but is fine now but local and useless.
I don’t have another host to try a vanilla setup on but I’ve checked in a couple of times with the hosting team and they don’t see anything specific.
So, what I have done since my last comment, in attempts to reduce load anywhere I can is…
- I have ditched the Qode Bridge Theme I was using as it was quite heavy with third-party plugins and replaced it with Kadence that is know to be more lightweight. A bit of rapid reworking of the site and have that in place. It’s more of an impact for the front end of course. It may have made things a bit more responsive but didn’t fix the admin slow pages or the WooCommerce console errors.
- So next I’ve upgraded hosting infra, again, Initially I went from shared hosting to a single CPU VPS and have just updated again to 2 CPU and double the RAM and storage available. This has made everything a lot snappier in front and back end and I’m able to at least get Elementor pages to open for editing without freezing. I’m also able to open WooCommerce admin pages without it taking down the whole site while all the console errors time out… so some progress
Certainly seems there is a hosting capacity component to some of this that may be out of the picture now but there are still a rash of errors on Woo pages that take time fail, then show up in the console. There is a jump in memory use when this happens, less of an issue now but on the previous VPS, as soon as I clicked on a Woo page, memory use would jump from say 20% up tp 60% and hang everything for a few minutes, perhaps until something in json / rest or elsewhere, timed out, and the errors show up in the browser console.
so current state is that I have a useable site, with lots of Woo console errors, and Elementor page edit times of about 30 seconds.
From the cast of thousands who have dipped into this ticket, it sure would be good to talk to someone who understands the WC Ajax / rest / json stuff, how it hangs together and authenticates, what is calling what, where the timeouts may be…
Cheers,
GuyIn the hosted test environment that is vanilla WP with only WC plugin installed, I updated WC to 8.1.0 that was just released and I get the same errors plus this new one (that doesn’t appear on every page load)…
Error: Minified React error #130; visit https://reactjs.org/docs/error-decoder.html?invariant=130&args[]=undefined&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.Good to see someone has spent time changing the big purple exclamation mark error icon to a small grey one. This is good, makes it easier to fit all the errors onto one tidy screen-shot now ??
- The topic ‘WC Admin Pages slow, unresponsive and return “Error retrieving settings”’ is closed to new replies.
