Elementor's frontend output is treated as static with high confidence — the page builder renders regular HTML/CSS, and Static Shield serves that output directly. The editor itself (only reachable to logged-in admins) is treated as private, not part of the public surface.
Elementor can be resource-heavy at request time. Elementor re-renders its widgets and generates page-specific CSS on every dynamic request — that's real, ongoing PHP and CSS-generation overhead on top of plain HTML.
We expect pages built with Elementor 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, same as any other page.
The Elementor editor UI stays behind admin authentication — it was never part of the public route surface to begin with.
None needed — Elementor declares no public routes of its own.
No special setup — Elementor is detected automatically once active.
This classification is rule-derived from Elementor's known architecture, not from running an automated test against a live install. Elementor Pro (a separate plugin slug) isn't separately recognized — an install running Elementor Pro would fall back to generic, unclassified handling rather than this specific profile.
Static Shield Lite is free to install and inspects your actual plugins, not just what's publicly visible.
Get Static Shield
Tulapp