• Resolved tom coady

    (@tomcoady)


    My site has been getting progressively slower so I have disabled all plugins and reactivated them individually in an attempt to discover which plugin is causing this and noticed the loading time doubled accoriding to the query monitor plugin which can provide more details if this would be helpful – possibly a configuration issue as nobody else is complaining?

Viewing 7 replies - 1 through 7 (of 7 total)
  • I’m not getting any better page result speed when disabling the plugin, however I’m not sure WooCommerce Maintain it, as I see two such errors on the page load. these two errors popup on their plugin

    Creation of dynamic property WhichBrowser\Analyser\Header\Useragent::$data is deprecated

    Creation of dynamic property WhichBrowser\Analyser\Header\Useragent::$options is deprecated

    Off topic – I recently found a critical issue in a plugin customize-tawk-to-widget where it was adding an entry for every visitor to wp_options which progressively slowed down my site. I found a post from 11 months ago and the owner of the plugin didnt respond or fix it. I managed to fix it by moving that portion to memcached and set expiry on the entry too, which the developer had not done.

    Thread Starter tom coady

    (@tomcoady)

    Thank you for sharing this information. Let’s address each point:

    1. WooCommerce Performance:It’s good that you’ve tried disabling the plugin to test performance. The errors you’re seeing related to WhichBrowser\Analyser\Header\Useragent are deprecation notices, which don’t directly affect performance but indicate that the code is using outdated PHP practices. These should be addressed by the plugin developers in future updates.

    To further investigate WooCommerce performance:

    ? Use a profiling tool like Query Monitor or New Relic to identify specific slow queries or processes.

    ? Check if you have unnecessary WooCommerce extensions active.

    ? Ensure your hosting environment is optimized for WooCommerce (proper caching, PHP version, etc.).

    2. Customize-tawk-to Widget Plugin Issue:I’m glad you found and fixed that critical issue. Your solution of using memcached with an expiry time is an excellent approach. It’s unfortunate that the plugin developer hasn’t addressed this problem. Here are some suggestions:

    ? Consider forking the plugin and maintaining your own version with the fix.

    ? Share your fix on the plugin’s support forum or GitHub repository (if available) to help other users.

    ? Look for alternative plugins that offer similar functionality but with better maintenance.

    For future reference, always be cautious with plugins that store data for each visitor, as they can quickly bloat the database.
    Plugin Support Zubair Zahid (woo-hc)

    (@doublezed2)

    Hello tom coady,

    Thank you for contacting WooCommerce support.

    My site has been getting progressively slower so I have disabled all plugins and reactivated them individually in an attempt to discover which plugin is causing this and noticed the loading time doubled accoriding to the query monitor plugin which can provide more details if this would be helpful – possibly a configuration issue as nobody else is complaining?

    I understand that you’ve noticed a significant slowdown on your site.
    Could you confirm if Query Monitor suggests that Google for WooCommerce contributes to the slowdown? If possible, please share a screenshot of these results.

    Additionally, I’d like more information about your setup.
    Could you send a copy of your site’s System Status Report?
    You can find it under WooCommerce > Status, then select Get system report and Copy for support.

    Looking forward to your response. ??

    Thread Starter tom coady

    (@tomcoady)

    Thanks for your reply Zubair. Fortunately I suspect that the root cause for this reduced performance is on my Krystal server so you can close this request for now and I will reopen in case I find the issue resurfaces independently of restricted resources.

    Plugin Support Zubair Zahid (woo-hc)

    (@doublezed2)

    Hello tom coady,

    Thank you so much for your response!

    I’m glad to hear that you’ve identified the root cause of the issue.
    Would you mind sharing a bit more about how you figured it out?

    It would also be fantastic for the community if you could share your solution once you have it!

    Wishing you a wonderful day!

    Thread Starter tom coady

    (@tomcoady)

    Thank you for your message and your interest in the issue I was facing. I’m happy to provide more details on how I identified the root cause.

    I noticed that the issue seemed to originate from a specific plugin that had been recently updated. To confirm this, I set up a test environment and replicated the scenario with and without the plugin update. This isolated the plugin as the source of the problem.

    Fortunately the root cause is more difficult to reproduce as it’s about the way WHM distributes the load between cPanel which recommends a maximum of one per domain.

    Thank you for your support and your kind wishes. I hope you have a great day too!

    Best regards,

    Tom

    Plugin Support Zubair Zahid (woo-hc)

    (@doublezed2)

    Hello tom coady,

    Thank you for sharing more details.
    I am grateful for it.

    Please don’t hesitate to contact us again if you have more questions or concerns about WooCommerce.
    We are here to help ??

    Best regards.

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.