Divi's frontend output — both its classic shortcode engine and its newer block engine — renders complete HTML server-side with no client-side hydration, so page content is served static with high confidence. Three optional modules talk back to the server and are bridged individually: the Contact Form module, the Signup/Email Optin module, and (only when enabled) a WooCommerce cart-count badge in the Menu module. The Visual Builder itself stays admin-only and was never part of the public surface.
Divi can be resource-heavy at request time. Divi is one of the heavier WordPress page builders at request time — extensive per-page CSS generation and DOM complexity, on every single dynamic visit.
We expect pages built with Divi to load dramatically faster once served statically — that rendering cost is paid once at publish time, not on every visit.
Static + Bridges
Page rendering and Divi's generated CSS/JS are both served from the static release — the generated stylesheets are plain cached files, not a live endpoint.
The Visual Builder (front-end and wp-admin) stays behind authentication. Two optional, rarely-used features — Divi's built-in split testing and the Login module — are treated as inert by default since most sites never enable them; a site that does use either should expect a more dynamic classification.
The Contact Form module bridges through the page's own URL rather than a fixed endpoint, since it self-submits back to whichever page it's on. The Signup/Email Optin module bridges through admin-ajax.php with its own rate limit. A WooCommerce cart-count badge some Menu module setups enable is flagged as needing the same treatment, since no client-side refresh for it was found.
No special setup — Divi is detected automatically whether it's the active theme or installed as the separate Divi Builder plugin.
Divi is normally installed as a theme rather than a plugin — recognizing that required teaching the Compatibility Layer to profile the active theme at all, not just active plugins. This classification is rule-derived from reading Divi 5.11.1's actual source against a live install, not from running an automated end-to-end test — the Contact Form and Signup bridges in particular still need manual validation, since a real submission sends a real email.
Static Shield Lite is free to install and inspects your actual plugins, not just what's publicly visible.
Get Static Shield
Tulapp