Hi @jun-e-jay
We understand that the pages on your sites load very slow with both Yoast SEO and the ACF plugins activated.
Could you check if you are using the latest version of WordPress 5.8.2, Yoast SEO 17.6, and the latest version of ACF?
Just to check, do you also have the Yoast ACF glue plugin installed – https://yoast.com/yoast-seo-supports-advanced-custom-fields-acf/
Would it be possible for you to provide us with any screenshots of any error messages from your browser’s console or any queries or functions that could pinpoint to the page slowness?
Hi Michael,
We use the latest versions and we have the Yoast ACF plugin.
Not sure what to send you regarding screenshots/queries/functions, because the pages in the backend jusr load very slow. I don’t see any errors in the console. Any suggestions?
Hi @jun-e-jay
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
Please do perform a conflict check with a default WP theme, and only ACF, Yoast SEO, and the Yoast ACF glue as the only plugins enabled, and then do see if this issue still occurs.
You can also possibly use the Query Monitor plugin so you’ll be able to track the page generation time and any slow queries or scripts that may help pinpoint this.
If this still occurs with a default setup with a default theme and only those plugins, we invite you to log a bug report on GitHub by following this article – https://yoast.com/help/how-to-write-a-good-bug-report/
Hi,
Thanks, I will try this, but the issue is still the same: with Yoast enabled the backend is slow. With Yoast disbaled the backend is fast. So it seems an issue with your plugin (or combination ACF/Yoast?)
Hi,
I just found out that when I disable the “classic editor” plugin, it all works fine and fast, even with Yoast and Yoast ACF enabled. So it seems that that little plugin is the issue. Even when I add add_filter( ‘use_block_editor_for_post’, ‘__return_false’ ); to my functions file, it make it slow again…
But when I enable classic editor and disable yoast/yoast ACF, it is also fast.
So it seems to be an issue with these 3 plugins?
I have a staging environment to test.
Thanks for the feedback and we are glad you were able to identify the conflicting plugin. Additionally, we highly recommend reporting plugin conflicts to the developer of the conflicting plugin as they may have additional information vital to providing a resolution.
Hi Maybellyne,
Haha, great respons but it is an conflict between Yoast/ACF Yoast and Classic Editor.
So I think you could help too? Because when Yoast is disabled and Classic Editor enabled, it works fine, only the combination of yoast and classic editor makes it slow…
So I don’t think it is just a classic editor error?
Hi,
Performing a conflict check would help pinpoint which combination of plugins and themes might be causing this issue. You’ve mentioned that this slowness occurs with a default WP theme (such as TwentyTwenty) and Yoast SEO, Yoast ACF glue, ACF, and the Classic Editor plugin, correct?
Were you able to locate any slow queries from the Query Monitor plugin or detect any error messages from the browser’s console? We have to rule out other issues such as your specific server set-up (if it’s meeting the plugin requirements), or what sort of nested ACF group fields you are creating (how many?) to try and reproduce this issue.
Please do file a bug report (with the exact steps and all relevant information) as stated in this article – https://yoast.com/help/how-to-write-a-good-bug-report/
Hi,
1. Correct. TwentyTwentyOne, ACF Pro, Yoast SEO, Yoast ACF glue and Classic Editor (or Disbale Gutenberg) enabled. Same issue when using a function in functions.php to disbale Gutenberg.
2. No, I can’t find any slow queries with Query Monitor plugin. Or any errors in browser console.
3. I could send you an export of the ACF groups/fields if needed. Please let me know how to send it to you.
BUG REPORT
1. Install WordPress, TwentyTwentyOne theme, Yoast SEO, Yoast ACF Glue, ACF Pro and Classic Editor/Disable Gutenberg.
2. Set up (a lot of) (nested) ACF groups/fields
3. Create a page with these ACF groups/fields and fill in the fields.
4. Save the page (will already take a while).
5. Go to WP Dashboard
6. Go to Pages
7. Open the created page
I have added the bug report to GitHub. Hope you can help soon, thanks!
@jun-e-jay
As much as we hate to say it, your question goes beyond the technical expertise of me and my colleagues on the Yoast support team. This means we can’t give you a solid answer to your current issue from this open forum without thoroughly investigating your specific setup.
What’s next?
Since you’ve opened a GitHub issue explaining the problem our product team will assess the severity of this problem in relation to other open bug reports and new features. Based on their assessment, the bug report will be given a priority level. Our developers work on the highest priority issues first. Unfortunately, this means we cannot give you an estimate of when they’ll start working on your report.
If you have any further information that may affect the prioritization or help our development team solve this bug, please leave a comment or subscribe to the GitHub report to get updates on the issue.
Oh. Not the answer I was hoping for or expecting.
This issue is really bad and I think it only happened after an updatr somewhere in the last year, but I am not sure.
For now we don’t have any other choice then to go to Rank Math for our choice of SEO plugin.
I see there is already a very pong thread on Github about this issue, but it has been silent from Yoast since august…
Hi,
It looks like the GitHub issue you opened was closed as it was a duplicate of this issue. If you could add more relevant information to the issue, that may help with the investigation. Unfortunately, we are unable to provide a specific ETA as to when this would be addressed, relative to the prioritization of other bugs and enhancements in development. Sorry, that we couldn’t be of more help here.
We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.
