Rebuilding a page-builder site as static HTML
A concept teardown — taking a representative page-builder business site and rebuilding it to see what the weight actually consists of.
This is a self-initiated concept piece, not client work. No client names, results or metrics are claimed anywhere on this page.
The premise
A self-initiated teardown. We took a representative small business site of the kind we see constantly — a page builder, a theme, a dozen plugins — and rebuilt the same content and layout from scratch to find out what the weight was actually made of.
No client is named because there is no client. This was run against a site we built ourselves to be typical.
Where the weight was
The revealing part was not the total. It was the breakdown:
- Layout CSS for every layout the builder supports, not the four in use
- Three separate icon font files, from three plugins, for eleven icons
- A slider library on a page with no slider
- jQuery, twice, at different versions
- Unscaled hero images
The rebuild
Same content, same layout, same fonts. Static HTML, one stylesheet, images converted to modern formats and sized to their containers, icons inlined as SVG.
What it demonstrates
- Page-builder weight is mostly unused code, not content
- Most of the win comes from images and dead scripts, before any framework decision
- A rebuild is not always necessary — but when it is, this is why
Honest limitations
A synthetic case. A real site carries real constraints: existing content, existing integrations, and people who need to keep editing it. The percentages here are illustrative of a pattern, not a promise about your site.
Let us look at what you have.
Send us your current site and what you want it to do. We will tell you what is worth fixing and what is worth rebuilding — before anyone talks about money.