Website creationElementor hosting

Elementor hosting: our server stack for fast sites

Server, caches, CDN, database, security: our setup for hosting Elementor sites, and the questions to ask a hosting provider.

Mehdi B.

Co-founder · SEO & digital strategy

Elementor hosting: our server stack for fast sites
In brief

An Elementor site needs more resources than a stripped-down WordPress site, and it is the hosting that decides whether it stays fast. We install it on a Debian 13 VPS with Nginx, PHP-FPM, Redis, FlyingPress and a CDN, with scheduled tasks run by the system and an administration area closed to the public. Above all, check the PHP version, the allocated memory and the object cache your host offers.

Take the head of a Lausanne accounting firm whose website was rebuilt three years ago, and who asks: “My Elementor site is slow. Is it Elementor’s fault or my hosting’s?” Our answer fits in one sentence. An Elementor site is more demanding than a stripped-down WordPress site, and it is the Elementor hosting, meaning the server and the caching layers around it, that decides whether it stays fast or drags.

We do not use Elementor on all of our web design projects. When it fits the client’s needs, however, we install it on a setup that we control from end to end. We describe it here layer by layer: the server, the software that builds the pages, the caches, the delivery network placed in front of the site, the scheduled tasks and security. The aim is not to turn you into a system administrator. It is to give you the right questions to ask whoever hosts your site.

Why Elementor hosting has such an impact on speed

Elementor is a page builder: it lets you compose a page by assembling blocks, without writing code. That flexibility has a technical cost. Each page combines many elements, and WordPress has to query its database, run PHP code and assemble the result before sending it to the visitor. The longer the server takes to do this work, the longer the visitor waits in front of a blank page.

The publisher acknowledges this in its system requirements. Elementor runs on PHP 7.4 and above, but it “strongly recommends” PHP 8.3 or newer. It asks for 256 MB of PHP memory for Elementor and Elementor Pro alone, recommends 512 MB and cites 768 MB for the best performance. A site that adds WooCommerce, the online shop extension, may need 512 MB to avoid loading problems. On the database side, the minimum is MySQL 5.6 or MariaDB 10.5, and WordPress 6.8 or newer.

These values show what is at stake. Hosting that cannot reach them will hold the site back, however carefully it was built. It is therefore the first thing to check on an existing Elementor site.

The server: a Debian VPS, sized with headroom

Our base is an OVHcloud VPS, in other words a virtual server whose resources are reserved for us, with no neighbours drawing on the same memory. We chose it because we know it well and it leaves us in control of the whole configuration. For the heaviest sites, we move to an OVHcloud dedicated server, meaning an entire physical machine. Depending on the project, we also host with Infomaniak, a hosting provider based in Geneva.

Pay-as-you-go cloud has its merits, but it is designed for workloads that vary sharply from one hour to the next. A brochure website or an online shop run by an SME in French-speaking Switzerland usually has a fairly steady load. Paying for that elasticity then makes little sense, which is why we prefer a dedicated server when a site grows.

The operating system is Debian 13, code-named “trixie”, the stable release published on 9 August 2025. The Debian releases page gives Debian 12 an end of life of 11 July 2026, so a new server is launched today on Debian 13.

For sizing, we start from at least 6 virtual processors and 12 GB of memory, even for a modest site. This headroom absorbs visit peaks. Above all, it lets us run the test copy of the site (the “staging” site) on the same server, with exactly the same configuration. A change validated in testing therefore behaves the same way once live. When a database becomes large, we add a separate storage volume and move the database onto it, so that its reads and writes do not slow down everything else.

Nginx, PHP-FPM and the database: the engine that builds the pages

The web server, the software that receives requests from browsers, is Nginx in our setup. Its documentation describes an architecture made of one main process and several worker processes, and states that 10,000 idle HTTP connections kept open use about 2.5 MB of memory. For a site that receives many visitors at the same time, this lightness matters.

