Hello Elementor Speed: How to Speed Up an Elementor Site When the Theme Is Already Tiny

What Hello itself sends to the browser

In version 3.5.1, Hello loads up to three static stylesheets: reset.css at 5,829 bytes, theme.css at 5,827 bytes and header-footer.css at 7,534 bytes, sizes taken from the wordpress.org package. That is about 19KB before compression. Elementor's marketing describes the theme two ways, as using 6KB of resources in its help center and as under 30KB, loading in about a quarter of a second, on its product page. Those are the vendor's figures, and they disagree with each other; the files sit between them.

Hello has no dynamic CSS system and no font setting. Its header and footer styling comes from Elementor Site Settings, and the only jQuery dependency we found in the theme source belongs to an Elementor editor script, not the front end. So the theme's speed controls are subtractive. They live on a settings page at WP Admin > Hello, split across three tabs, and every toggle is off by default. Elementor's own help article warns that some of them affect content and should be tried on staging first.

Turn on the first three where they apply and the theme's footprint drops close to nothing. That is worth doing, and it will not change a failing score by itself. The rest of this page is about Elementor, because that is where a Hello site's speed is decided. Our Hello Elementor review covers the theme's other settings and its support quirks.

Elementor's speed settings, by name and by tab

Elementor has moved its settings more than once, so older tutorials point to menus that no longer exist. As of October 2026, Elementor's help center places them under Elementor > Editor > Settings, spread across three tabs. These are the ones that change what a visitor downloads, with what each does in Elementor's own description.

Performance tab

• CSS Print Method. Prints Elementor's CSS as an independent stylesheet, which Elementor recommends, or inside each page. Choose the stylesheet so browsers cache it.
• Optimized Image Loading. Adds fetchpriority="high" to the image Elementor judges to be the LCP image and loading="lazy" to images below the fold. Elementor's help center says this typically improves page loading times by 5 to 10 percent; that is the vendor's figure.
• Lazy Load Background Images. Applies lazy loading to every background image except the first one on the page.
• Optimized Gutenberg Loading. Dequeues block editor scripts and styles that Elementor-built pages do not use.
• Load Google Fonts Locally. Downloads the fonts in use to /wp-content/uploads/elementor/fonts/ and rewrites the CSS to serve them from your server. Since Elementor 3.32.1 it is off by default, and sites that had it on before must enable it again.
• Element Cache and Element Cache Expiration. Controls the server-side element cache described below, and how often it is cleared.

Features tab

Inline Font Icons is listed as stable. It renders icons as inline SVG instead of loading the Font Awesome and eicons libraries with their CSS and font files. Elementor notes that it does not convert Font Awesome Pro icons, which need the kit itself set to SVG. Element Caching and Optimized Control Loading sit here as experiments; the second speeds up the editor rather than the public page.

Advanced tab

Google Fonts can be set to Disable to stop Elementor loading them at all. Google Fonts Load chooses the font-display behavior: Default, Blocking, Swap, Fallback or Optional. Load Font Awesome 4 Support adds a shim script for icons picked under the old library; switch it to No once no Font Awesome 4 icons remain.

Why most Elementor sites on Hello end up slow

Elementor's own speed checklist asks owners to switch to the Hello theme as a test, which tells you where the vendor thinks the problem usually sits. On a site already running Hello, the remaining weight is the design itself and what was installed to make it. These are the patterns we see most.

• Deep layouts. Every section, column, container and inner container is a wrapper element. A page assembled by nesting adds hundreds of elements the browser must lay out before it paints. Elementor promotes its container model as the leaner structure; older section-and-column pages are worth converting when they are rebuilt.
• Add-on widget packs. A third-party pack installed for one widget often registers its CSS and scripts across the whole site.
• Motion. Entrance animations, scrolling effects and sliders all run scripts, and an animated hero can keep the LCP element hidden until its animation starts.
• Font sprawl. Site Settings makes it easy to assign a different family to every text style. Each family and weight is another file.
• Popups and forms everywhere. Theme Builder popups and form widgets are convenient, and their assets ride on every page that might trigger them.
• External scripts. Elementor's help center names Google Maps embeds, share counters and avatar images as common culprits.

Hello also has one theme-specific report worth knowing: owners on multiple sites running Hello with Elementor Pro have reported a flash of unstyled content, where the page appears briefly without its styles. That is usually a CSS loading order or caching problem, and it also shows up as layout shift. Hello Elementor CSS not loading covers the checks, and our Elementor slow website repair page covers the builder-wide causes.

Speeding up an Elementor site in nine moves

This order front-loads the free, low-risk changes and saves the ones that can break layouts for last. Use a staging copy; Elementor's help pages make the same recommendation.

1. 1

   Measure the templates that matter

   Test the home page, a Theme Builder single template, an archive and, for stores, a product page in PageSpeed Insights. Write down the LCP element and the field data for each.

2. 2

   Strip what Hello no longer needs

   At WP Admin > Hello, enable Disable theme header & footer if Theme Builder supplies both, and deregister reset.css or theme.css only if a child theme covers them.

