I get asked to “make the Elementor site faster” a lot. The pattern is remarkably consistent. Here is what I check, in the order I check it.
Is it Elementor’s fault?
Mostly no. A tuned Elementor build like Fence Decks and More scores 98 on desktop and 89 on mobile, which is a genuinely fast site. Elementor adds more CSS and JavaScript than a lean builder, so it starts further back, but it is very rarely the reason a site is in the red. The reasons are the five below.
What is the biggest single cause?
The hero image. Nine times out of ten, the largest element on the first screen is a full-width photo or graphic exported at desktop resolution and shipped, unchanged, to a phone. On a throttled mobile connection it can take 5 to 15 seconds to paint, which is your entire Largest Contentful Paint. On one build the whole mobile gap was a single decorative hero graphic; on another it was one lifestyle photo. The fix is a properly sized, compressed mobile crop, and it is often a one-hour job.
What else, after the hero?
- Site-wide assets. Elementor and every add-on plugin load their stylesheets and scripts on every page by default, even pages that use none of them. Limiting assets per-page removes a large chunk of the payload.
- Layout shift. Images without explicit dimensions, a sticky header that resizes, a cookie bar or chat bubble that appears a second late. Each nudges Cumulative Layout Shift up. Reserve space for all of them.
- Fonts and icons. Four font weights plus Font Awesome plus an icon pack is common and unnecessary. Two or three weights, self-hosted, and only the icons actually used.
- Third-party embeds. A live-chat widget, an embedded map, an autoplay video. Each loads its own bundle from another domain. Facade-load them: show a lightweight placeholder and only load the real thing on interaction.
Why is it fine on desktop but bad on mobile?
Because PageSpeed’s mobile test emulates a mid-tier phone on a slow connection. Desktop has the bandwidth and CPU to absorb a heavy page; a throttled phone does not. Everything above hurts two to four times more on the mobile test. That is also why a site can feel fine on your own phone and still score 55.
What can I fix myself?
Re-export and replace the hero image at a sensible size. Delete unused plugins. Cut font weights in the Elementor global settings. Add a caching and optimisation plugin and enable its “load assets per page” style options carefully, testing after each. That alone often moves a mobile score 15 to 25 points.
When is a rebuild the answer?
When the site is still slow after all of the above, the theme is a heavy multipurpose one, and you were considering a refresh anyway. Then a move to Bricks or a custom build is worth it. Otherwise, tune what you have.