Behind Nginx, WordPress code is run by PHP-FPM, the PHP process manager. Its documentation presents it as an implementation aimed mainly at heavily used sites. It lets you configure how processes are started (permanently, on demand or dynamically) and log scripts that are unusually slow. We adjust these settings to the actual load of each site. The same documentation also reminds us that PHP-FPM must never be reachable from an untrusted network, a point to check on any server.

We install the latest stable version of PHP. According to the official PHP calendar, security fixes end on 31 December 2026 for PHP 8.2, at the end of 2027 for PHP 8.3, at the end of 2028 for PHP 8.4 and at the end of 2029 for PHP 8.5. In our article on the PHP2Shell vulnerability, we explained what it costs to stay on an old version.

For the database, we install MariaDB or MySQL, at the client’s choice. The setting that matters most is InnoDB’s “buffer pool”, the memory area where the database keeps the most frequently used tables and indexes. The MySQL documentation states that, on a server dedicated to the database, up to 80% of memory is often allocated to it. On our servers, the database shares the machine with PHP and Nginx, so we size it lower. Some guides still recommend enabling the “query cache”, MySQL’s query cache. It was removed in MySQL 8.0, however, the publisher having found that it scaled poorly on multi-core machines.

Three layers of cache, and the order in which to clear them

A cache keeps a result that has already been computed so that the work is not redone on every visit. On an Elementor site, we stack several, and each has its own role.

The first is the object cache, handled by Redis. The WordPress documentation specifies that its object cache is not persistent by default: data stays in memory only for the duration of a request. Redis, a database that works in memory, keeps these results available from one page to the next. WordPress thus avoids asking MariaDB or MySQL the same questions over and over.

Next comes Elementor’s own cache. Its “Element Caching” feature stores in the database the HTML code produced by each widget, so that it is not recomputed on every display.

Last is the page cache, which we entrust to FlyingPress, installed on all of our Elementor sites. It keeps a ready-to-serve version of each page and reloads it in advance when the content changes. It also minifies CSS and JavaScript files, defers the loading of images, videos and iframes located further down the page, and cleans up the database. The extension is paid: its public price list, expressed in dollars, starts at $59 per year for one site. FlyingPress recommends making it the only optimisation extension on the site, and we follow that advice. We are often asked about LiteSpeed Cache. Its page cache, however, requires a LiteSpeed environment (LiteSpeed server or QUIC.cloud network), which does not match our choice of Nginx.

This stacking calls for discipline. After a change, clearing a single level is not enough, and the order matters: Redis first, then Elementor, then FlyingPress, and finally the CDN. Each layer is in fact rebuilt from the one beneath it. If the page cache is cleared before the object cache, FlyingPress regenerates its pages from outdated data, and the old version stays online.

Cloudflare or Bunny CDN: the layer placed in front of the server

A CDN, or content delivery network, is a set of distributed servers that keep a copy of the site’s files as close as possible to visitors. Cloudflare is in place on all of our Elementor sites, and for file delivery we often prefer Bunny CDN.

The reason is first of all economic. Bunny CDN bills by usage: its public price list, expressed in dollars, shows $0.01 per gigabyte for Europe and North America, with a minimum of $1 per month. Cloudflare’s plans are flat-rate: the Free plan is free, the Pro plan costs 20 US dollars per month billed annually (25 billed monthly) and the Business plan 200 dollars per month (250 billed monthly). A site delivering 50 gigabytes per month from Europe would thus pay 50 cents, so the monthly minimum of $1.

Cloudflare does more than speed up the site. Its web application firewall (WAF) is included in all plans. Its rate-limiting rules, which block a visitor or a bot sending too many requests in a short time, number one on the Free plan, two on Pro and five on Business. Its custom rules also make it possible to block the traffic of an entire country. We use them to keep out regions that have no connection with the client’s business and that only bring bots. This setting is decided case by case, however: an exporting SME obviously must not close the door on its own customers. Finally, Cloudflare compresses the files sent to visitors, using Brotli by default on the Pro and Business plans.

