Skip to main content

Improving WordPress site speed with Elementor: A comprehensive guide

Article Content

Elementor is a popular visual page builder for WordPress. It lets you build complex pages without writing code, but it also adds CSS and JavaScript files to every page. The result: a site built with Elementor can be slow, but it does not have to be. This guide goes through the steps in the order you should take them.

1. Choose a lightweight theme

The theme sets the skeleton of the site: the header, the menu, the base styles and the files that load on every page. A heavy theme adds files you may never use.

For a site built with Elementor, choose a minimal theme. Hello Elementor is a lightweight, minimalist theme, and its WordPress.org page describes it as a theme built specifically to work with Elementor. When the theme adds no design of its own, Elementor controls how the site looks, and everything that loads is under your control.

2. Review Elementor's experiment settings

Elementor has performance options you can switch on. According to the Elementor documentation, they are on the Features tab of the editor settings (Elementor > Editor > Settings). Two of them are worth knowing:

  • Improved Asset Loading: better loading of the CSS and JavaScript files.
  • Optimized DOM Output: an optimized page structure (DOM) output.

Back up the site before you switch anything on. According to the documentation, these experiments are still in Alpha or Beta and may change. After each change, check the main pages, and if something breaks, switch the option off. The menus differ between versions, so check the screen you actually see.

3. Do not build in Elementor what repeats on every page

The header, the footer and the sidebar appear on every page of the site. If you build them in Elementor, every page loads their code, even when they have not changed. It is better to build those parts in the theme and leave the page content to Elementor.

If you have already built the header or the footer in Elementor, ask a WordPress developer to review the structure and move those parts into the theme.

4. Reduce plugins, widgets and animations

Every third-party plugin on an Elementor site adds more code that loads. Install only the plugins you really use.

A few simple rules:

  • Turn off or remove widgets you do not use, if your tool allows it.
  • A slider with many slides and heavy images slows the page down. Use fewer slides, compressed images and lazy loading where you can.
  • For page layout, use grid or flexbox, not complex tables.
  • Keep animations for places where they add something for the reader.
  • In a form, keep only the required fields. A newsletter sign-up form usually needs only an email field.

5. Set up a caching plugin correctly

A caching plugin is an important tool on almost every site, and on Elementor it needs proper settings, or it can break the design.

  • Set the cache not to serve logged-in users, and exclude the editing pages.
  • Check that CSS and JavaScript minification does not break the pages. If it does, switch that option off or add an exception for the Elementor files.
  • Deferred JavaScript loading can break dynamic widgets such as forms and sliders. Use it carefully, and test every form after the change.
  • After each edit to a page, clear the cache so you see the updated version.

If you use a CDN alongside the caching plugin, check that the plugin does not set cache rules that conflict with the CDN rules.

6. Raise the memory limit

Elementor requires at least 256MB of PHP memory, and its system requirements recommend 512MB. If the site has heavy plugins, such as a WooCommerce store, you may need more.

On our shared hosting, you raise the PHP memory limit yourself in cPanel, using the MultiPHP INI Editor, and set memory_limit to the size you need, for example 256M.

In WordPress you can also raise the limit in the wp-config.php file. According to the WordPress documentation, the line looks like this:

define( 'WP_MEMORY_LIMIT', '256M' );

7. Measure before and after

Choose one measuring tool, and use it before the change and after it. Response time changes during the day, so one measurement is not enough. Measure several times, at different hours.

You can also measure in the browser: open the page on your computer, press F12, and open the Network tab. On the first request to the server, the Waiting (TTFB) field shows how long the browser waited for the first byte of the response. Record the values before and after the change.

When to call a professional

If the pages break after every change, or if the site is still slow after these settings, the problem is probably somewhere else: in the infrastructure, the plugins or the code. In that case, contact a WordPress developer or our support team.

If you want someone to maintain the site and the server for you, the server and website maintenance page describes what is included. The infrastructure itself has a large effect on performance. If the site is heavy and you cannot speed it up, check the type of hosting too, and compare shared hosting with a virtual server.

Related articles


Monthly newsletter

Guides, tips and updates for site and server owners. Once a month.

Practical guides on WordPress, VPS and security, what's new on the site and in our services, reader-only discounts and measured infrastructure metrics. One e-mail a month, one-click unsubscribe.

We send a confirmation e-mail (double opt-in). No spam, no sharing of addresses. Privacy policy

2026 © Linux Hosting - Web Hosting since 2012

By Linux Hosting: hosts.click - preview any website before DNS changes

Visa Mastercard American Express PayPal Bitcoin