Hello Biz Speed: Tuning an Elementor Site on a Theme That Has Stopped Growing

A small theme carrying a large builder

Elementor does not document how Hello Biz loads CSS or JavaScript, and it publishes no performance claims for it. The theme package itself is modest: PHP templates and a theme.json. What happens next is the interesting part. The Hello+ setup wizard installs Elementor, applies a business kit, and takes over the header and footer through two filters in the theme's source, hello-plus-theme/display-default-header and its footer twin. From that moment the theme is mostly a frame. The picture inside it is drawn by three other parties.

So when someone asks whether Hello Biz is fast, the honest reply is that the question is aimed at the wrong layer. The Hello Biz review covers the theme as a whole; this page is about where the bytes on your pages actually come from and what you can do about each source.

Maintenance mode changes what speed work is worth

Elementor's help articles, updated August 18, 2026, say Hello Biz will be moved into maintenance mode soon, with no new features, and recommend moving to Hello Themes instead. No date was given. For speed, that means two things. First, nothing faster is coming from the theme: any performance gains from here on arrive through Elementor and Hello+ updates. Second, money spent on deep theme-level surgery, such as rewriting templates in a child theme, buys improvements for a theme you will probably leave.

The sensible budget goes to portable work. Compressed and correctly sized images move with you. A shorter plugin list moves with you. Elementor settings stay put if you switch to Hello Elementor, because they live in Elementor, not in the theme. Even a full move to Next.js reuses the image work and the knowledge of which features the business actually needs. Spend on those first and the money is not stranded when the theme is.

Tune the parts that will come with you, not the frame you are about to leave.

Finding the weight, one folder at a time

Here is a method that works on any Hello Biz page and needs nothing but a browser. Open the page in Chrome, open developer tools, choose the Network panel, tick Disable cache and reload. Then type each folder below into the filter box and note the number of requests and the transferred size. Do it on the homepage and on one plain text page, such as the privacy policy, so you can see what loads everywhere and what loads only with the kit sections.

Most owners find the theme row nearly empty and the last two rows surprisingly full. That result is the point of the exercise. If Elementor's rows dominate, Elementor slow website goes deeper on the builder, and the Elementor repair hub collects the rest of what tends to go wrong with it.

The Elementor switches that matter on a Hello Biz site

Since version 3.22, Elementor's settings page has a Performance tab. Elementor's help center describes these options; test each one on a staging copy before switching it on live.

• CSS Print Method. External File writes each page's styles to a separate stylesheet the browser can cache; the alternative prints them into every page. Elementor marks the external stylesheet as recommended.
• Optimized Image Loading. Per Elementor, it adds fetchpriority high to the likely LCP image and lazy loading to images below the fold. Turn off any second lazy-loading system if you use it.
• Load Google Fonts Locally. Elementor downloads the fonts in use to /wp-content/uploads/elementor/fonts/ and points your CSS at them, which removes the trip to Google's servers.
• Element Cache Expiration. Controls how often cached widget output is cleared, if you use Element Caching, which Elementor labels experimental and says to use only on static elements.
• Optimized Markup, on the Features tab. Elementor's switch for leaner HTML output. Fewer wrapper elements mean less for a phone to lay out.

Kits also bring typography choices. Every extra Google font family and weight a kit sets in Site Settings is another file, local or not. Two families in two weights each is a reasonable ceiling for a small business site.

A Hello Biz tune-up that survives a theme switch

1. 1

   Take a baseline on a phone profile

   Test the homepage, the main service page and the contact page in PageSpeed Insights. Write down the LCP element on each. Our guide to mobile speed on WordPress themes lists what else to watch.

2. 2

   Copy the site to staging

   Elementor settings apply site-wide and can change how pages render. Test on a copy, not on the site that answers the phone.

3. 3

   Set the Performance tab

   CSS Print Method to External File, Optimized Image Loading on, Load Google Fonts Locally on. Clear Elementor's generated CSS afterward, then retest.

4. 4

   Shrink the kit's images

   Replace the kit's hero and ZigZag photos with images sized close to their displayed width and compressed. This is the single largest win on most kit sites, and it moves with you to any platform.

5. 5

   Cut fonts to what the brand needs

   Trim the kit's typography in Site Settings to two families and the weights you actually use.

6. 6

   Remove plugins that duplicate Hello+ or Elementor

   If Form Lite handles your contact form, a separate form plugin is dead weight. Check each remaining plugin with the folder method above.

7. 7

   Retest, then write the changes down

   Record every setting changed. If you later move to Hello Elementor or another platform, the list tells the next person what was done and why.

Layouts that shift or break after a setting change are covered in Hello Biz layout broken, and a header that disappears is in Hello Biz header not showing. Our theme speed optimization service runs this list for you on staging.

LCP, CLS and INP on a kit-built business page

LCP: the Hero widget's picture

On a kit homepage the largest element is usually the Hero or Flex Hero image, or the headline over it. If the image is set as a section background, the browser cannot find it until the CSS has arrived and been read, which delays it no matter how small the file. Where you can, use an image element for the main hero picture, and keep that first image out of every lazy-loading system. Slow LCP on WordPress themes and WordPress vs Next.js on LCP explain why.

CLS: logo, contact button and late fonts

The Hello+ Header widget has sections for Site Identity, Navigation, a Contact Button and a Call to Action. A logo without set dimensions, or a font that swaps in with different widths, can shift that row as the page settles. Give the logo fixed dimensions and keep header fonts to one family. Banners injected above the header by plugins are the other usual cause. See WordPress vs Next.js on CLS.

INP: taps on the hamburger

Forum reports describe Hello Biz mobile submenu entries that fail to expand, which is a function problem rather than a speed one, but it lands in the same place: the menu is the first thing a phone visitor taps. Slow responses usually come from third-party scripts competing for the main thread. WordPress vs Next.js on INP covers the mechanism.

What no Hello Biz setting can reach, and where to go next

• Elementor's structure. Sections, containers and widgets each write wrapper elements. Optimized Markup trims some; it cannot remove the builder model.
• Hello+ asset loading. Which files the widgets load, and when, is Elementor's code, updated on Elementor's schedule.
• A frozen theme. Once maintenance mode starts, no theme-level performance work is coming, and compatibility fixes are the most to expect.
• Server time. Elementor pages are assembled by PHP on every uncached request; only caching and hosting help there.

There are two exits. The short one follows Elementor's own advice to move to its Hello Themes: switch to Hello Elementor, keep your Elementor pages, and tune from there with the Hello Elementor speed guide. Hello+ widget content needs checking after any theme change; Elementor theme conflicts covers what to look for.

The longer exit makes sense when speed is the business case: paid traffic to landing pages, a phone-first audience, or a site that must rank against faster competitors. A Next.js build prerenders pages, self-hosts fonts with next/font and resizes images with next/image, with no builder runtime on the page. It costs more up front and needs a developer for layout changes. Compare honestly in Hello Biz vs Next.js and page builders vs Next.js, then read moving a Hello Biz site to Next.js. Every other theme we cover is in the WordPress themes hub.