Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Speed & performance · Info

Does WPBakery Slow Down Site? The Short Answer

Does WPBakery Slow Down Site? The Short Answer

Short answer

WPBakery does add some CSS, JavaScript and extra HTML to pages, so it can slow a site down a little. On a well-configured site with caching the effect is usually modest, and heavy add-on packs, sliders, large images and weak hosting cause most real slowdowns.

Key takeaways

  • WPBakery adds some overhead, like every page builder.
  • Add-on packs and sliders often cause the biggest slowdowns.
  • Page caching removes most of the shortcode processing cost.
  • Test your own pages before blaming the builder.
  • Switching away means rebuilding pages, since shortcodes stay behind.

Does WPBakery slow down your site?

WPBakery adds some weight to every page it builds, but on a well-configured site the slowdown is usually modest. Heavy add-ons, sliders and nested layouts cause most of the real speed problems.

Like every page builder, WPBakery trades some speed for convenience. It loads its own CSS and JavaScript and wraps content in extra HTML so the layout can work.

That overhead is real but rarely the whole story. A simple WPBakery page on good hosting with caching can load quickly, while a complex one with several add-on packs can be slow.

So the honest answer is that WPBakery can slow a site down, and how much depends far more on how it is used than on the plugin itself.

Why do page builders like WPBakery add weight?

Page builders add weight because they load their own stylesheets and scripts and wrap each row, column and element in extra HTML containers.

WPBakery stores layouts as shortcodes inside your post content. When a page loads, WordPress has to process those shortcodes and turn them into HTML, which takes a little server time.

The output also tends to have deeper nesting than a hand-coded or block-based page. Each row and column adds wrapper elements, and a long page can end up with a large DOM.

Large DOMs make the browser work harder to lay out and paint the page. The Lighthouse guidance on excessive DOM size explains why this affects responsiveness.

Server time matters as well. Processing many shortcodes on every uncached request adds a small delay, which grows on slower hosting or during traffic spikes.

None of this makes WPBakery unusable. It simply means a WPBakery page starts with more to download and process than a plain one.

What actually makes a WPBakery site slow?

The biggest slowdowns usually come from third-party add-on packs, sliders, large images and heavy hosting limits, not from WPBakery's core features alone.

FactorImpact on speedWhat to do
WPBakery core CSS and JSLow to moderateKeep it, but optimize delivery
Third-party add-on packsOften highRemove packs you barely use
Sliders and carouselsHigh, especially above the foldReplace with a static image
Deeply nested rows and columnsModerateSimplify layouts
Unoptimized imagesHighCompress and size images
Weak or overloaded hostingHighUpgrade or tune hosting
No page cachingHighAdd a caching plugin or host cache

Add-on packs are worth singling out. Each one can load its own CSS, JavaScript, icon fonts and animation libraries on every page, even where you only use one element.

Themes bundled with WPBakery can add to this. Many multipurpose themes ship WPBakery alongside several other plugins, sliders and demo features that all load assets.

A quick audit helps here. List every add-on and the elements you actually use from it, and you will often find packs that can go without changing the design.

Icon fonts are another hidden cost. Several add-ons may each load a full icon library when the site only shows a handful of icons.

How do you measure WPBakery's impact on speed?

Test a WPBakery page and a similar page built with the block editor using the same tools, so you can see the difference on your own server.

Run both through PageSpeed Insights and note Largest Contentful Paint, Total Blocking Time and the page weight. Test the mobile results too, since they are usually worse.

Look at the waterfall in your browser's developer tools to see which files load. Filter by the plugin folder names to see what WPBakery and each add-on contribute.

The free Query Monitor plugin shows which plugins add the most database queries and server time. Our guide on finding slow plugins covers a full process.

Use the same test conditions each time and run each test a few times. Single results can vary quite a lot.

How can you make a WPBakery site faster?

You can speed up a WPBakery site by adding page caching, trimming add-ons, simplifying layouts, optimizing images and delaying or removing unused scripts.

  1. Turn on page caching through your host or a caching plugin.
  2. Remove add-on packs you use for only one or two elements.
  3. Replace sliders above the fold with a single optimized image.
  4. Flatten layouts with fewer nested rows and inner columns.
  5. Compress images and serve modern formats such as WebP.
  6. Use a performance plugin to remove unused CSS and delay JavaScript.
  7. Keep WPBakery, the theme and PHP up to date.

Caching does the heaviest lifting. It stores the finished HTML, so WordPress does not have to process shortcodes on every visit.

For unused assets, our guides on removing unused CSS and reducing unused JavaScript are good next steps. Test after each change, since delaying scripts can break builder animations.

Hosting matters too. A builder-heavy site on cramped shared hosting will struggle under traffic, and our guide on how hosting affects WordPress speed explains why.

Is WPBakery slower than Elementor or the block editor?

The block editor usually produces the lightest pages, while WPBakery and Elementor both add builder overhead, and real-world results depend more on setup than on the brand.

Gutenberg blocks output fairly clean HTML and load only the styles each block needs on many setups. That gives them a head start on speed.

Elementor has added performance features over recent releases, and our explainer on Elementor performance settings covers them. Comparing the two builders fairly means testing the same layout on the same host.

For a wider view of builder trade-offs, see our comparison of Gutenberg versus page builders.

Should you switch away from WPBakery for speed?

Switch only if testing shows WPBakery is the main bottleneck and you can afford the rebuild, because moving away from a shortcode builder takes real work.

When you deactivate WPBakery, its shortcodes stay in your content. Pages then show raw text in square brackets until you rebuild them, which the WordPress Shortcode API documentation helps explain.

For a small site, rebuilding key pages in the block editor can be worth it. For a large site, optimizing the current setup is often the better first step.

If you decide to move, our guide on converting WPBakery to Elementor covers one migration path. Always rebuild on a staging copy first.

Is WPBakery still a reasonable choice?

WPBakery is still a workable builder for many sites, especially ones already built with it, as long as you keep add-ons lean and use caching.

New projects have more options now. The block editor and newer builders may give you lighter pages with less lock-in.

If you are staying with WPBakery, our guide on how to use WPBakery Page Builder covers the basics, and the official WPBakery website lists current features and licensing. Check there for up-to-date details, since plans and features change.

Frequently asked questions

Is WPBakery bad for SEO?

Not directly. Search engines can read WPBakery pages fine. Speed and page experience can suffer if the site is heavy, which may affect rankings indirectly. A lean WPBakery setup with caching and optimized images can still perform well in search.

Is WPBakery faster than Elementor?

There is no fixed answer. Both add builder overhead, and results depend on the layout, add-ons, theme and hosting. The fairest way to compare them is to build the same page with each on the same server and test both.

What happens if I deactivate WPBakery?

Your pages will show raw shortcodes in square brackets wherever WPBakery elements were used, because WordPress no longer knows how to turn them into HTML. You need to rebuild those pages or use a cleanup tool before deactivating it on a live site.

Does a caching plugin fix WPBakery speed issues?

Caching fixes a large part of the server-side cost, because pages are stored as finished HTML. It does not reduce the CSS, JavaScript or image weight the browser downloads, so you still need to trim add-ons and optimize assets.

Sources

  1. WPBakery Page Builder WPBakery
  2. Avoid an excessive DOM size Chrome for Developers
  3. PageSpeed Insights Google
  4. Shortcodes WordPress Developer Resources
  5. Query Monitor WordPress.org Plugins

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.