Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

WPBakery’s split CSS loading, introduced in version 9.0, divides its global stylesheet into element-specific styles and uses a page’s content to decide which styles to load. The goal is to deliver less unused CSS and reduce browser work. That may help some pages, but WPBakery’s published article does not include percentage-based test results, and enabling the feature is not a guarantee of faster performance on every site.

What split CSS loading changes

In a September 2026 article, WPBakery describes the change this way: “instead of always loading one large CSS file, styles are now split by element and loaded only when needed.” Rather than loading the same broad set of builder styles on every page, the feature aims to select styles based on the elements present on that page.

WPBakery says that “on most pages, up to 90%” of the CSS is unused. That is the vendor’s general assertion, not an independently documented measurement of every WPBakery site or a result from a published controlled test of version 9.0. The intended benefit is less unused CSS for the browser to download and process.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Will it make your WPBakery site faster?

It could reduce CSS delivered to pages that use only a limited set of builder elements, but the available article does not establish how much CSS or load time the feature saves. WPBakery reports preliminary reductions on pages with limited element sets and says full percentage-based results would be published alongside the 9.0 release; the article itself contains no such results. There is no basis in that article for quoting a specific payload or speed improvement.

Any practical effect depends on the pages and configuration on your site, including the elements they use, custom components, theme styles, and other asset optimization. Less CSS does not automatically translate into a noticeably faster page for every visitor. Treat split loading as a feature to evaluate, not a universal performance fix.

Which CSS loading modes does WPBakery offer?

WPBakery describes three modes: Legacy, Hybrid, and Optimized. Its article said Legacy was still the default when it was published and described a future switch to Hybrid as planned. That statement does not establish the default in every later release. Check the installed WPBakery version and its current settings before changing modes; release notes about CSS loading changes do not by themselves identify the setting active on every site.

WPBakery does not publish comparative numeric results for the three modes in the cited article. Assess them against the same practical criteria rather than assuming that a mode name predicts your outcome:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  • CSS delivered: Inspect the stylesheet requests and the styles actually used on representative pages.
  • Compatibility: Check the theme, custom elements, and any CSS optimization or caching tools your site uses.
  • Visual integrity: Look for missing or incorrect styling and flashes of unstyled content.
  • Site-specific results: Compare pages before and after the change under consistent conditions.

How to evaluate split loading on your site

WPBakery’s beta guidance recommends checking varied page types because configuration can affect results. Use a repeatable comparison, and include the kinds of pages your visitors actually use.

  1. Record the baseline. Note the current WPBakery version and CSS mode. Choose representative pages and capture their stylesheet requests, unused-CSS audit, and visual appearance before changing the setting.
  2. Cover different page shapes. Include a lean page and a complex page. If your site has them, also check WooCommerce pages, portfolios, and pages using custom elements.
  3. Change the CSS mode. Use the setting available in your installed version. The cited sources do not establish one universal UI path or current default, so follow the labels in your own installation.
  4. Repeat the same checks. Inspect generated stylesheet requests and unused CSS on the same pages, then compare the results with the baseline.
  5. Check rendering, not just reports. View pages after loading and watch for missing styles, layout changes, or flashes of unstyled content. Test interactive states where custom elements or store components are involved.
  6. Keep or revert based on evidence. If a page loses styling or the results are not beneficial, return to the previous mode and investigate compatibility before trying again.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

What to check with custom elements

WPBakery recommends using standard WordPress enqueue functions and conditional asset loading for custom elements. WordPress’s theme guidance also describes loading block styles only when those blocks are used. These are useful asset-management practices, but they do not establish that every extension will work automatically with WPBakery’s split-loading feature. Test custom elements on the pages where they appear, and confirm that their required styles load reliably.

Sources and evidence

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.