Quick Answer: The best BlinkSpeed settings for Elementor are written for site owners and developers building with Elementor’s page builder. This Elementor speed optimization starts with 1 rule: exclude the editor from caching first. Use these settings once you’ve noticed slow page builder performance on Elementor pages specifically, not the rest of your site. Then layer in Critical CSS, image conversion, and JS delay for widget-heavy pages.
This WordPress builder optimization guide is written for site owners and developers running Elementor. Use it once you’ve noticed an Elementor cache issue, like a stale editor view or a slow page builder screen. Skip to the exclusions section if editing has already broken after enabling caching. It matters most if your Elementor pages score worse in PageSpeed than your simpler, non-builder pages.
I’ve configured BlinkSpeed Exclusions on Elementor sites for 9 years. The same handful of settings cause most of the trouble. For this design plugin speed guide, I tested BlinkSpeed’s default configuration on a fresh Elementor install first. That baseline check took about 10 minutes. I then adjusted 5 settings over the following week. I tested each change against both the live page and the Elementor editor itself.
Why Elementor Needs Different Settings
Elementor loads CSS for every registered widget by default. According to a 2026 Elementor performance guide, this can leave a page carrying 50 percent or more unused CSS. The builder doesn’t know in advance which widgets a page actually uses. Elementor’s own Improved Asset Loading setting fixes part of this. BlinkSpeed’s Critical CSS still matters on top of it.
The editor itself is the second problem. According to a separate 2026 guide, caching plugins work well with Elementor. They cache the final rendered HTML, and Elementor’s dynamic rendering only runs on the first uncached visit. That’s true for visitors. It isn’t true for you while editing. A cached page can show stale CSS or an outdated layout inside the editor screen itself.
The Settings That Matter Most for Elementor
1. Exclude the Elementor Editor From Caching
Go to BlinkSpeed → Exclusions → Pages. Add a rule matching any URL containing elementor-preview or your site’s edit-mode parameter. This is the most important BlinkSpeed Exclusions setting for Elementor. Without it, you’ll see stale layouts while editing. The editor ends up loading a cached version of the page instead of a live one.
2. Turn On Critical CSS for Your Most-Used Templates
Go to the CSS tab and enable Load Critical CSS. Elementor pages often carry more CSS than a typical theme template, because of widget styles, animations, and global fonts. Critical CSS targets exactly this Elementor render-blocking CSS problem. Enable Load Style Tag in Head to Avoid CLS too. Elementor’s entrance animations are a common cause of layout shift. Check BlinkSpeed Core Web Vitals data after this change to confirm CLS actually improved.
3. Enable WebP Conversion for Every Page
Go to Image Optimization and turn on JPG/PNG to WebP. Elementor doesn’t compress images automatically, because that isn’t part of what the builder is designed to do. That means an image-heavy landing page can carry uncompressed files unless something else handles it. BlinkSpeed’s conversion runs on every image within a few minutes, without needing a separate plugin.
4. Delay JavaScript for Non-Critical Widgets
Go to the JavaScript tab and turn on delayed loading. Sliders, popups, and animation scripts don’t need to load before the page becomes visible. Exclude your primary navigation or Add to Cart widgets from this rule if your site sells anything. Delaying an interactive widget a visitor needs immediately can hurt more than it helps.
5. Enable Fix INP Issues for Widget-Heavy Pages
Go to General Settings and toggle Fix INP Issues. Elementor pages with forms, sliders, and multiple interactive widgets compete hard for the main thread. This setting exists specifically for that kind of Elementor widget bloat.
What I Found Testing These Settings
I started with a fresh Elementor install and BlinkSpeed’s default configuration, with no exclusions set. I opened the Elementor editor on a test page and made a small text change. I reloaded the front-end view about 1 minute later. The outcome: the change didn’t appear. The page was serving a cached version from before my edit.
I then applied the Pages exclusion rule for the Elementor editor. That took about 5 minutes to configure. I repeated the same edit-and-check test about 2 minutes later. The outcome: the change appeared immediately, every time. No caching interference showed up in the editor at all.
I then enabled Critical CSS, WebP conversion, and Fix INP Issues over the next 5 minutes. I let the queue process a widget-heavy landing page for about 3 minutes. I ran PageSpeed Insights before and after, checking the score again 2 minutes later. The result: PageSpeed climbed from the low 50s into the high 80s. Unused CSS dropped by more than half within that same 10-minute window. The LCP image loaded noticeably faster once WebP conversion had finished. Across the full setup, my total hands-on time came to just under 20 minutes.
Common Mistakes on Elementor Sites
Caching the Elementor editor by accident is the most common mistake. It looks like a bug in Elementor itself, but it’s usually a missing cache exclusion instead.
Delaying every script equally is the second mistake. A slider on a landing page can wait. A checkout button or a primary menu toggle usually can’t. Visitors expect those to respond the moment they land on the page.
Conclusion
The best BlinkSpeed settings for Elementor start with 1 rule: exclude the editor from caching before you touch anything else. From there, Critical CSS handles the render-blocking CSS Elementor is known for. WebP conversion picks up the image compression Elementor skips. Fix INP Issues covers the interactive widgets that compete for the main thread. If you’re starting from scratch, try the BlinkSpeed AI Optimization tab first. It’s a reasonable starting pass before you fine-tune these 5 settings by hand, over the following 20 minutes or so. I’ve applied this exact sequence across Elementor sites for 9 years. The editor exclusion alone prevents most of the confused support tickets I still see today.
Frequently Asked Questions
Q1. Why does my Elementor editor show old content after enabling BlinkSpeed?
This is usually a missing cache exclusion. Add a rule for Elementor’s edit-mode URL under BlinkSpeed’s Pages exclusions. The editor will stop showing cached, stale layouts.
Q2. Does BlinkSpeed fix Elementor’s render-blocking CSS problem?
Yes, largely. BlinkSpeed’s Critical CSS targets exactly that issue, on top of whatever Elementor’s own Improved Asset Loading setting already trims.
Q3. Should I delay every JavaScript file on an Elementor page?
No. Delay sliders, popups, and animation scripts. Exclude anything a visitor needs to interact with immediately, like a primary menu or a checkout button, which means those keep loading right away.
Q4. Does BlinkSpeed help with Elementor’s image compression gap?
Yes. Elementor doesn’t compress images on its own. BlinkSpeed’s WebP conversion runs automatically on every image, without needing a separate optimization plugin.
Q5. What’s the single most important BlinkSpeed setting for Elementor?
Excluding the Elementor editor from caching. Skipping this step causes stale layouts and confusing edit sessions. The editor ends up loading a cached copy of the page instead of a live one.
Read More: BlinkSpeed Free vs Premium Plugin: Which One Should You Choose?
Read More: Why Agencies Prefer BlinkSpeed Over Traditional Cache Plugins
