Every WordPress + Elementor site I've audited for a small business client has the same handful of problems. Not exotic ones — the boring, easy-to-skip ones. Here's the list I actually work through, roughly in order of impact-to-effort ratio.
1. Measure before you touch anything
Run PageSpeed Insights (or web.dev) and write down the numbers: LCP, CLS, INP, and the "opportunities" list. You need a baseline, otherwise you're optimizing blind and won't know which change actually helped.
2. Turn on page caching first
Before touching plugins one by one, install a caching plugin (WP Rocket, LiteSpeed Cache if your host supports it, or W3 Total Cache) and enable page caching. This is usually the single biggest win available, and it takes five minutes.
3. Compress and modernize images
Elementor sites are image-heavy by nature — hero sections, portfolio grids, background images. Run everything through a compressor and serve WebP or AVIF. A plugin like ShortPixel or Imagify (or your host's built-in optimizer) can automate this. Also: set explicit width/height attributes so the browser reserves space and you don't get layout shift.
4. Lazy-load below-the-fold images
Most modern themes and Elementor itself support native lazy loading, but double-check it's actually on. Anything below the first screen shouldn't load until the user scrolls near it.
5. Audit your plugins with a query monitor
Install Query Monitor (or use your host's profiling tool) and look at which plugins add the most load time. It's common to find one forgotten plugin — an old page builder, a broken SEO plugin, a stats widget nobody looks at — quietly adding 500ms+ to every page load.
6. Limit web fonts to what you actually use
Every additional font weight or style is a render-blocking request. If your Elementor Global Fonts settings have five weights of the same font loaded and you're only using two, trim it.
7. Clean the database
Post revisions, spam comments, and expired transients pile up over time and slow down every query, including admin-side ones. A plugin like WP-Optimize (used sparingly, with a backup first) or a manual cleanup query handles this.
8. Be careful with CSS/JS minification and combination
Aggressive "combine all CSS/JS into one file" settings can break Elementor widgets that expect their scripts to load in a specific order. Enable it, then actually click through the site — sliders, popups, forms, accordions — before assuming it's safe.
9. Check your hosting is appropriate for your traffic
No amount of plugin-level optimization fixes underpowered shared hosting once a site starts getting real traffic. If TTFB (time to first byte) is consistently high even with caching on, the bottleneck is often the server, not WordPress.
10. Re-run PageSpeed Insights and compare
Go back to step 1's baseline. If a change didn't move the numbers, it probably wasn't worth the added complexity — revert it and try the next thing.
None of this is advanced. It's mostly discipline: measure, fix the boring stuff first, measure again. In practice, steps 2 and 3 alone (caching + image compression) account for most of the improvement I see on client sites.
Written by Onur Freelance, a web design and digital marketing agency in Maltepe, Istanbul, working with WordPress and Elementor.
Top comments (0)