Woocommerce editting extreme slow

While WP-Optimize focuses on enhancing your site’s performance, backend slowness during product saving in WooCommerce is often influenced by other factors, such as database complexity or plugin interactions.

Here are some specific steps to help resolve the issue:

1. Clear WooCommerce Transients: Temporary data generated by WooCommerce can accumulate and slow down backend operations. Go to WooCommerce > Status > Tools > Clear transients to clean up unnecessary data.
2. Database Table Optimization: WooCommerce tables, such as wp_postmeta and wp_woocommerce_sessions, can grow significantly. Ensure these are optimized. If possible, check database indexes for efficiency.
3. Check Plugin Overhead: Some WooCommerce plugins or extensions might add extra processing during product saving. Temporarily deactivate non-essential plugins to identify conflicts.
4. Debug Slow Queries: Use a tool like Query Monitor to identify slow database queries related to saving products. This can help pinpoint WooCommerce processes needing attention.

These steps should help address the slowness you’re experiencing. Hope it helps, Thanks!

Hi @wpmansour, I should have tested this before but I only thought about this now: when I edit or create a normal WP post it saves very slow too. Tomorrow I’ll crate a copy of the site for testing. I can’t deactivate plugins on the live site.

Thanks, Tom

Its looks like a very strange issue, we just found out that the product IS saved but the wheel keeps spinning. Never experienced this before.

Thanks for the follow-up! If the product is saving correctly but the spinner keeps spinning, it sounds like the save request is completing on the backend, but the AJAX response might be delayed or encountering an error.

Here’s what I’d suggest next:

1. Inspect AJAX Requests: Open your browser’s developer tools (usually F12 > Network tab) while saving a product. Check if the AJAX request to save the product is returning an error or timing out.
2. Error Logs: Check your site’s error logs for any PHP errors or timeouts related to saving products. This could give clues about what’s happening behind the scenes.
3. JavaScript Conflicts: A script conflict could also be causing the spinner to stay active. Temporarily switch to a default theme (like Twenty Twenty-Three) and disable non-essential plugins on your test site to isolate the issue.

These steps should help narrow down whether the issue is with WooCommerce, another plugin, or custom code. Let me know what you find, and I’ll be happy to guide you further!

Thanks for the extra suggestions. The front-end is now okay and sale starts tomorrow so I’m not changing things on the test site too which runs on the same server. We are also in contact with the hosting company and might upgrade our package.

I’ll be back when there is any news.

Thank you for the update! It’s great to hear the front-end is running smoothly. Given the spinner issue, working with your hosting provider to ensure server resources are sufficient sounds like a good step forward. Upgrading the hosting package could help if server performance is contributing to the backend slowness.

Hi @wpmansour , I did some extra testing on a copy of the site and it appears to be a WP Optimize caching issue. The difference between saving a post with Page cache disabled and enabled is 30 seconds. I tried changing the cache settings but nothing worked. We need the cache for the front-end. Is there a way to disable it for the back-end?

Best regards, Tom

And the solution appears to be to disable the Automatically preload content option.

To ensure that your cache preloading still runs on your posts despite disabling Automatic preloading, simply make sure to set your cache life span?(under WP-Optimize > Cache > Page Cache)?and activate Scheduled preloader (under WP-Optimize > Cache > Preload) having it set to run at the same time as cache lifespan or earlier.