Why Your Website Is Slow, and Why It Is Probably the Page Builder

When somebody tells me their website is slow, the first thing I do is not look at the hosting or the images. I open the page, count what it loads, and nine times out of ten the answer is sitting there in the list. A page builder.

What a page builder actually costs you

Page builders promise that anyone can change anything. To keep that promise they load their own scripts and styles on every page, whether or not the page uses them. Then the plugins that came with the builder do the same. A slider library on a page with no slider. Three icon fonts for eleven icons. A form plugin’s entire front end on pages with no form.

A typical small business homepage built this way comes in at around three megabytes, over a hundred separate requests, and forty or so scripts. The same page rebuilt as a proper theme is usually under a megabyte, around thirty requests, and a handful of scripts. Nothing about the design has changed. Everything the page never used has gone.

Why that matters beyond the speed test

Google measures how quickly the first thing appears on screen and how long the page takes to become usable. Both feed into where you rank, and both are the numbers a page builder hurts most. On a phone on a patchy connection, which is where most local searches happen, the difference between under a second and nearly three is the difference between someone reading your page and someone pressing back.

How to check yours in two minutes

Open your homepage in Chrome, press F12, click the Network tab and reload the page. The two numbers at the bottom are requests and the total weight transferred. For a brochure homepage, over two megabytes or over eighty requests means the builder is doing most of the damage. If you see the name of the builder in the file list dozens of times, that is your answer.

What moving off it involves

Less than people expect. The layout, the copy and the photos all stay. The site is rebuilt as a theme where each section is a field the owner edits, rather than a block dragged around a canvas. Most of the work is deleting what was never needed. The client ends up with more control, not less, because changing a heading is typing in a labelled box rather than opening a builder and hoping nothing shifts.

Not every site needs it. If the site is small, rarely changes and is fast enough, leave it. If it is slow, the builder is nearly always why, and the fix is a known quantity.

I cover this on the web design page, and if you want somebody to look at yours and tell you plainly whether it is worth doing, that is what the £150 audit is for.