We do not recommend that bloggers use pagebuilders to create pages on their website, and we don’t offer support for it.
Below is an opinionated take on pagebuilders, and why we don’t support it. As always, bloggers are free to customize their theme in any way they see fit, if they’re willing to take on the burden of maintaining those customizations.
In addition to adding an unnecessary layer of complexity, they don’t allow you to do anything that you can’t do with a classic editor.
As always, we recommend asking: why am I making this change?
Unless you can draw a direct correlation between using a pagebuilder to build a conversion-optimized page that will immediately boost your revenues by a significant number, it’s best not to waste time on it.
Heavy Up-Front Investment
While creating pages can be quicker once you’ve invested in learning how to use it (40+ hours), we’ve never actually seen a page built that offers any sort of user-benefit that justifies this investment.
The “Block Editor” (codename Gutenberg) release from WordPress is a direct attack on pagebuilders, providing what will be a similar pagebuilding experience to the above.
There’s been some good arguments that the pagebuilders will always be more useful for the top 10%-20% powerusers, who make 3-4 landing page variations per day, and for whom a 5% increase in conversions results in thousands of dollars.
But that means 80%-90% of their market (non-power-users) will disappear. With that much of the market drying up, revenues will plummet and the industry will be forced to cut back. This will cause customer support to suffer, and more people to abandon, leading to a death spiral. If this happens, every page built will have to be manually migrated and rebuilt.
Pagebuilders make transferring content difficult. They often store content in shortcodes, code blocks, or custom post types, fragmenting the page content. This means the content of a page may be hidden across multiple areas, rather than directly in the standard classic or block editor.
You can check pagespeed at https://developers.google.com/speed/pagespeed/insights/
Then there’s the issue of making it play well with optimization plugins like WP Rocket. Lazyloading, caching, and defering are critical to food blogs in 2019 and in the future, and the pagebuilder may or may not have compatibility with performance plugins in mind.