If your hosting gives WordPress PHP 8.2 or newer and at least 256MB of memory (512MB is better), it will usually cope with Elementor. Bargain shared plans often don’t. The editor sits on a grey loading screen forever, you click Update and nothing saves, or pages load fine for visitors but the backend crawls. These get reported to us as “Elementor problems”, and a good share of the time the real cause is the hosting account underneath.
Elementor asks more of a server than a plain WordPress blog does, mostly while you’re editing. Cheap shared hosting can run a simple site well enough for visitors and still fall over the moment you open the builder.
What Elementor needs right now
Elementor publishes its system requirements, and they change as WordPress and PHP move on. At the time of writing (late 2026), they are:
| Requirement | Elementor’s figure |
|---|---|
| WordPress | 6.8 or later (latest recommended) |
| PHP | 7.4 or later, with PHP 8.3 or newer highly recommended |
| Database | MySQL 5.6+ or MariaDB 10.5+ |
| WordPress memory limit | 256MB minimum, 512MB recommended, 768MB for best performance |
| Editing device | Desktop browser (phones and tablets aren’t supported for editing) |
Elementor also notes that a site running WooCommerce or other plugins with their own demands may need 512MB just to avoid loading issues.
WordPress itself is moving the same way. WordPress 7.0 dropped support for PHP 7.2 and 7.3, and the WordPress hosting team’s compatibility page lists PHP 7.4, 8.0 and 8.1 as end of life, kept only for backward compatibility. In practice, if your host has you on anything older than PHP 8.2, ask why.
Our view: treat the “minimum” column as the point where things start breaking, not as a target. A business site with Elementor Pro, a forms plugin, an SEO plugin and some caching should be on a current PHP version with at least 512MB available.
Check your setup in five minutes
You don’t need to log into your hosting control panel for this. WordPress will tell you.
1. Site Health
In the WordPress dashboard, go to Tools > Site Health > Info. Open the Server section and note the PHP version and the PHP memory limit. Then open WordPress Constants and look for WP_MEMORY_LIMIT.
These are two different numbers. The PHP memory limit is what the server allows. WP_MEMORY_LIMIT is what WordPress asks for. If WordPress asks for 512MB but the server caps PHP at 128MB, you get 128MB.
The Status tab on the same screen will also flag an outdated PHP version as a recommended improvement.
2. Elementor’s System Info
Elementor has its own System Info screen in its admin menu. It shows your PHP version, memory limit, maximum upload size and whether any requirements are flagged. If you ever log a support ticket with Elementor, they’ll ask you for this report.
3. Note the plan you’re on
While you’re there, find out the plan name and provider. You need it to compare against what the host offers, and you need to know who holds the hosting login. If that’s “the guy who built the site in 2019”, read who should own your domain, hosting and logins before anything else.
What goes wrong on bargain shared hosting
The cheapest plans put hundreds of sites on one server and limit how much each can use. A few patterns we see when Elementor sites live there:
The editor never finishes loading. Usually a memory limit or a script timeout. The editor loads a lot at once, and if PHP runs out of memory part-way, you get a spinner or a blank panel.
Changes won’t save, or you get a “server error” on Update. Often memory again, or a security module on the server blocking the editor’s requests because they look unusual. Some hosts need to whitelist rules or adjust a setting. Elementor’s requirements page lists a few host-specific quirks of this kind.
The site slows down at random. A neighbour on the same server is having a busy day, and your site shares their CPU. You can’t fix this from inside WordPress.
Backups and updates fail part-way. Large backup jobs time out on plans with strict limits, which means you may not have the backup you think you have. That matters before any update, as we explain in updating Elementor safely.
Stuck on old PHP. Some bargain hosts leave accounts on old PHP versions for years, because moving them causes support tickets. Then a plugin update requires a newer version and the site breaks.
None of these mean shared hosting is always bad. A good shared plan from a decent host, with sensible limits and current PHP, runs a small Elementor site perfectly well. The problem is the $3 a month plan sold on “unlimited” everything.
Raising the memory limit
If Site Health shows WP_MEMORY_LIMIT below 256MB but the server’s PHP limit is higher, you (or whoever does your WordPress support) can raise WordPress’s request by adding this line to wp-config.php, above the line that says “That’s all, stop editing”:
define( 'WP_MEMORY_LIMIT', '512M' );
If the server’s own limit is lower, that line won’t help. You’ll need to ask the host to raise the PHP memory limit, or change it in the control panel if your host lets you (cPanel’s PHP selector often does). If the host won’t go above 128MB or 256MB on your plan, that’s your answer about the plan.
Edit wp-config.php only if you’re comfortable with it and have a backup. A typo in that file takes the whole site down.
Questions to ask your host
If you’re on the fence about your current hosting, ask these directly:
- What PHP versions do you offer, and how do I switch?
- What’s the PHP memory limit on my plan, and can it be raised to 512MB?
- Are there CPU or process limits per account? What happens when I hit them?
- How often are backups taken, how long are they kept, and can I restore one myself?
- Is support in Australia, and how fast do they respond?
- Where are the servers? (For a local audience, Australian servers help.)
Vague answers to the first three tell you most of what you need to know.
When it’s time to move
Moving hosts is worth it when you’ve checked the settings above, raised what you can, and the editor is still unreliable or the site still stalls. It’s also worth it if your host can’t give you current PHP.
Cheap hosting is a false economy for a site that brings in work. The difference between a bargain plan and a properly managed one is often a few hundred dollars a year, which is less than one lost job or a day of a developer’s time chasing a fault the host caused. For comparison, our own managed hosting is $25 a month + GST.
Run the Site Health check today and write down the two memory numbers and your PHP version. Numbers below the table above? Some plans can be bumped up with a support ticket and some can’t, and we can help you work out which yours is. Hosting is also one of the first things we look at when a site comes to us for WordPress and Elementor web design work.