Delivery
Prebuilt HTML vs Runtime Page Builders
The cheapest request is the one that only has to send a file.
Two different request paths
A runtime builder or CMS may authenticate a session, query content, run theme logic, and then send HTML, plus the scripts the theme expects. A static host sends the file that was built and checked.
Both can sit behind a CDN. Only one of them needed the CDN to hide the origin’s work.
Predictable HTML is easier to test
If the page is a file, the title, canonical, headings, and main landmark can be validated in the build. A runtime page can vary with plugins, experiments, and logged-in state.
We validate the output. We do not hope the theme still emits the same tags after an update.
Dynamic where it is actually dynamic
Search indexes, form posts, and inventory that changes by the minute can be endpoints. They should not force every marketing URL through the same runtime.
Static-first means the default path is a file. Exceptions are explicit.
Continue
Builder Subscriptions vs an Owned Website
How to compare the cost of WordPress, Wix, Squarespace, and page builders with a static site without pretending hosting is free.
Read →SEO Control on Static Sites
Why static sites give clearer SEO control than WordPress, Wix, Squarespace, and page builders, without fake ranking promises.
Read →Accessibility Inside Page Builders
Why WordPress, Wix, Squarespace, and page builders make WCAG 2.2 AA harder, and why static semantic HTML is the better base.
Read →