Skip To Section

A slow website isn’t just annoying — it costs real money. When pages take too long to load, customers bounce, online orders drop, and Google quietly moves you further down the search results.

This case study walks through how I rebuilt a slow, heavy Elementor website for a Sunshine Coast café. If your site is sluggish or unstable, this is the type of project handled through Website Performance Rescue or, for urgent cases, an Emergency Website Rescue.

A Sunshine Coast café frustrated by a slow, unstable website

The café relied heavily on online menu views and table enquiries — yet their homepage was taking 7–9 seconds to load on mobile.

Customers complained that the site “wouldn’t load”, which meant lost bookings and fewer online orders. The owner had been told “that’s just Elementor”, but the truth is: slow websites can always be fixed when you know where the bottlenecks are.

They contacted me to diagnose the issue and rebuild the site for performance and stability.

Why Elementor sites often become slow over time

Elementor is a powerful builder, but it can become slow when:

too many widgets are used
sections are deeply nested
unoptimised images are uploaded
unused scripts load on every page
the hosting environment is limited
old builder templates accumulate

Many websites only need a fraction of what Elementor loads by default. Cleaning out the excess is one of the fastest ways to improve speed.

Step 1: Auditing the page builder, hosting and heavy assets

I began with a full audit:

tested page speed on mobile and desktop
reviewed the site’s hosting resources
inspected the Elementor structure for nested sections
located oversized hero images (up to 2.5MB each)
identified unused widgets and scripts
checked caching configuration

The audit revealed what I see often: a site designed for looks rather than performance. A common problem — but one that can be fixed.

Step 2: Rebuilding key pages using a lightweight structure

Instead of performing band-aid fixes, I rebuilt the café’s busiest pages with a lean, lightweight layout that didn’t rely on heavy Elementor widgets.

This included:

reducing deep nested sections
replacing bloated widgets with lighter alternatives
removing unnecessary animations
refactoring the page structure for accessibility
cleaning up unused Elementor templates

The café kept their original design style — just without the bulk. The experience was identical, but the structure became dramatically more efficient.

This process is a core part of my Website Performance Rescue service.

Step 3: Converting images and optimising performance settings

Most slow websites suffer from huge images, especially sites with food photography.

Typically, my aproach is:

convert all images to WebP
resize oversized hero images
add responsive image attributes
enable server-level caching
configure browser caching rules
optimise CSS and JS delivery
improve Core Web Vitals (LCP, INP, CLS)

These changes alone shaved several seconds off the load time.

To prevent the site from becoming slow again, the café chose one of my website maintenance plans, which includes monthly updates, monitoring and optimisation.

The result: a fast, stable and mobile-friendly website

After the rebuild, the café saw immediate improvements:

Mobile load time dropped from 7–9 seconds to 1.8 seconds
Desktop load time dropped to 1.2 seconds
Customers stopped complaining about loading issues
Online order conversions increased
Hosting resources were no longer maxed out

A fast website makes a measurable difference — especially for local businesses competing for attention.

What businesses can learn from this performance rescue

Here are the biggest takeaways:

1. Elementor isn’t slow — poorly built Elementor sites are slow.
A lean structure performs just as fast as any hand-coded layout.

2. Most speed problems come from oversized images and bloated layouts.
Fixing the structure solves 80% of the issue.

3. Cheap or overcrowded hosting can make a fast site slow.
Performance relies on both the site architecture and the server.

4. A performance rescue is often cheaper and faster than a full redesign.
Rebuilding only the heavy pages saves time and money.

5. Ongoing maintenance prevents slowdowns.
Websites accumulate bloat — regular optimisation keeps everything running fast.