How fast should my website load?

Under 2.5 seconds for the main content, which matches Google's Largest Contentful Paint threshold for a good score. Under 2 seconds is the practical target for a local business site, and modern custom-built sites achieve well under 1 second.

Why is my WordPress site so slow?

Usually the stack, on cheap shared hosting, running a heavy theme, a page builder and 20+ plugins each loading their own scripts. Each layer adds weight. Removing unused plugins, compressing images and adding caching recovers most of it without a rebuild.

Does website speed affect Google rankings?

Yes. Core Web Vitals are a confirmed ranking signal, and speed compounds through user behaviour: slow pages get abandoned, abandonment reads as a poor result, and rankings slip. Speed also decides whether visitors who do arrive stay long enough to convert.

How do I test my website speed properly?

Run pagespeed.web.dev and read the top Field Data section, which shows real visitor measurements rather than a one-off lab test. Test your homepage and your most important service page, on mobile first. The Opportunities list below tells you which of the 12 fixes applies.

Why Your Website Loads Slowly: 12 Fixes That Work

Load your own website on your phone, on mobile data, outside your office wifi. Count the seconds before you can read it. If you got past three, more than half the people who tried just gave up, because Google's research puts mobile abandonment at 53% beyond the three-second mark, and every additional second strips roughly 7% off conversions.^[1] Speed is a revenue setting, and yours is probably set wrong.

SECTION 01What slow actually costs you

Run the numbers on a typical trades site getting 500 mobile visits a month. At a 5-second load, the three-second abandoners cost you around 265 visits before your page even renders. If 5% of visitors normally enquire and an average job is worth $800, that single setting costs five figures a year. The maths gets worse for ecommerce and worse again for paid traffic, where you pay for the click and the site throws it away.

SECTION 02Diagnose it in five minutes, free

Open pagespeed.web.dev, enter your homepage, and read two things. Field Data at the top shows what real visitors experienced over 28 days, with the key metric LCP (Largest Contentful Paint) needing to sit under 2.5 seconds. The Opportunities section below names your specific problems in order of wasted time. Match each one to the fixes below. Test your top service page too, since customers land there from search more often than the homepage.

SECTION 03Fixes 1-3: images (the usual culprit)

1. Compress and convert to WebP

A phone photo uploads at 4-8 MB; the web needs 100-300 KB. Run every image through Squoosh or TinyPNG and serve WebP, which cuts size 25-35% over JPEG at the same quality.

2. Size images to their container

Serving a 3000px image in a 600px slot wastes every extra pixel. Export at the display size, at 2x for retina screens at most.

3. Lazy-load below the fold

Add loading="lazy" to images the visitor can't see yet, so the browser spends its opening seconds on the content that matters. Never lazy-load the hero image itself.

SECTION 04Fixes 4-6: hosting, caching, CDN

4. Fix slow hosting

If your server takes over 600ms to send the first byte (PageSpeed reports this as TTFB), no front-end fix saves you. $4/month shared hosting sits behind everyone else on the box. Move to quality Australian hosting, or static hosting for brochure sites, which is what we build client sites on.

5. Turn on caching

Caching serves a saved copy instead of rebuilding the page per visitor. On WordPress, one well-configured cache plugin routinely cuts load times 20-50%.

6. Add a CDN

A CDN stores your files in cities near your visitors. Cloudflare's free tier alone shaves real time for regional Australian audiences reaching a Sydney server.

SECTION 05Fixes 7-9: builders, plugins and scripts

7. Audit the page builder

Elementor, Divi and friends ship megabytes of CSS and JS to every page whether used or not. Keep the builder if you must, but strip unused modules, or rebuild key landing pages clean.

8. Delete plugins

Each active plugin can add scripts, styles and database queries. Sites running 30 plugins usually need 10. Deactivate, retest, repeat.

9. Cut third-party scripts

Chat widgets, heatmaps, three analytics tools and a Facebook pixel all load before your content settles. Keep what you act on monthly; delete the rest and defer what remains.

SECTION 06Fixes 10-12: fonts, redirects, layout shift

10. Trim web fonts

Two font families, the weights you use, preloaded. Five families in nine weights blocks text rendering while they download.

11. Remove redirect chains

http to https to www to the final page adds a round trip per hop, brutal on mobile networks. Point everything at the final URL in one jump.

12. Stop layout shift

Content jumping while ads, images and embeds load is CLS, a Core Web Vital. Give every image and embed fixed width and height attributes so the browser reserves the space.

SECTION 07What order to do it in

Work your PageSpeed Opportunities list top-down; it already ranks by seconds saved. For most local sites the winning order runs images, hosting, caching, then plugin surgery, and those four typically recover 80% of the available speed. Retest after each change so you know what moved the needle, and screenshot the before scores. Watching red turn green is half the motivation to finish the list.

REFERENCESSources

[1] Google mobile performance research (53% abandonment beyond 3s); Akamai (7% conversion loss per second of delay); Google Core Web Vitals thresholds (LCP under 2.5s).

Written by Automatrix

Want the diagnosis done for you?

Our free audit includes a full speed teardown: what loads, what blocks, what it costs you in leads, and the exact fix list in priority order. Most Albury Wodonga sites we test have three fixes worth 80% of the gain.

Get my free speed audit → See our web design work