Short answer: it is usually not Elementor itself. It is font and icon files loading on every page for a handful of characters, the same fonts being requested more than once, and images uploaded at camera size. A caching plugin hides some of that. It does not remove it.
Here is how to find what is actually costing you, in about ten minutes.
Measure before you change anything
Open your homepage in Chrome, press F12, go to the Network tab, tick
Disable cache, and reload.
Sort by Size, largest first. Now look at the Type column and ask one question: what are the biggest files, and does the page visibly use them?
That question finds most of the problem.
What I usually find, in order
1. Icon fonts loading in full
This is the big one and almost nobody checks it.
Elementor, your theme, and any addon pack each ship icon fonts. A single icon font family is often 400–600 KB, and loading two or three is routine. On one site I measured recently, over a megabyte was icon fonts — for perhaps a dozen icons that were actually visible.
Filter the Network tab by Font. If you see files named for icon sets —
uicons, fontawesome, eicons — you have found real weight.
The fix: in Elementor → Settings → Features, there are options to load Font Awesome inline and to disable icon libraries you do not use. For the handful of icons a design really needs, inline SVG is smaller than any icon font and cannot cause a text flash.
2. The same font requested several times
Filter by Font and look for identical filenames appearing more than once.
This happens when the theme registers Google Fonts, Elementor registers them again, and a plugin does too. Each thinks it is being helpful. The browser downloads the same file repeatedly.
The fix: Elementor → Settings → Advanced → Google Fonts can be disabled if your theme already loads them. Pick one owner for fonts and turn the others off.
Also: does the design use six weights, or two? Every weight is a separate download.
3. Images at original size
A 4000-pixel photo from a phone, displayed in a 600-pixel space, still downloads all 4000 pixels.
The fix: resize before uploading, and serve WebP. This alone often halves page weight and needs no plugin — though a bulk converter helps if there are hundreds already uploaded.
4. Plugins loading everywhere
A slider plugin used on one page usually loads its CSS and JavaScript on every page, including ones with no slider.
The fix: audit what is installed. Anything you cannot explain the purpose of is a candidate for removal. This is tedious and it is usually where a surprising amount of weight is hiding.
Where caching actually helps
I am not against caching plugins — server-level caching is genuinely valuable, and many hosts leave it switched off by default. Check your hosting control panel before installing anything.
But caching makes the second visit fast. It does nothing for a first-time visitor, which is every visitor arriving from Google. Removing weight helps both.
What to measure afterwards
Run PageSpeed Insights. If your site has enough traffic, pay attention to the field data section rather than the lab score — that is real visitors on real connections, and it is what Google actually uses.
The number worth caring about most is Largest Contentful Paint: how long until the main thing on screen appears. Under 2.5 seconds is the target.
Is Elementor just slow?
Not inherently. It is heavier than hand-written HTML, and that is the cost of giving a client a page builder they can use — usually a cost worth paying.
I have built Elementor sites that reach first contentful paint in about a second. It takes deliberate work rather than a plugin, but the ceiling is much higher than the average Elementor site suggests.
Site slow and not sure why? Send me the URL — diagnosing this is most of what I do, and the cause is usually specific and fixable rather than “WordPress is slow”.