Elementor hosting: WordPress with a page builder
Elementor is a page builder for WordPress, and a page builder makes a site heavier than a classic theme: more PHP memory when editing, more scripts and more imagery when loading. Elementor itself recommends a generous memory limit; so choose a plan with 256 or 512 MB PHP memory. A current PHP version, Redis object caching, free SSL and the Jaan Performance Engine are included with every plan, and an Elementor site simply runs on shared hosting with us.
The basis is our WordPress hosting. What Elementor adds is mainly weight: the editor itself needs memory, and the pages you build with it load more styling, scripts and images than a lean theme. That is no problem as long as the hosting is built for it and you do not overload the site. Here is what an Elementor site asks of its environment and where it usually goes wrong.
What Elementor asks of its environment
A high PHP memory limit
The editor loads all widgets, templates and settings into memory at once. On a plan with too little PHP memory the editing screen hangs or a page is not saved. Choose 256 MB, and for a large site with many add-ons 512 MB.
A current PHP version
Elementor and its add-ons follow PHP development closely. A recent PHP version is faster and receives security updates; you choose the version per site yourself, so you can test first and then switch.
Image optimisation
A page builder site consists mostly of imagery: backgrounds, hero sections, icons, galleries. If those are not resized and compressed, the site is slow regardless of the server. Upload images at the size they are displayed and let the Jaan Performance Engine defer their loading.
Object caching
Elementor stores the layout of every page in the database and fetches it again on every view. Redis object caching keeps that data in memory, which makes a noticeable difference especially on a site with many pages and templates. It is included with every plan.
Which environment does Elementor belong on?
An Elementor site is first and foremost a WordPress site and belongs on shared hosting, on the same basis as our WordPress hosting but with a plan that has enough PHP memory for the editor. A VPS only comes into play if you manage dozens of sites, need your own server software or want shell access.
About shared hostingWhat most often goes wrong with Elementor
A separate widget plugin for every section
Hundreds of add-on packs with extra widgets exist around Elementor. If you install five of them for one widget each, every page loads the scripts and styles of all five. Choose one pack that does what you need, and remove what you do not use.
Animations and video backgrounds
A video playing in the background and elements floating in one by one look good in the editor. On a phone with a mediocre connection they cost seconds and visitors. Use them sparingly and never above the fold of the home page.
No caching
Without page and object caching, the server rebuilds every page builder page for every visitor, and those are heavy pages. Switch on the Jaan Performance Engine; it comes free with every plan and handles the caching together with Redis. Only after that is a slow site a question for us.