WPBakery's shortcode-based frontend output is treated as static; both the wp-admin editor and the front-end inline editor require a logged-in, capability-checked user, so neither was ever part of the public route surface.
WPBakery Page Builder can be resource-heavy at request time. WPBakery parses and renders its shortcode-based layouts into HTML on every dynamic request, which adds up on pages with deeply nested rows and columns.
We expect pages built with WPBakery Page Builder to load dramatically faster once served statically — that rendering cost is paid once at publish time, not on every visit.
Fully Static
Frontend page rendering is served from the static release.
The visual editor (backend and front-end inline) stays behind admin authentication.
None needed — WPBakery declares no public routes of its own.
No special setup — detected automatically once active.
WPBakery has no free wp.org distribution, so broad real-world testing is limited — this classification is rule-derived from the plugin's known architecture.
Static Shield Lite is free to install and inspects your actual plugins, not just what's publicly visible.
Get Static Shield
Tulapp