Why Your Website Is Slow and What It Is Costing You
53% of mobile users leave a page if it takes more than 3 seconds to load. That number is from Google's own research and it has been consistent for years. If your site takes 5 seconds on mobile, you are losing more than half your mobile visitors before they see a single word of your content.
Slow websites are not a design problem. They are a revenue problem. Here are the 6 most common causes on WordPress sites, ordered by how much impact fixing them will have.
1. Unoptimised Images
This is the most common cause of slow WordPress sites and the highest-impact fix. A full-resolution photo from a DSLR can be 8 to 15 megabytes. Served at that size to a mobile user, it takes seconds to download. Most of the time the image is being displayed at 400 pixels wide. The file size should be nowhere near 15MB.
The fix has 3 parts. First, resize images to the dimensions they are actually displayed at before uploading. Second, compress them. Tools like Squoosh, ShortPixel, or Imagify will reduce file size by 60 to 80% with no visible quality loss. Third, serve images in WebP format. WebP files are typically 30% smaller than equivalent JPEGs. Modern browsers support it universally.
If your site has 40 unoptimised images, this fix alone can cut your page load time in half.
2. Too Many Plugins
WordPress makes it easy to install plugins. That ease creates a habit of reaching for a plugin every time you need something. Over time, a site accumulates 30, 40, sometimes 60 active plugins. Each one adds PHP execution on the server, often adds CSS and JavaScript to every page, and represents a potential source of conflict with every other plugin.
Audit your plugins. Go through every single one and ask: is this actively being used, what would break if I deactivated it, and is there a leaner way to do what it does? Deactivate plugins you are not sure about and test the site. You will often find things that were installed for a one-off task and never removed.
A site running 20 well-chosen plugins will outperform a site running 45 every time.
3. No Caching
Every time a WordPress page loads without caching, the server runs PHP, queries the database, assembles the HTML, and sends it to the browser. That process takes time. Caching stores the assembled HTML so the server can skip that process for subsequent visitors.
Without caching, a modest amount of simultaneous traffic can overwhelm a WordPress server. With caching, the same server handles far more requests with a fraction of the processing overhead.
WP Rocket is the most effective caching plugin available for WordPress. It handles page caching, browser caching, and several related optimisations. If you are not using a caching plugin, this is the first thing to install after fixing your images.
4. Slow Hosting
The hosting environment has a ceiling. If you are on cheap shared hosting where your site shares a server with hundreds of others, there is a limit to how fast your pages can load regardless of how well you have optimised everything else.
Shared hosting is fine for low-traffic sites that are genuinely low-stakes. If your site is driving business, it needs better infrastructure. Managed WordPress hosting from providers like Kinsta, WP Engine, or Cloudways sits on faster hardware, uses server-level caching, and is configured specifically for WordPress workloads.
The difference in Time to First Byte between budget shared hosting and managed WordPress hosting is often 300 to 600 milliseconds. That is significant. It is also the single most expensive fix on this list, though the pricing gap has narrowed considerably.
5. Render-Blocking Scripts
When a browser loads a web page, it builds the page from top to bottom. If it encounters a JavaScript file that is not marked as async or deferred, it stops, downloads the script, executes it, and then continues building the page. This is called render-blocking. The user sees nothing until the script is done.
Most JavaScript on a website does not need to run before the page is visible. Analytics, chat widgets, marketing pixels, form libraries: none of these need to block the page from rendering. Mark them as async or defer. Load them after the main content.
This is often the cause of poor Interaction to Next Paint (INP) scores in Core Web Vitals. The main thread is occupied with JavaScript and cannot respond to user input.
6. No CDN
A CDN (Content Delivery Network) stores copies of your static assets, images, CSS, JavaScript, fonts, across servers in multiple locations around the world. When a user requests your site, the CDN serves those assets from the location closest to them.
For an Adelaide business, this matters most when you have customers in other states or internationally. Without a CDN, every request for an image travels to your server wherever it is hosted and back. With a CDN, that image is served from a server 50 kilometres away instead of 2,000.
Cloudflare offers a CDN on its free plan. It takes about 30 minutes to set up and it reduces load times measurably, particularly for users who are not close to your hosting server.
The Order to Fix These
Do not start with hosting. Start with images, then plugins, then caching. These 3 fixes are free or near-free and have the most impact. If your site is still slow after addressing all 3, look at render-blocking scripts. Then evaluate hosting. Add a CDN alongside the hosting upgrade.
A site that has addressed all 6 of these problems will load in under 2 seconds on mobile for most users. That is the target. Everything above 3 seconds is costing you conversions.
If you want to know exactly what is slowing your site down before committing to any fixes, we run a full performance and CRO audit as part of our website engagements.