Hello Dario,
We are sorry that Yoast SEO is causing some unexpected high CPU usage. Are you running Yoast SEO 16.7 and WordPress 5.7.2? And to clarify further, does the issue still happen if Yoast is the only plugin active on the site and you switch to a default WordPress theme like Twenty-Twenty?
This guide explains more about how to do a conflict check: https://yoast.com/help/how-to-check-for-plugin-conflicts/
We look forward to hearing from you.
I didn’t similar behavior, but my websites run on dedicated servers.
Which is version of WP Bakery? It could be an issue with outdated version. The latest is 6.7.0 – https://kb.wpbakery.com/docs/preface/release-notes/
I also had this problem. My CPU skyrocketed and maxed out the server causing 503 errors. I rolled back to the last version of Yoast and that seemed to fix it.
For what it’s worth I’m running WPBakery 6.7.0 (most recent version).
Hi @amandabandb
We are sorry you’re having a similar issue. Please open a new request. That way it’s easier to track issues and provide assistance for your case scenario. Thanks!
Hello,
i’m back, so i confirm: latest version of WP, latest version 6.7 of WPBakery, and the latest version of Yoast
When i update a page with WpBakery+Yoast i have the problem of the resources.
I’m with a professional hosting with the “starter hosting”, so i can’t use it because Yoast get all the resources and make more slow the website (backend).
So i need to pay the double price to the hosting to upgrade it.
Can you check the codes to make more “light” that plugin? for sure ther’s something that need more cpu when update a page.
Best regards
-
This reply was modified 4 weeks ago by
mimmicat69.
Hi @mimmicat69
Thanks for confirming that you have the latest version of WordPress, WPBakery, and Yoast SEO.
Could you check if you are meeting all of the necessary plugin requirements in order to run the plugin properly?
Could you also check if you’ve already completed the SEO data optimization process located under your WP admin dashboard > SEO (sidebar) > Tools?
Server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, please ask your hosting provider to look for you.
If you or your web host cannot pinpoint the cause, please provide us with a copy of the server error log for further investigation. As server logs can cover a large amount of time, please limit the error log to a few minutes before you generated the error to a few minutes after the 503 or 508 error.
If the server error log does not contain any errors at the time of the issue, please enable advanced WordPress debugging with the code here. This code requires that you change line 84 to point to a path on your server. Your webhost can provide you with a secure path to save the error.log file.
Hello, i just updated the homepage and i got the error 508
The hoster gave me the Log
For privacy i removed the name of the website
---
Mon Jul 19 11:21:01.834877 2021] [hostinglimits:error] [pid 1042071:tid 140500392736512] mod_hostinglimits: Error on LVE enter: LVE(1056) HANDLER(proxy:unix:/usr/local/php74/sockets/uesrb32n.sock|fcgi://localhost) HOSTNAME(www.xxxxxx.it) URL(/index.php) TID(1042175) errno (7) Read more: http://e.cloudlinux.com/MHL-E2BIG min_uid (0)
[Mon Jul 19 11:21:01.835052 2021] [deflate:error] [pid 1042071:tid 140500392736512] [client 151.16.19.148:0] AH01385: Zlib error -2 flushing zlib output buffer ((null)), referer: https://www.xxxxxx.it/
[Mon Jul 19 11:21:06.349820 2021] [hostinglimits:error] [pid 1042071:tid 140501978171136] mod_hostinglimits: Error on LVE enter: LVE(1056) HANDLER(proxy:unix:/usr/local/php74/sockets/uesrb32n.sock|fcgi://localhost) HOSTNAME(www.xxxxx.it) URL(/wp-cron.php) TID(1042157) errno (7) Read more: http://e.cloudlinux.com/MHL-E2BIG min_uid (0)
[Mon Jul 19 11:21:06.349997 2021] [deflate:error] [pid 1042071:tid 140501978171136] [client 81.31.149.138:55072] AH01385: Zlib error -2 flushing zlib output buffer ((null)), referer: https://www.xxxxxxx.it/wp-cron.php?doing_wp_cron=1626686465.9471149444580078125000
[Mon Jul 19 11:21:11.941824 2021] [proxy_fcgi:error] [pid 1042071:tid 140502237918976] [client 151.16.19.148:0] AH01067: Failed to read FastCGI header, referer: https://www.chedolcidigioia.it/wp-admin/post.php?post=2687&action=edit
[Mon Jul 19 11:21:11.941919 2021] [proxy_fcgi:error] [pid 1042071:tid 140502237918976] (104)Connection reset by peer: [client 151.16.19.148:0] AH01075: Error dispatching request to : , referer: https://www.xxxxxx.it/wp-admin/post.php?post=2687&action=edit
[Mon Jul 19 11:21:14.342108 2021] [proxy_fcgi:error] [pid 1042071:tid 140500367558400] [client 151.16.19.148:0] AH01067: Failed to read FastCGI header, referer: https://www.xxxxxxxa.it/wp-admin/post.php?post=2687&action=edit
[Mon Jul 19 11:21:14.342166 2021] [proxy_fcgi:error] [pid 1042071:tid 140500367558400] (104)Connection reset by peer: [client 151.16.19.148:0] AH01075: Error dispatching request to : , referer: https://www.xxxxxx.it/wp-admin/post.php?post=2687&action=edit
[Mon Jul 19 11:21:17.049190 2021] [proxy_fcgi:error] [pid 1042071:tid 140499771971328] [client 151.16.19.148:0] AH01067: Failed to read FastCGI header, referer: https://www.xxxxxxx.it/wp-admin/post.php?post=2687&action=edit
[Mon Jul 19 11:21:17.049241 2021] [proxy_fcgi:error] [pid 1042071:tid 140499771971328] (104)Connection reset by peer: [client 151.16.19.148:0] AH01075: Error dispatching request to : , referer: https://www.xxxxxxx.it/wp-admin/post.php?post=2687&action=edit
[Mon Jul 19 11:21:17.240079 2021] [proxy_fcgi:error] [pid 1042071:tid 140501969778432] [client 151.16.19.148:0] AH01067: Failed to read FastCGI header, referer: https://www.xxxxxxx.it/wp-admin/post.php?post=2687&action=edit
[Mon Jul 19 11:21:17.240166 2021] [proxy_fcgi:error] [pid 1042071:tid 140501969778432] (104)Connection reset by peer: [client 151.16.19.148:0] AH01075: Error dispatching request to : , referer: https://www.xxxxxx.it/wp-admin/post.php?post=2687&action=edit
---
Hi,
Thanks for providing the server log.
Could you check if you are meeting all of the necessary plugin requirements in order to run the plugin properly?
Could you also check if you’ve already completed the SEO data optimization process located under your WP admin dashboard > SEO (sidebar) > Tools?
Often, we see problems occur in combination with another plugin or theme. The fastest way to rule out any conflict, is to deactivate all non-Yoast plugins and switch to a standard theme like Twenty Twenty.
Please test this on your development or staging site, if you have one. If not, we recommend using the Health Check & Troubleshooting plugin. This plugin has a troubleshooting mode, which does not affect normal visitors to your site.
If you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process: How to check for plugin conflicts
We’d like to know if you still encounter this issue with a default WP theme such as TwentyTwenty, and only WPBakery and Yoast SEO as the plugins enabled.
Hi @mikes41720 ,
I can confirm that the server meets all the plugin requirements listed in your website.
Also we have a lot of customers using your plugin without any issue.
We’ve conducted several analysis and found out that the only circumstance in which we detected a huge increase in CPU consumptions is when an user is using Yoast SEO in combination with the WP Bakery page builder plugin.
Yoast SEO with other page builder plugins (e.g. Elementor, etc.) doesn’t have any CPU consumption issue.
Hi @lmarzo
Thanks for confirming that the server meets all of the plugin requirements. Are you working together with the original poster of this topic?
Could you also check if you’ve already completed the SEO data optimization process located under your WP admin dashboard > SEO (sidebar) > Tools?
We haven’t received any reports of conflicts regarding high CPU usage between the latest version of Yoast SEO v16.7 and WPBakery v6.7.
We recommend performing a conflict check with a default WP theme such as TwentyTwenty, and only Yoast SEO and then WPBakery as the plugins enabled. If you are still able to reproduce the abnormal CPU usage (even though you’ve met all of the plugin requirements) with just those 2 plugins enabled, we recommend opening a bug report – https://yoast.com/help/how-to-write-a-good-bug-report/
Otherwise, please enable the plugins and themes, one by one, until you are able to reproduce the issue and locate the plugin or theme conflict.
Hi @mikes41720 ,
sorry, I didn’t write it earlier.
I was working together with the original poster of the topic.
The user executed all the mentioned tests, in combination with other plugins, deactivating plugins, changing default theme, using another installation, we’ve even tried to setup a new site on a different server.
We’ve tested also the scenario Elementor+YoastSEO without any issue.
In conclusion, we had the high CPU usage only when there is a WPBakery+YoastSEO.
Hi @lmarzo
We tried this on a test site with the default WP TwentyTwenty theme and only Yoast SEO and WPBakery as the plugins enabled, and tried to edit a page with WPBakery, and were unable to reproduce the 503 or 508 errors.
Since you’ve mentioned that you’ve already completed the SEO data optimization process, and that this issue (high CPU usage even though plugin requirements are met) occurs with a default theme and only Yoast SEO & WPBakery enabled, we expect this to be a bug. Please log a bug report on our GitHub repository by following the steps here – https://yoast.com/help/how-to-write-a-good-bug-report/
We also recommend reaching out to the WPBakery team and reporting this issue as well. Having both teams work on your issue will help in terms of a resolution.
Hi,
This thread has been marked as resolved due to a lack of activity.
You’re always welcome to re-open this topic. Please read this post before opening a new request.
Thanks for understanding!
