Sydney Theme Speed: The Hero Slider, the Elementor Front Page and the Settings That Help

How Sydney decides what each page downloads

Credit first. Sydney does not dump every file on every page. Its enqueue code in functions.php loads several pieces only when a feature or plugin needs them, which is more discipline than many Customizer themes of its age show. Read the list, though, and one condition stands out: a large share of it switches on whenever Elementor is active, and on most Sydney sites Elementor is active on every page.

So a Sydney page without the slider, without Elementor and without comments is lighter than a Sydney demo suggests. A typical Sydney business site has all three of the heavier conditions met on its front page. That is where the work is.

The full screen slider is the slowest thing on most Sydney front pages

Sydney sets its hero in the Customizer under Hero area, then Hero type. Front page header type offers four choices: Full screen slider, Image, Video, and No header (only menu). A second control, Site header type, sets the hero for every other page. The slider takes up to five slides, each with an image, a title and a subtitle, plus a call-to-action button, a Slider speed setting and a Mobile behavior for the slider images choice between full screen and responsive.

Choose the slider and Sydney loads hero-slider.js, whose own header identifies it as Superslides version 0.6.3-wip from December 2013, running on jQuery. Each slide's photo is set as an inline CSS background image on a div, and the template also prints an image element for every slide as the mobile version. Those image elements carry no lazy-loading attribute, and browsers download image elements even when CSS hides them. A five-slide hero can therefore fetch five large photos before the visitor has seen one.

Background images also arrive late. The browser's preload scanner looks for image elements in the HTML; it cannot see a photo named inside a style attribute until it builds the page's styles. So the first slide, very often the Largest Contentful Paint element, waits on HTML, CSS and the slider script before it settles. The fix is plain: set Front page header type to Image, or to No header and build a one-image hero in Elementor using a real image widget. If marketing insists on rotation, cut to two slides and compress both.

A slider asks five photographs to compete for one first impression, and the visitor waits for all five.

Five toggles under General, Performance, and one under Misc

Sydney keeps its speed switches in the Customizer under General, then Performance. Most are off by default, and aThemes links its own performance guide from the same panel. Here is what each one does, from the theme's own control labels and code:

1. 1.Load Google Fonts Locally? Off by default. Serves the theme's Google Fonts from your own server instead of Google's. The control's description limits it to fonts loaded by the theme, not by third-party plugins, and vendor support says fonts chosen only in Elementor are not covered. Turn it on.
2. 2.Disable Google Fonts preconnect. Off by default. Once fonts are local, the early connection to Google's servers buys nothing; switch it on after the option above.
3. 3.Disable Emojis. On by default. Leave it on; it removes WordPress's emoji script and its DNS hint.
4. 4.Disable jQuery Migrate. Off by default. Removes the compatibility layer that some older plugins still lean on. Turn it on in staging, click through forms, sliders and the menu, then decide.
5. 5.Defer block styles. Off by default. Checks whether a post has block content and defers the block stylesheet when it does not, which suits Elementor-built pages. Turn it on and check a blog post afterward.

The sixth switch lives elsewhere, under General, then Misc: Enable preloader, which is on by default. It prints a spinner over the page. The theme's footer script removes it once the document is ready, then waits 600 milliseconds before hiding it completely. Every visitor watches a spinner for at least that long on top of the real load time. Turn it off. A fast page does not need a curtain, and a slow page is not improved by one.

Elementor front pages: where Sydney hands the weight to someone else

On activation Sydney turns off Elementor's global color and typography schemes, so the Customizer stays in charge of the look. Everything else on an Elementor page is Elementor's: each section, column and widget adds wrapper markup, entrance animations add script work, and Sydney Pro's own Elementor widgets, such as Timeline, Pricing Tables and Food Menu, bring their own assets onto the pages that use them. The starter sites, three free and seventeen in Pro, are built to impress in a demo. Many owners import one and keep every section.

Elementor has its own Performance settings, and they belong in this tune-up. Optimized Image Loading adds fetchpriority=high to the image Elementor identifies as the likely LCP and lazy-loads images below the fold. Lazy Load Background Images holds off section backgrounds until the visitor scrolls near them. Element Caching stores rendered widget HTML so the server does less work per request. Turn them on in staging, then check the hero, the mobile menu and any form.

The structural fixes matter more than the switches. Delete sections nobody scrolls to. Replace background-image heroes with an image widget. Remove entrance animations from anything above the fold. If an add-on pack supplies one widget, rebuild that widget from core parts and uninstall the pack. Our Elementor slow website guide goes deeper on the builder side, and page builders vs Next.js explains why builder output carries a floor you cannot tune below.

