Jump to a section6

Page builders solved a real problem: they let people without coding knowledge build pages. The cost of that convenience, however, is paid on every visit, by every visitor.

Where the weight comes from

A page builder has to be ready for anything: columns, carousels, accordions, animations, forms. It does not know in advance what you will use, so it loads a generous set of styles and scripts on every page, whether the page needs them or not.

On top of that, the layout is built from layers of nested containers. What could have been a section with three cards becomes a structure many levels deep, each with its own classes and inline styles.

What changes with a block theme

  • Only what the page uses gets loaded. Block styles are added on demand.
  • The markup is cleaner. Fewer levels mean less for the browser to compute on every resize or scroll.
  • The design lives in one place. Colours, fonts and spacing are defined in `theme.json` and applied everywhere, instead of being set page by page.
  • Editing stays visual. The native editor does what the builder did, for the text and images inside the content.

What I measured on a real case

Migrating this website from a builder-based theme to a block theme written from scratch, the home page weight dropped from about 1.6 MB to about 220 KB, and first contentful paint fell from over 6 seconds to roughly one second, under simulated mobile conditions. It is not magic: the same information, delivered with far less ballast.

The largest saving did not come from code, but from images served at the right size and from dropping effects that were recalculated on every frame.

When a builder is still the right choice

Honestly: it does not always have to go.

  • You have a team that frequently builds campaign pages and is already used to it.
  • The site is small, traffic is small and speed is not a business problem.
  • You depend on an ecosystem of extensions with no native equivalent.

Otherwise, for a presentation website that has to stay fast and maintainable for years, a block theme is the healthier choice.

How the move is done, step by step

  1. Inventory the pages and the section types that are actually used.
  2. Build the theme: `theme.json` for global styles, templates for page types, parts for header and footer.
  3. Move the content, not the builder’s markup. This is where the ballast is lost.
  4. Check every page, on mobile and desktop, before deactivating the builder.
  5. Keep the old theme installed for a while, as a quick way back if something turns up.

A detail that is often forgotten: content built with a builder frequently lives in the builder’s own data, not in the page content. Deactivate it without moving the content and the pages come out empty.

Is it worth it

A page builder is a tool, not a sentence. But if your site is slow, hard to maintain and full of options you never use, a block theme gives you back control, speed and calm updates.

Want to see whether it is worth it in your case? Write to me.