Claude Code analysis

Describe the Problem I'm sure the team did the same and used AI to analyze the Elementor code base :smile: Info: I've used the compiled version, not the source from the repo Of course it still needs to be verified if everything is true but I'm sure some are valid and need to be fixed to improve performance. E.g. I've turned of AI in the user settings, why does it still load the AI/MCP stack? Elementor 4.2.0 — Biggest Editor Performance Issues TL;DR: The editor's three dominant costs are (1) rebuilding the entire widget/control configuration in PHP from scratch on every single editor open — with zero persistent caching anywhere in that path, (2) shipping and booting two complete UI frameworks plus a ~2.4MB always-on AI/MCP JavaScript stack, and (3) re-serializing and re-rendering the whole document twice on every autosave. 1. No caching of widget/control config — full rebuild on every editor open (PHP, highest impact) Every time the editor ope…