Defensive nesting
Every element wrapped in extra containers so the tool stays flexible for whatever gets dragged next, whether needed or not.
WHY NOT · PAGE BUILDERS
We do not build with page builders
A page builder is a visual, drag-and-drop tool for arranging a page without writing code: Elementor and Divi on WordPress, or the built-in editors inside Wix, Squarespace and Webflow. It generates the HTML and CSS behind the scenes, wrapping elements defensively so the layout can accommodate anything a person might drag next.
THE MECHANISM
Why the generated code costs more than it needs to
Not a criticism of the editing experience. A description of what it produces underneath.
Inline styles alongside a global stylesheet
Styling applied per-element to support visual editing, duplicating and bloating what a shared stylesheet would otherwise handle once.
Unused CSS shipped regardless
The builder's full style library loads whether or not a given page uses more than a fraction of it.
WHERE WE SIT
Under 1,400 DOM nodes, by rule
Our own performance target, applied to every page.
Hand-written markup means a heading is one tag, not one tag wrapped in four defensive containers a builder added in case something else got dragged next to it. Every page we ship is built against a stated DOM node and page weight budget, not left to whatever a visual editor happened to generate.
THE ONE EXCEPTION
When a page builder is a reasonable tool
Publishing what we will not do includes saying when the alternative is fine.
For a non-technical person roughing out a layout privately before handing it to a developer, a page builder is a fine prototyping tool. It stops being reasonable the moment the generated markup is the thing actually shipped to every visitor of a production page.
STRAIGHT ANSWERS
Questions about this position
The ones that come up when people notice we say this plainly instead of hedging it.
A visual, drag-and-drop tool for arranging a page without writing code: Elementor and Divi on WordPress, or the built-in editors inside Wix, Squarespace and Webflow. It generates the HTML and CSS behind the scenes so a person can move blocks around visually.
A page builder cannot know what a person will drag next, so it wraps every element in extra containers to stay flexible for any arrangement. A heading that needs one tag in hand-written code often sits inside four or five nested wrapper elements a page builder adds defensively.
It shows up as more DOM nodes for the browser to build and more CSS to load and apply, both of which slow down rendering. Our own performance target keeps every page under 1,400 DOM nodes; a page-builder page frequently carries several times that for the same visible content.
For a non-technical person prototyping a rough layout privately before handing it to a developer, sure. Not for a public-facing production page, where the generated markup becomes the thing actually shipped to every visitor.
Send us your website address. We will tell you what is wrong with it.
Two days, no charge, no obligation, and you keep the report whether or not you hire us.