Elementor and Core Web Vitals: a checklist for agency builds

Elementor sites are not slow by nature. They get slow through accumulated choices: oversized images, too many plugins, heavy effects, cheap hosting and nobody measuring. This is the checklist we use so speed is designed in, not patched on in the last week.

Know what you are measuring. Core Web Vitals are three metrics: LCP (how quickly the main content appears), INP (how quickly the page responds when someone taps or clicks) and CLS (how much the layout jumps). Real-user data in Search Console matters more than any single lab score. Test the templates that matter (home, a service page, a blog post) on mobile, before and after your changes.

1. Start with the page, not the plugin

• Design for the LCP element. Decide which image or heading is the largest thing above the fold and keep it simple. A full-width hero slider is almost always the slowest part of the page.
• Cut effects that do not earn their cost. Scroll animation, parallax and large sliders add JavaScript and layout work. Use them where they help the client, not by default.
• Keep the DOM small. Deeply nested containers add weight. Prefer a flat structure built with containers over stacked sections and columns.

2. Images do most of the damage

• Resize to the size actually displayed. A 4,000-pixel photo in a 600-pixel slot is wasted bytes.
• Use modern formats (WebP or AVIF) with sensible compression.
• Set explicit width and height so the layout does not jump (this protects CLS).
• Lazy-load images below the fold, but never the LCP image. Load that one eagerly and give it priority.

3. Fonts

• Limit families and weights. Every extra weight is another request.
• Self-host fonts rather than loading them from a third party, and use font-display: swap.
• Preload only the one or two files used above the fold.

4. Plugins and third-party scripts

• Every plugin is a cost. Remove what is unused, and avoid two plugins doing the same job.
• Load analytics, chat widgets and tag managers late.
• Be honest with clients: a heavy chat widget or a dozen tracking pixels will cost more speed than any Elementor setting can win back.

5. Elementor settings worth reviewing

Elementor ships performance options, split between the Performance and Features tabs in its settings. Two worth knowing: Optimized Image Loading applies high fetch priority to the likely LCP image and lazy loading to images below the fold, and Optimized Control Loading loads editor controls only when needed. Element Caching is also available as a feature. Some of these are active by default on new sites only, and Elementor says features can change or be removed between versions, so check what your install offers.

Do not assume a setting helps. Change one at a time and measure, because they can interact with themes and add-ons.

6. Hosting and caching

A fast build on slow hosting is still slow. Check server response time, use full-page caching, and make sure caching rules do not break forms or logged-in views. Test the contact form after enabling any cache.

7. Keep it fast after launch

Speed decays: a new plugin, a bigger upload, one more script. A monthly check on the key pages, plus updates and backups, keeps the gains. That is much of what a care plan is for.

What to promise your client

Promise a process and a measured improvement, never a guaranteed score. Scores depend on the client’s content, third-party tools and hosting as much as on the build. Our companion piece covers what you can honestly promise clients on speed.

Want it built in from the start?

We build Elementor sites lean by default, under your brand. See white label Elementor development, or talk to us about your next build.

Frequently asked questions

Is Elementor bad for Core Web Vitals?

Not inherently. Most problems come from images, plugins, effects and hosting. A disciplined build can perform well.

Which metric is hardest to fix?

Usually LCP on mobile, because of oversized hero images and render-blocking resources.

Should I trust a perfect PageSpeed score?

Use it as a guide, but check real-user data in Search Console. A lab score can look good while real visitors struggle.