Why is the Gutenberg block editor better for speed?

Gutenberg Block Guides

Why is the Gutenberg block editor better for speed?

1

Pagebuilders add bloat.

Front-end performance impacts visitor user experience (UX). Site performance is affected by CSS styles, JavaScript files, and more. WordPress core, the theme and plugins affect load time, too.

The downside is pagebuilders create more bloat and unnecessary code in site pages. Pagebuilders add more weight to the website.

It’s a trade off: ease of use versus slower page speed and low-quality page markup.

Why is the Gutenberg block editor better for speed?

With the block editor, CSS styles are only loaded for blocks used on a page. This selective activation reduces the amount of CSS needed. This increases performance efficiency.

In Gutenberg releases prior to 10.1, styles for blocks were enqueued in a single file causing extra page load. Today, only what’s necessary is loaded when content is viewed.

Most blocks have fairly small stylesheets. These are inlined. Including everything in a single request further improves performance. This is considered good practice for speed.

Inlining CSS code helps users and service providers because it lowers the number of HTTP Requests. The website then loads faster than using an external CSS file.

Most blocks have fairly small stylesheets. These are inlined. Including everything in a single request further improves performance. This is considered good practice for speed.

Inlining CSS code helps users and service providers because it lowers the number of HTTP Requests. The website then loads faster than using an external CSS file.


 

More Block Editor Goodness