Web performance

The research on this is unambiguous: speed affects user behaviour. Google's own data shows that as page load time increases from one second to three seconds, the probability of a user leaving increases by 32%. At five seconds, that figure reaches 90%.

Every additional second of load time represents customers who left before they saw what you were offering.

Speed and conversion are directly correlated. Walmart found that for every one-second improvement in page speed, conversions increased by 2%. For a business with meaningful online revenue, the maths on a one-second improvement are compelling.

It doesn't take a large site or significant traffic to make this matter. Even a local Brisbane business with a few dozen monthly enquiries can see meaningful differences from a properly optimised site.

In 2021, Google introduced Core Web Vitals as official ranking signals. These are a set of performance metrics that measure real user experience, how fast content loads, how quickly a page responds to interaction, and how stable the layout is as it loads.

A slow website isn't just losing customers who leave. It's being ranked lower in search results, meaning fewer potential customers are finding it in the first place.

This one is harder to measure but worth naming: a fast, stable, responsive website communicates competence. A slow site with a layout that jumps around and images that take three seconds to appear communicates the opposite.

For service businesses in particular, where the website is often the first impression, performance is part of the brand.

Images are the most common cause of slow websites. A high-resolution photograph exported directly from a camera and placed on a web page is a performance disaster. Images should be:

- Compressed without visible quality loss

- Sized appropriately for the viewport they'll appear on (not a 3000px-wide image displayed at 400px)

- Served in a modern format like WebP, which is significantly smaller than JPEG or PNG at equivalent quality

- Lazy loaded below the fold, so they don't block the initial page render

Most sites fix 40–60% of their image performance issues by addressing these four points alone.

Modern websites load a lot of JavaScript, tracking scripts, third-party integrations, interactive features, analytics tools. Each script is a download that can block the page from rendering.

JavaScript performance optimisation involves: deferring non-critical scripts so they load after the page is visible, removing unused scripts entirely, and code-splitting large JavaScript bundles so only what's needed for a specific page is loaded.

Some page resources, certain CSS files and JavaScript, block the browser from rendering the page until they've fully downloaded. These render-blocking resources are a common cause of high Largest Contentful Paint scores.

The fix involves auditing which resources are genuinely needed before render, deferring the ones that aren't, and inlining critical CSS directly in the HTML to avoid additional round-trips.

A slow server is a slow site, regardless of how well the code is optimised. Shared hosting, the cheapest tier of web hosting, typically provides minimal server resources and no performance guarantees. Sites on shared hosting are competing for resources with dozens or hundreds of other websites on the same server.

Performance-focused hosting involves: dedicated resources (VPS or container-based hosting), a Content Delivery Network (CDN) to serve assets from servers geographically close to visitors, and appropriate caching at the server level.

WordPress with fifteen plugins is not a well-optimised platform. Every plugin adds JavaScript, CSS, and server-side processing. Even well-regarded plugins can add significant performance overhead.

This is one of the architectural advantages of headless CMS development, by decoupling the content management system from the frontend, the frontend can be built as a static site or edge-rendered application, with no CMS overhead on the page load path.

Analytics, live chat, cookie consent tools, marketing pixels, A/B testing scripts, these all load on your site on behalf of external services. Each one adds weight and latency. In aggregate, a site with ten third-party scripts can lose multiple seconds of load time to requests it doesn't control.

Auditing third-party scripts and removing the ones that don't justify their cost is often an easy performance win.

A frontend that's statically generated or server-rendered at the edge, meaning pages are pre-built and served instantly, rather than generated on demand by the CMS. This is the biggest single performance lever, and it's an architectural decision, not a settings tweak.

All images compressed, sized correctly, served in WebP format, and lazy loaded below the fold.

Code-split bundles, deferred non-critical scripts, removed unused scripts.

A CDN for static assets, server-side caching, appropriate server resources.

Audited and reduced to only those that justify their performance cost.

Ongoing performance tracking in Google Search Console and real-user monitoring to catch regressions.