WordPress removed the classic editor and introduced the Gutenberg editor with version 5.0.
Since many users like the ease of the old classic editor, WordPress still provides a “Classic Editor” plugin to continue using the old classic editor gui.
However, Gutenberg is the future of WordPress, and you don’t have any other ways to start using it sooner or later.
Although Gutenberg Editor has drag-and-drop blocks, it loads content publishing very slowly.
Slow Gutenberg Editor is one of the main problems holding back users.
If you are struck by ever loading the Gutenberg editor, here are the explanations and fixes for speeding up the editor.
Is Your WordPress Editor Slow – Gutenberg Fix
Try the following to address the sluggish editor of Gutenberg:
- Check your internet connection
- Remove blocks you are not using
- Disable meta boxes
- Stop autosave and revisions
- Avoid large tables
- Use light theme and plugins
- Update WordPress
- Check your hosting
- Use classic editor
Verify the Internet Connection
Gutenberg will load several of the scripts and styles required for each block feature.
So, initial loading needs to have a proper internet connection.
If you have a really slow or interrupted link, you can see some error messages in the editor.
For example, a slow connection will lead to an autosave failure and will display a message like “Updating failed.”
Message of error: The answer is not a true JSON response.”
To ensure a secure link, make sure your Wi-Fi network is powerful enough or use network cables. Also, make sure you have unrestricted internet access without any blocking services. Otherwise, you’ll have to use a VPN to access unrestricted internet.
Autosave and Revisions should be disabled.
Autosave is a WordPress feature that allows you to save several copies of an article. You can get the most recent version from the autosaved revisions if you have a problem, such as an internet connection failure. Though this is a useful feature in terms of data recovery, saving the content in the editor every few minutes will slow you down. When autosave fails in the editor, you’ll get a JSON error, as seen in the image above.
The process named “Saving” can be seen running in the background. During this time, WordPress will disable the “Publish” or “Update” buttons, which will have an impact on your work. Many of us, in our opinion, don’t need this autosave function, which you can read about in our previous article on how to disable autosave and revisions.
In the Gutenberg Editor, disable blocks.
The Gutenberg editor comes with over 50 default blocks, and plugins like Yoast SEO can also add custom blocks. When the editor loads, it requires the resources for each block, which can take a long time. You don’t have to use any of the blocks on any of the entries. Fortunately, you can turn off the blocks you don’t use any longer:
Choose “Manage Block Editor” from the settings icon.
Disable all the blocks you never use on your site.
Meta Boxes on Post Editor
Are there a lot of meta boxes in your post editor? Many plugins and themes will have meta boxes in the post editor to enable you to set unique page options. The loading speed is affected by each meta box in the post editor. Plugins like Yoast SEO, WP Review, and WP Rocket, for example, all include meta boxes in the editor.
Choose “Options” from the dropdown menu when you click on the settings icon.
Disable meta boxes on the editor that you don’t want to load.
After disabling the blocks and meta boxes, you can feel the editor will load faster.
Avoid Large Tables
When you have a lot of content in your table, Gutenberg’s table block will take a long time to respond. Even though the performance has improved in recent versions, when you have a large table with a lot of content, it still takes a long time to type. Make sure the table has a reasonable number of rows and columns. Otherwise, create tables outside of the editor with separate table plugins like TablePress and embed them in the post using shortcode.
Use Light Theme and Plugins
This is a generic approach for a variety of WordPress issues. As previously stated, the majority of commercial themes will include meta boxes in the post editor. This will make it easier to have post-specific settings such as a different background, advertisements disabled, or different layouts. Revert to one of the default WordPress themes, such as twenty-twenty, if the Gutenberg editor is sluggish to load. If this does not fix the issue, you should consider modifying the theme or seeking assistance from the theme creator.
Many of us believe that plugins only affect the frontend page loading time. However, many plugins, like themes, add a lot of weight to the editor. The popular Yoast SEO plugin, for example, includes a meta box in the editor. It will take a long time to load, especially if your internet connection is slow. If it exceeds the acceptable level, you should think about replacing the plugin with something else.
Recent WordPress updates have primarily focused on improving the Gutenberg editor’s results. As a result, make sure to upgrade your website to the most recent WordPress edition. Use the new PHP version (>7.3) and keep your themes and plugins up to date in addition to core WordPress.
This will assist in resolving some of the previous issues as well as increasing the editor’s pace.
Check Your Hosting
We discussed how the hosting affects the admin pages in a previous post. Poor shared hosting can also affect the loading time of the Gutenberg editor, particularly if you’re editing content at a time when your site’s traffic is at its peak. Check with your hosting provider to learn more about how PHP files like admin.php use resources. In certain cases, depending on the amount of traffic and load on your server, you can upgrade your hosting.
Use Classic Editor
Unfortunately, some of the above remedies, such as changing the theme or removing a plugin, are not possible to enforce. If this is the case, you can try using the old editor again. Remember that WooCommerce and bbPress forms are not compatible with Gutenberg. Also, the classic editor interface will be used for the majority of custom post styles in WordPress. As a result, reverting to Gutenberg is a viable choice for online store and forum websites. This will ensure that all editors have the same classic gui.
However, since Gutenberg is part of the heart, the tools will still be loaded into the editor. To fully disable Gutenberg and use the classic editor, you will need to analyse and deque these files.
WordPress moved Gutenberg without fully preparing it, as many users argued. Even though there have been numerous changes to boost performance, it is unnecessary to load two editors when using WooCommerce or bbPress. If you have a larger blog or spend a lot of time editing posts, Gutenberg is the way to go. We hope that the above points discuss the causes of the sluggish Gutenberg editor and assist you in reducing the editor’s loading time.