Elementor Popup Not Working? Check Conditions, Triggers and Advanced Rules
An Elementor popup needs conditions, a trigger and passing rules before it shows. Check each in order, plus the multiple-popup option and…
When an Elementor website is slow, the cause may be the server, images, fonts, scripts, plugins or caching. Measure first, then fix the layer that is actually slow.
Elementor website slow is a symptom, not a diagnosis. The delay can sit in the server, in heavy images, in fonts, in scripts from other sites, in plugins, or in missing caching. Changing settings at random can waste hours and sometimes break the layout. This guide shows how to measure first and then fix the one layer that is actually slow. For general habits that keep a site fast, see how to keep Elementor sites fast.
Run your page through PageSpeed Insights and note the slowest metric. A slow Time to First Byte points at hosting, caching or plugins. A slow Largest Contentful Paint usually points at one big image or hero background. Layout shifts point at fonts or images without sizes. Heavy blocking time points at scripts and embeds. Fix one thing, clear caches, and measure again, because you can only call it fixed if the numbers move.
How this guide was prepared: the steps follow Elementor’s help articles, web.dev guidance and the WordPress handbook listed under Sources, read on October 19, 2026. We did not reproduce a slow Elementor site for this guide, so the steps are research-based. Results depend on your host, theme, plugins and content, and a speed score is not a promise of ranking or sales.

| What you see | Likely cause | Start with |
|---|---|---|
| Long wait before anything appears | Slow server response, no page cache, heavy plugin | Steps 2 and 6 |
| Main banner appears late | Large hero image or background, not prioritised | Step 3 |
| Text jumps when the page loads | Font loading method, images without dimensions | Steps 3 and 4 |
| Page is visible but sluggish to tap | Heavy scripts, sliders, chat widgets, embeds | Step 5 |
| Very large page, many sections | Deeply nested layout and many elements | Step 8 |
| Slow only inside the editor | Editor load, memory limit, many plugins | Step 7 |
Use PageSpeed Insights, which shows lab data from a test run and, when enough visitors exist, real-user data for your site. web.dev describes three Core Web Vitals: Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness) and Cumulative Layout Shift (visual stability). Read the report from the top: find the weakest metric, then open the diagnostics under it. That tells you which of the steps below to start with. Test a typical page, such as the homepage, and also a heavy one, such as a long landing page.
web.dev explains Time to First Byte (TTFB) as the time until the first byte of the page arrives, and notes that a slow TTFB delays everything after it. If it is high on every page, the cause is not your design. Common causes are slow shared hosting, no page caching, an old PHP version and plugins that do heavy work on every request. Ask your host about PHP version and server-side caching, and enable a page-cache plugin or your host’s cache. If TTFB is good, move on, and do not spend time on the server.
web.dev’s guide to optimizing Largest Contentful Paint says the load time of the main image or text block is usually the biggest factor. Check which element PageSpeed Insights names as the LCP element. If it is an image, make sure it is not larger than needed, is in a modern format, and has width and height. Elementor offers lazy loading for background images (all but the first) and image loading optimization that prioritises the images that take longest, and an Image Optimization tool for compression. Do not lazy-load the first image on the page, because it is the one visitors wait for.
Elementor says the method used to load Google Fonts can affect performance. In WP Admin open Elementor → Editor → Settings → Advanced and choose a Google Fonts Load method: Default, Blocking, Swap, Fallback or Optional. Blocking hides text until the font has loaded, while Swap shows a fallback font first. Use fewer font families and weights, because each one is another download. Check any custom font files are not huge, and re-test after the change.
Sliders, chat widgets, video embeds, maps, tracking tags and social feeds each load their own code. In the PageSpeed Insights diagnostics, look for third-party code and long main-thread work. Remove what nobody uses, replace autoplay video with a poster image that loads the video on click, and load maps and chat only where needed. Elementor states that it does not load widget-specific assets for widgets that are not used on the page, so disabling unused Elementor widgets is not needed. That advice does not apply to other plugins’ widgets.
If TTFB is high, a plugin may be adding slow database queries or remote requests. On a staging copy, deactivate plugins in groups, test, and reactivate until the slowdown returns. Our guide How to find the plugin that broke your site explains the method. Next, make sure only one caching layer is doing each job: two page-cache plugins at once can conflict. After any change, clear caches as in Elementor changes not showing, then test again.
A slow editor does not mean a slow site. The editor loads many scripts and your plugins’ admin code. If only the editor is slow, check the PHP memory limit with your host, deactivate unneeded plugins on staging and use a different browser profile without extensions. If the editor does not open at all, see Elementor editor not opening. Do not weaken the live site to fix an editor problem.
Elementor describes a traditional Section, Column and Inner Section layout as producing many nested div elements, while a Flexbox container can produce the same result with fewer. Its optimized DOM output also removes wrapper elements. A smaller page is easier for the browser to render. Before rebuilding anything, check whether the page is simply very long, with many widgets, big sliders and loops. Splitting a very long page, or removing repeated sections, can help more than any setting. Rebuild layouts only on staging and review the result on mobile.
Scores come from a test run. Real visitors have slower phones and networks, so check the real-user data in PageSpeed Insights if it is available.
Elementor says unused widgets, fonts and icons do not load their assets on pages where they are not used.
Not by default. Slowness usually comes from hosting, images, fonts, scripts and plugins, and Elementor is only one part of that. Measure to know.
Not before measuring. A new plugin adds its own code and can conflict with your cache. Fix the slowest layer first.
Related guide: Elementor Mobile View Broken? Fix Responsive Layout Problems
Related guide: Cumulative Layout Shift (CLS) in WordPress: Causes and Fixes
Related guide: Optimize Images in WordPress: WebP, AVIF, Sizes and Lazy Loading
Related guide: Interaction to Next Paint (INP) in WordPress: What It Is and How to Improve It
Measure, pick the slowest layer, change one thing and measure again. If the Elementor website is still slow, send your host and the PageSpeed Insights report to your host or Elementor support. If you would like a person to look, wpallsolution offers independent plugin support, and our Elementor development page explains how we build Elementor sites. We cannot promise a score without seeing your setup.
Last reviewed: October 19, 2026. Elementor is a trademark of its owner. wpallsolution is not affiliated with or endorsed by Elementor.
An Elementor popup needs conditions, a trigger and passing rules before it shows. Check each in order, plus the multiple-popup option and…
The free Elementor plugin covers more than many expect, but Pro adds the Theme Builder, popups, forms and WooCommerce tools. See which…
Moving from Elementor to a block theme is a rebuild, not a switch. Use this checklist to audit, test on staging and…
Black FridayCyber Monday sale
Before you go,
Our biggest discount of the year on the first payment of every maintenance plan.
BF2026 at checkout