3. 3

   Set CSS Print Method to the stylesheet

   Under Elementor > Editor > Settings, Performance tab, choose the independent stylesheet, then regenerate Elementor's CSS files and clear every cache layer.

4. 4

   Turn on the image settings

   Enable Optimized Image Loading and Lazy Load Background Images. Then check the hero in the page source: it should carry fetchpriority="high" and no loading="lazy".

5. 5

   Bring fonts home

   Enable Load Google Fonts Locally, cut Site Settings down to one or two families, and set Google Fonts Load to Swap so text shows in the fallback font immediately.

6. 6

   Replace icon fonts with SVG

   Activate Inline Font Icons, set Load Font Awesome 4 Support to No, and replace any Font Awesome 4 icons the shim was holding up.

7. 7

   Prune widgets, packs and motion

   Remove add-on packs used for one or two widgets, drop entrance animations above the fold, and replace a hero slider with a single image.

8. 8

   Try Element Caching on static widgets

   Only after the front end is lean. Enable it for widgets with no dynamic tags or shortcodes, set a cache expiration, and test logged-out pages carefully.

9. 9

   Add page caching, then re-measure

   Enable page caching and compression at the host or in one caching plugin. Introduce script delay last, test menus and forms after each change, and rerun the baseline.

If the header disappears after step two, Theme Builder conditions are the first thing to check; Hello Elementor header and footer not showing has the routine. A layout that breaks after step three usually points to stale CSS, covered in Hello Elementor layout broken.

LCP, CLS and INP on a Hello and Elementor build

LCP: the hero widget and its background

Optimized Image Loading only helps an image it can see as an image. Many Elementor heroes are container backgrounds, which the browser finds only after parsing CSS. Lazy Load Background Images spares the first background on the page, but first in the document is not always the hero, especially if a Theme Builder header carries a background of its own. Rebuild the hero with an Image widget where you can, keep it out of any entrance animation, and size it for the largest screen it serves. The cross-theme checklist is in WordPress theme slow LCP.

CLS: Theme Builder headers and late fonts

Layout shift on Elementor sites tends to start at the top. A sticky header that changes height as it attaches, a logo without set dimensions, or a header template that loads its CSS after the first paint will push everything below it. Fonts loaded with Swap can also reflow headings when the real face arrives, which is why local fonts and fewer weights matter twice. The reported flash of unstyled content is CLS in its most visible form. Diagnosis steps are in WordPress theme layout shift (CLS).

INP: menus, popups and the scripts behind them

Responsiveness suffers when a tap has to wait for a busy main thread. On Elementor sites that thread is crowded by animation scripts, popups listening for triggers, widget packs and third-party tags. The mobile menu is where owners notice it. Hello's own header offers a dropdown menu with a Breakpoint of Mobile, Tablet or None, and most sites replace it with an Elementor Pro Nav Menu. Whichever you use, test the first tap on a mid-range phone, and if it stops opening after a caching change, see Hello Elementor mobile menu not working.

Element Caching: faster servers, not lighter pages

Element Caching is often recommended as a speed fix, so it deserves a precise description. When enabled, Elementor stores a widget's rendered HTML in the database and serves that copy the next time the element appears, instead of rendering it again. Elementor says this reduces server memory use and time to first byte. Containers, sections, columns, inner sections, grid containers and off-canvas elements are cached automatically; other widgets can be set Active or Inactive under Advanced > Cache Settings.

It does nothing to the bytes a visitor downloads, the images they wait for or the scripts that slow a tap. It also has a sharp edge. Elementor warns that it must not be used on elements with dynamic tags or shortcodes, such as a widget showing the visitor's name, and Elementor still labels the feature experimental. Use it after a page cache, on static content, and test anything personalized while logged out.

The ceiling: what neither Hello nor Elementor settings can lift

Set everything above correctly and an Elementor page still carries Elementor: its front-end framework, the wrapper markup its widgets write, and the Pro modules the design depends on. Settings decide how efficiently that arrives. They cannot make the builder optional. Server response on uncached pages, WooCommerce's own scripts on stores and the update cadence of theme, builder, Pro and add-ons sit outside both settings pages too. Each update can change what a page sends, which is how a site that passed in March fails in June.

For a marketing team that redesigns landing pages every week, that trade is often worth it, and we would tell you to keep Elementor and tune it. When the site's job is leads, bookings or sales and the field data still fails after tuning, the builder is the limit. A Next.js build prerenders pages and serves them from a CDN, self-hosts fonts with next/font, sizes images with next/image and keeps most components off the client with React Server Components. It costs more to build and needs a developer for layout changes. The trade is laid out in Hello Elementor vs Next.js and page builders vs Next.js, and metric by metric in LCP, CLS and INP comparisons.

No theme switch fixes a builder problem. Hello proves it, because there is nothing left to switch.

The move is planned in Hello Elementor to Next.js and, for the builder data, Elementor to Next.js; we keep your URLs and redirect every old one. Athena CMS then gives the marketing team plain fields and a live preview in place of the canvas. If you are tuning instead, our theme speed optimization service and Elementor developers handle it on staging, and the WordPress themes hub and performance guides cover the measurement. Hello Biz owners have their own notes at Hello Biz speed.