That leaves APO, Cloudflare’s “Automatic Platform Optimization”, which serves an entire WordPress site from Cloudflare’s network. It is included in the Pro and Business plans and costs $5 per month on the Free plan. It can help on a brochure website. On an online shop, however, we never enable it. Cloudflare nonetheless states that WooCommerce is compatible, and APO bypasses the cache as soon as it detects certain cookies, such as those starting with “woocommerce_” or “wordpress”. The bypass relies on a list of prefixes, though. A shop extension that names its cookies differently may then see a personalised page, a basket for example, served from the cache. On a site that takes orders, we prefer not to take that risk.

Scheduled tasks, WordPress settings and performance monitoring

WordPress runs its scheduled tasks (delayed publications, backups, sending of emails) through a mechanism called WP-Cron. Its documentation explains that it does not run continuously: it checks for tasks to run on every page load. On a site with few visitors, a task may therefore start late. On a heavily visited site, this check needlessly consumes resources. We disable this trigger in the WordPress configuration and hand the tasks over to the system scheduler, which launches them at fixed times, as the documentation recommends.

To lighten WordPress, we use the Admin and Site Enhancements extension, often abbreviated ASE. It disables, in a single place, several features that are rarely useful on a business site: embedding content from other sites (“embeds”), the XML-RPC protocol, the REST API for logged-out visitors, and emojis. It also lets you slow down or switch off the “heartbeat”, the regular communication between the browser and the server. We also keep the number of extensions as low as possible, because Elementor already takes up a good share of the resources. The database is cleaned regularly, in particular of old revisions and temporary data.

For monitoring, we use Query Monitor, which displays in WordPress the slow, duplicated or failing database queries, PHP errors and external calls. On complex sites, New Relic’s PHP agent completes the picture: it traces transactions, database queries and errors over time.

Security: reducing the attack surface

On the sites we host, the WordPress administration area is not accessible from the Internet. Login goes through a VPN only, an encrypted tunnel reserved for authorised people. This is a daily constraint, and we do not hide it. It does, however, take the login page out of reach of bots that try passwords in bulk.

To this are added the measures already described: XML-RPC disabled, Cloudflare’s firewall and rate limiting, blocking of countries unrelated to the business, up-to-date PHP. No configuration makes a site invulnerable. The goal is to reduce the number of entry points and to quickly spot anything abnormal.

Questions to ask your host about an Elementor site

If your Elementor site is hosted elsewhere, a few questions will quickly tell you where you stand. They require no technical skills, only precise answers.

  • Which PHP version does the site run on, and when will it move to the next one? Elementor recommends PHP 8.3 or newer.
  • How much PHP memory is allocated to the site? Elementor recommends 512 MB.
  • Is a persistent object cache, such as Redis, available and enabled?
  • Are scheduled tasks run by the system scheduler or by WP-Cron?
  • Is there a test copy on the same configuration as the live site?
  • Who clears the caches after a change, and in what order?
  • In which country are the servers and the backups located?

The last question concerns data protection. According to the Federal Data Protection and Information Commissioner, the new Data Protection Act (nLPD) allows personal data to be disclosed abroad if the legislation of the recipient country ensures an adequate level of protection. The list of these countries is drawn up by the Federal Council in the annex to the Data Protection Ordinance. Failing that, protection must be ensured by other means, in particular through contractual safeguards. A contact form or an online shop processes personal data, so the location of the server is not a detail.

If the answers remain vague, or if you would like your Elementor site’s configuration reviewed, let’s talk during a first conversation.

Sources

Mehdi B.
About the authorMehdi B.

Co-founder of Smart Impact. Hooked on the web from the start, he launched his first project in 2006: an online music magazine still running today. With close to 20 years of SEO experience, a Swiss federal diploma in marketing and a solid geek streak, he turns clients' ideas, sometimes hazy ones, into concrete digital projects with his team.

LinkedIn
Further reading