Development · 5 min read
Page builders vs custom themes: what's really slowing your site down.
Short answer
Page builders aren't automatically slow, and custom themes aren't automatically fast. Most slow WordPress sites are caused by poor hosting, oversized images, too many plugins and third-party scripts, and bloated layouts. A well-built page builder site can pass Core Web Vitals; a careless custom theme can fail them.
Page builders vs custom themes: the debate
Ask a room of developers about page builders and you'll get strong opinions. One side says tools like Elementor, Divi and WPBakery create bloated, slow websites. The other says they let teams build and edit quickly without waiting for a developer.
Both sides have a point, and both miss the bigger picture. When we audit slow websites, the page builder is rarely the only problem, and often not the biggest one. Speed comes from dozens of decisions, and page builders are just one of them.
How website speed is measured
Before blaming any tool, it helps to know what "slow" means. Google measures real-user experience with three Core Web Vitals (opens in a new tab).
| Metric | What it measures | Good score |
|---|---|---|
| Largest Contentful Paint (LCP) | How quickly the main content appears | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How quickly the page responds to taps and clicks | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | How much the layout jumps while loading | 0.1 or less |
INP replaced First Input Delay as a Core Web Vital in March 2024. It's the metric that most often exposes heavy JavaScript, including the scripts some page builders and plugins load.
The 7 real causes of a slow website
In our experience, these are the most common reasons a site is slow, roughly in order of how often we find them.
- Cheap or overloaded hosting. If the server takes a second to respond, nothing else can make the page fast. Check Time to First Byte first.
- Oversized images. A 4 MB photo scaled down to a 400-pixel card is still a 4 MB download. Resize, compress and serve modern formats like WebP or AVIF.
- Too many plugins. Each plugin can add database queries, CSS and JavaScript to every page, even pages that don't use it.
- Third-party scripts. Chat widgets, tracking pixels, heatmaps and embedded videos often cost more than the whole theme.
- Bloated layouts. Deeply nested sections, columns and wrappers create a large DOM that the browser must calculate and paint.
- Unoptimised fonts. Several font families and weights, loaded from different sources, delay text and shift layouts.
- No caching. Without page caching and a CDN, the server rebuilds every page for every visitor.
Notice that page builders only appear directly in one of the seven. They can contribute to others, but they're rarely the whole story.
Where page builders do cost you
Page builders are general-purpose tools, so they ship code for features you might not use. Older builders in particular wrap every element in several layers of markup, which inflates the DOM and the CSS needed to style it.
The bigger risk is how they're used. Because page builders make it easy to add sections, animations, sliders and widgets, it's easy to keep adding. A homepage with fifteen sections, three carousels and entrance animations on every element will be slow on any platform.
Modern page builders have improved a lot. Elementor's flexbox containers, for example, produce much leaner markup than its older section and column structure, and most builders now load assets only where they're needed.
Where custom themes win, and where they don't
A custom theme ships only the code your design needs. Done well, that means smaller pages, fewer requests and markup that's easy for search engines and assistive technology to read. It's the approach we choose when performance is critical or the design is highly specific.
But a custom theme is only as good as the developer who built it. We regularly see custom themes that load entire frameworks for one slider, ignore image sizes, or are so rigid that editors resort to pasting in images of text. And custom themes can make everyday edits harder, which has its own cost.
How to choose between page builders and a custom theme
- Choose a page builder when your team needs to create and edit layouts often, the design uses a consistent set of components, and speed of change matters more than the last few milliseconds.
- Choose a custom theme when performance is a competitive advantage, the design is highly bespoke, or the site is large enough that every kilobyte multiplies across thousands of pages.
- Choose a hybrid when you want both: a lightweight custom theme with a small set of editable blocks, or a page builder limited to a design system with global styles.
Whatever you choose, set rules. A short list of approved components and a page weight budget will do more for speed than any single tool.
Fixes that make the biggest difference
If your site is slow today, you probably don't need a rebuild. Start with these, in this order.
- Move to good hosting with server-level caching and a CDN.
- Compress and resize images, and lazy-load anything below the fold.
- Remove plugins you don't need, and replace heavy ones with lighter alternatives.
- Audit third-party scripts and delay the ones that aren't essential.
- Simplify your heaviest templates, starting with the homepage.
- Limit fonts to two families and the weights you actually use.
Measure before and after each change with PageSpeed Insights, and check the field data for real users, not just the lab score.
The short version
Page builders aren't the villain, and custom themes aren't a magic fix. Most slow sites are slow because of hosting, images, plugins, scripts and layout bloat. Fix those first, then choose the build approach that fits how your team works.
Frequently asked questions
Are page builders bad for SEO?
No. Search engines don't penalise page builders. What matters is the result: fast pages, clear headings, crawlable content and good Core Web Vitals. Page builders can deliver all of these when used with discipline.
Will switching to a custom theme make my site faster?
Not necessarily. If your site is slow because of hosting, images or third-party scripts, a new theme won't fix it. Measure first, fix the biggest causes, and rebuild only if the theme is the real bottleneck.
How do I find what's slowing my site down?
Start with PageSpeed Insights and check the field data from real users. Then look at server response time, the largest images and the scripts that block the page, using the waterfall in your browser's developer tools.
Do too many plugins slow WordPress down?
Quality matters more than the number. One badly built plugin can do more damage than ten lightweight ones. Remove what you don't use, and check what each remaining plugin loads on every page.
Can you speed up my existing website?
Yes. We start with a performance audit, fix the biggest problems first, and measure the improvement in Core Web Vitals before and after.
Need help with this?
Slow website? We'll find what's really holding it back.
