Plenty of site owners tell us the same thing. The design looks good, and everyone is happy with it, but the pages feel heavy on a phone, and PageSpeed shows a lot of red. If you have been asking Why is my Elementor site slow?’ this guide is for you. We will go through the usual causes, what to fix first, and how to get all three Core Web Vitals into the green. In our experience, Elementor speed optimisation is mostly about removing extra weight, not adding more plugins to cover it up.
Why is my Elementor site slow? The usual causes:
It is rarely Elementor alone. A slow page is normally a few smaller problems stacked together:
- Cheap hosting with a slow server response
- A hero photo of 2 to 3 MB straight from a camera or stock site
- Old Section and Column layouts with many wrapper divs
- Add-on widget packs that load scripts on every page
- Chat widgets, tracking pixels and social share buttons
- Several Google Fonts plus a full icon library
- No page caching
So when someone asks, ‘Why is their Elementor site slow?’ there is hardly ever one answer. We open the page and check each of these in turn.
Before you change anything, run the page through PageSpeed Insights. Read the real user data at the top first, because that is what Google uses. The lab score below it is only a test on a simulated device.
The three numbers you need to pass:
- LCP (loading): how fast the main content shows up. Good is 2.5 seconds or less, and poor is over 4 seconds.
- INP (responsiveness): how fast the page reacts to taps and clicks. Good is 200 ms or less, and poor is over 500 ms.
- CLS (visual stability): how much the layout jumps around. Good is 0.1 or less, and poor is over 0.25.
Google looks at the 75th percentile of real visits, and a page passes only when all three are good. INP replaced the old FID metric in March 2024. It is stricter because it looks at every tap and click during a visit, not just the first one.
A little over half of websites pass all three today. Green scores can give you an edge, but don’t expect rankings to jump overnight, since content still matters more. What you will notice sooner is fewer people leaving the page.
Elementor Core Web Vitals problems usually show up in one metric more than the others. Find the red one first and fix that.
- Step 1: Fix hosting and caching first.
Elementor can’t make a slow server fast. Check how long your server takes to send the first byte of the page. Use a current PHP version, a page caching plugin, and a CDN. If most of your visitors are in India, a server in India or Singapore, or a CDN with a nearby location, makes a real difference. Good Elementor Core Web Vitals scores start with a quick server.
- Step 2: Turn on Elementor’s own performance settings.
Open the Elementor settings and look under the Features and Performance tabs. Names move around between versions, so don’t worry if yours look a little different. Turn on what you find from this list:
- Flexbox containers (and Grid) instead of Sections and Columns
- Optimised Markup
- Optimised image loading and lazy loading for background images
- Element caching
- Load Google Fonts locally.
Also open the Element Manager and disable widgets you never use.
Take a backup or use a staging copy first. Optimised Markup changes the wrapper classes, so any custom CSS that targets them may stop working. This is the cheapest part of Elementor speed optimisation. It costs nothing and usually takes under an hour.
How to reduce Elementor DOM size?
The DOM is every element on your page: each section, column, heading, button and wrapper. Lighthouse warns at about 800 elements and shows an error at around 1,400. It also complains when nesting goes deeper than 32 levels or one parent has more than 60 children. Elementor pages cross these lines easily, because older layouts add several wrappers around every widget. A big DOM slows loading, and it also slows every tap, because the browser has to recalculate styles for all those elements.
Here is how to reduce Elementor DOM size without redesigning the whole site:
- Move from Sections and Columns to Containers. Elementor’s own figures say Flexbox Container output is up to 39% smaller and Grid output up to 85% smaller.
- Stop nesting containers just for spacing. Use gaps and padding instead.
- Delete hidden copies. If you build one block for desktop and another for mobile and hide one with CSS, both stay in the DOM. Build one responsive layout.
- Trim long tabs, accordions and mega menus. Hidden content still counts.
- Split very long landing pages into two pages where it makes sense.
Caching plugins can’t help here. DOM size is a design problem, so the fix has to happen in the layout. If you only have time for one job on a heavy page, start with the layout, since learning how to reduce Elementor DOM size helps both loading and tapping.
Fix LCP: look at the hero section.
On most pages, the LCP element is the hero image or the main heading. Check which one the PageSpeed marks, then:
- Don’t lazy-load it. Lazy loading is for images below the fold. On the hero, it delays the most important thing on the page.
- Resize it to the size it is actually shown at, and use WebP or AVIF. A resized hero is a fraction of the original file.
- Preload it if your caching plugin has the option.
Skip sliders and background videos at the top. A plain image with a heading and a button almost always loads faster.
A practical WordPress INP fix
INP gets slow when the browser is busy running JavaScript at the moment a visitor taps. On WordPress, that is usually third-party code: chat widgets, analytics and ad pixels, share buttons, review embeds and add-on widget packs. A WordPress INP fix is mostly about removing or delaying things, not adding new ones.
What to do:
- List every script on the page. PageSpeed has a third-party code section that shows the heavy ones.
- Delay non-essential scripts until the first interaction. Most optimisation plugins have a “delay JavaScript” option. Start with the chat widget.
- Remove plugins that do the same job twice.
- Cut the DOM size, as above.
- Test on a real mid-range Android phone. Open the menu, open an accordion, and fill in a form. If it lags there, your visitors feel it too.
Test after every change. A WordPress INP fix done in a hurry can break a contact form, and a broken form costs more than a slow page.
Fix CLS.
CLS is usually the easiest of the three. The common causes are images without width and height, cookie bars and popups that push content down, fonts that swap late, and embeds that load after the text. Set image dimensions, give embeds a minimum height, load fonts locally, and let banners sit over the page instead of pushing it.
Your Elementor mobile PageSpeed score will be lower than desktop.
The mobile test simulates a slower phone and a slower network, so a gap from desktop is normal. Don’t chase 100. We would rather see green real user data and a lab score in the middle than a perfect lab score that came from stripping the design. Check the mobile report on its own, because Google indexes the mobile version of your site. Track your Elementor mobile PageSpeed score after each change, but judge the work by LCP, INP and CLS.
How do we look at slow sites at 360 Digital Idea?
At 360 Digital Idea, we handle speed as part of our WordPress development and maintenance work, and we have been doing this for 10+ years. When a slow site comes to us, I start with the same four things: server response, the hero image, third-party scripts and page structure, including how the page builder is set up. Often the fix is in those places, and the site does not need to be rebuilt or moved to another builder.
Keeping it fast after the fix.
Elementor speed optimisation is not a one-time job. Speed slips back when someone adds a new plugin, the marketing team adds a pixel, or large images get uploaded. Once a month, run your home page and top three landing pages through PageSpeed Insights and check the Core Web Vitals report in Search Console. Real user data covers a rolling 28 days, so improvements take a few weeks to show fully.
This is where our maintenance work helps. Along with updates and security, we look at performance on an ongoing basis, so a slow plugin doesn’t sit there unnoticed for months.
Where to start?
If you want a simple order, go with this: hosting and caching, Elementor’s settings, the hero image, third-party scripts, DOM size, and then layout shifts. Test after each step. Passing Elementor Core Web Vitals is a series of small fixes, more than one big change.
If you would like a second pair of eyes on your site, you can reach us at 360 Digital Idea for a free consultation, and we will go through your pages with you.
Frequently Asked Questions
Q1. Does Elementor slow down a WordPress site?
Not on its own. Most slow Elementor sites are slow because of heavy images, weak hosting, extra plugins and old layouts. A well-set-up Elementor site can pass Core Web Vitals.
Q2. Why is my Elementor site slow only on mobile?
Phones have slower processors and networks, and the mobile test is stricter. Large images, heavy scripts and a big DOM hurt more there.
Q3. What is a good Elementor mobile PageSpeed score?
Google does not set a target for the lab score. It judges pages on real user LCP, INP and CLS. Use the score to compare before and after, not as a pass mark.
Q4. How many DOM elements are too many?
Lighthouse warns at about 800 and shows an error around 1,400. It also flags nesting deeper than 32 levels and any parent with more than 60 children.
Q5. Can I do a WordPress INP fix without a developer?
Partly. You can delay chat and tracking scripts with an optimisation plugin and remove unused plugins. Heavy custom code needs a developer.
Q6. Do caching plugins fix Elementor Core Web Vitals?
They help with server response and sometimes LCP. They can’t reduce DOM size or fix heavy JavaScript.
Q7. Should I lazy load the hero image?
No. Lazy-load images below the fold and load the hero image normally.
Q8. How long before Search Console shows the improvement?
Real user data uses a rolling 28 days, so expect a few weeks to a month.
Q9. Do I need to leave Elementor to pass Core Web Vitals?
In most cases, no. Fix the setup first. Moving only makes sense if the layout is so heavy it needs a rebuild anyway.