Speeding up a Sydney site in nine moves

1. 1

   Measure the front page and one inner page

   Run both through PageSpeed Insights on mobile and note which element is the LCP. On Sydney it is usually the first slide or the hero background. Our PageSpeed Insights guide explains the report.

2. 2

   Work on a staging copy

   Sydney updates have moved headers before; 2.69 changed sticky header colors for at least one owner. Make every change below on a copy first.

3. 3

   Turn off the preloader

   General, then Misc, then Enable preloader. The cheapest win on the list.

4. 4

   Replace the slider

   Set Front page header type to Image, or build a single-image hero in Elementor with an image widget sized for phones.

5. 5

   Set the Performance toggles

   Load Google Fonts Locally, Disable Google Fonts preconnect, Disable jQuery Migrate and Defer block styles, testing forms and menus after each.

6. 6

   Settle the fonts

   Use the same one or two families in the Customizer and in Elementor, with no more than three weights, so nothing slips past the local option.

7. 7

   Enable Elementor's image and caching features

   Optimized Image Loading, Lazy Load Background Images and Element Caching, then confirm the hero is not lazy-loaded.

8. 8

   Prune widgets, add-ons and plugins

   Remove unused sections, animations above the fold, and any add-on pack that supplies a single widget.

9. 9

   Cache, measure again, test on a phone

   Add one page cache, rerun the same pages and tap through the header and mobile menu on a real phone before pushing live.

How Sydney pages score on LCP, CLS and INP

Largest Contentful Paint on Sydney is decided by the hero. A slider image set in a style attribute, a preloader covering the page and render-blocking stylesheets from Bootstrap, the theme and Elementor all stand between the request and the paint. A single image element, sized for the phone and marked high priority, removes most of the delay. WordPress vs Next.js on LCP shows why the background-image pattern is so costly, and slow LCP on a WordPress theme lists the other usual suspects.

Cumulative Layout Shift comes from things that settle after first paint: a slider whose script sizes its container, web fonts swapping in and reflowing headlines, and Elementor sections whose height depends on images without dimensions. Give the hero a fixed height on mobile and set width and height on every image. The mechanisms are in the CLS comparison.

Interaction to Next Paint suffers when the main thread is busy. On a Sydney and Elementor site that means jQuery, scripts.js, Elementor's frontend scripts, add-on widgets and whatever tracking tags sit in the head. The mobile menu is the tap visitors make first, so test it on a mid-range phone. INP on WordPress and Next.js explains how a slow tap is counted.

What Sydney's settings cannot reach

• Bootstrap stays. sydney_enqueue_bootstrap loads the stylesheet on every page, and the theme's grid depends on it. Removing it means restyling the theme by hand, which is a rebuild in disguise.
• Elementor brings jQuery with it. With Elementor active, scripts.js loads site-wide and pulls in jQuery, so even a page built in blocks pays for the builder's presence.
• The local font option has a gap. Fonts set only in Elementor stay on Google's servers unless you handle them separately.
• Updates can undo your header. Forum reports show header builder options vanishing and sticky header changes after updates. Keep a staging habit; Sydney header not showing and Sydney CSS not updating cover the aftermath.
• The server is not the theme's job. A slow host, a crowded plugin list and an uncached database query stay slow whatever Sydney does.

None of these is a scandal. They are what a Customizer theme built on Bootstrap and paired with a page builder looks like when measured honestly. Most small business sites can still reach passing Core Web Vitals on Sydney after the steps above. The question is how much effort it takes to stay there after the next redesign, the next add-on and the next update.

When a faster Sydney still is not fast enough

Keep Sydney if the site is a modest brochure or portfolio, passes after tuning and is edited by someone who likes Elementor. The full case for and against the theme is in our Sydney review, and it is a fair one.

Speed becomes a reason to move when the site earns money from paid traffic or local search. Landing pages that load behind a slider cost ad spend. Ten service pages built from the same heavy Elementor template cost rankings. A Next.js build prerenders each page, serves it from a CDN, sizes every image with next/image and self-hosts fonts with next/font, and no plugin added later can put a slider script back. It costs more up front and needs a developer for layout changes. Sydney vs Next.js weighs the trade row by row; Sydney to Next.js and moving Elementor content to Next.js cover the move itself.

Owners who are used to Elementor get plain fields and a real preview in Athena CMS, with Picasso making sure every image is described and sized. If you would rather keep Sydney and have it tuned, our theme speed optimization service follows the steps above on a staging copy and reports what changed. More theme guides are in the WordPress themes section.