That’s already clear even for WordPress newbies. Moreover, the vast majority of builders are shortcode-based and their parsing is a highly processor-intensive operation. Complex layouts with tons of content can take much more time to render pixels to screen; the more complicated styles, the more time is taken for painting them.
For WordPress page builders, the measure of speed comes with 2 aspects:
- Firstly, the speed of editing process (inside the builder): how fast the builder is loading, how fast the content modules are loaded and added, and sometimes, how fast the user loses patience staring at a preloader.
- Secondly, how long it takes to load the site page created with the builder. While the first aspect is more about providing a happy user experience, the second one is a significant SEO factor. The backend of the builder should be loaded maximum quickly and at least the basics of page speed rules and recommendations should be taken into account.
For example, one useful strategy is performed by the developers of Elementor page builder: to speed up the loading time of content created with the builder, CSS generated by Elementor are saved to external minified CSS files, therefore CSS markup is processed much faster. A great way to lighten the source code and load the page faster.
There are too many external factors that can worsen a website SEO. The page builder as a major plugin of many websites that use it should not be one of them.
5. Well-coded plugin
Taking into account that builders oftentimes take a role of main content keepers, nobody wants to have a buggy overloaded plugin to host their content. Nobody wants to have a site that takes forever to load because of one plugin. That’s why an “extremely well-coded” plugin is becoming something vendors emphasis in their advertising more often. And this is what users pay attention to, even without being able to properly check whether it’s true.
To recap, as well as it’s significant to leverage coding standards for page builder plugins, builder creators may invest more time in educating users providing real examples on what they mean by a “well-coded product”. Or they can invite to discuss some critical topics and start some behind the scene talks.