Website speed and local SEO for SA small businesses and councils: a practical guide

For most South Australian small businesses, councils and not-for-profits, the website is the first place a customer, resident or buyer checks before they call. If it is slow on a phone, hard to find in search, or shows the wrong opening hours on a map, people quietly go elsewhere. This guide explains, in plain words, how website speed and local search work, what Google actually measures, the fixes that usually matter most, and what to ask a web supplier. It is practical guidance from an Adelaide team, not a promise of rankings: nobody can honestly guarantee a position in search results.

Why speed and local search belong together

Speed and search visibility are usually treated as separate jobs, one for the developer and one for a marketing agency. In practice they overlap:

• Search engines look at the mobile version first. Google indexes the mobile version of a site, so a page that is slow, cramped or missing content on a phone is judged on that version.
• Page experience is part of the picture. Speed and stability are not the main ranking factor, relevant and helpful content is, but a slow page loses visitors before they read anything.
• Local searches are often urgent. Someone searching for a plumber, a clinic or a council service near them is usually on a phone, on mobile data, and ready to call.
• The same fixes help accessibility. Clear headings, descriptive links, alt text and stable layouts help screen reader users, search engines and impatient visitors at the same time (see our WCAG 2.2 guide for SA websites).

Core Web Vitals in plain words

Core Web Vitals are three measurements Google uses to describe how a page feels to real visitors. Google assesses each one at the 75th percentile of page visits, so most of your visitors, not just the ones on fast office Wi-Fi, need a good experience.

Measure	What it means	Good result	Common causes of a poor result
Largest Contentful Paint (LCP)	How long until the main content, usually the hero image or headline, appears.	2.5 seconds or less	Huge hero images, slow hosting, render-blocking fonts and scripts, no caching.
Interaction to Next Paint (INP)	How quickly the page responds when someone taps a button, opens a menu or types in a form.	200 milliseconds or less	Heavy JavaScript, page builders, chat widgets, tag managers and tracking scripts competing for the phone’s processor.
Cumulative Layout Shift (CLS)	How much the page jumps around while it loads.	0.1 or less	Images without set sizes, late-loading banners and cookie bars, ads and web fonts that swap in late.

INP replaced an older measure, First Input Delay, in 2024, so older reports and plugins may still talk about the previous metric.

Lab scores versus real visitors

There are two kinds of measurement, and suppliers sometimes mix them up:

• Lab data comes from a test run on demand, for example Lighthouse in Chrome or the lab section of PageSpeed Insights. It is great for finding problems and checking a fix before it goes live.
• Field data comes from real Chrome users visiting your site over the previous 28 days, shown in PageSpeed Insights and the Core Web Vitals report in Google Search Console when your site has enough traffic.

A score of 100 in a lab test on a fast laptop does not mean your customers on older phones have a good experience. Ask for both, test on a mid-range phone, and judge improvements by the field data trend over the following weeks.

The fixes that usually matter most

Every site is different, but a first speed review tends to land on the same short list:

1. Right-size images. Serve modern formats such as WebP or AVIF, provide several sizes so phones download small versions, set width and height so the layout does not jump, and lazy-load images below the fold, but never the main hero image.
2. Cut third-party scripts. Each chat widget, social feed, heatmap, booking embed and tracking tag adds weight. Remove the ones nobody uses, load the rest after the page is interactive, and keep tags under change control.
3. Use a content delivery network and caching. Serving pages and images from an Australian edge location, with long cache times for files that rarely change, makes the first view faster and repeat visits almost instant.
4. Tame fonts. Host fonts yourself, use one or two families, preload the main one and let text show immediately while it loads.
5. Reduce plugins and page-builder bloat. On WordPress and similar platforms, unused plugins and visual builders often load scripts and styles on every page. Fewer, well-maintained plugins are faster and safer.
6. Consider a static or pre-rendered site. Many marketing and information sites do not need a database on every visit. A pre-rendered site served from cloud storage behind a CDN is fast, cheap to run and has a much smaller attack surface (see our static website on S3 and CloudFront architecture).

Local SEO basics for Adelaide and regional SA

Local search results, the map and the short list of businesses near the searcher, rely heavily on information outside your website. The basics are unglamorous but effective:

• Claim and complete your Google Business Profile. Choose accurate primary and secondary categories, set your service area or address, opening hours including public holidays, phone number, website link, services and real photos of your work or premises.
• Keep your name, address and phone consistent. Use exactly the same business name, address and number on your website, Google Business Profile, Apple Maps, Bing Places, industry directories and social profiles.
• Give each service and location a real page. A clear page for each main service, and for each area you genuinely serve, with useful detail, beats one thin page listing every suburb in South Australia.
• Collect genuine reviews and reply to them. Ask happy customers for reviews and respond politely to every review, good or bad. Never write, buy or selectively filter reviews; the ACCC has published guidance on online reviews under the Australian Consumer Law.
• Add structured data. Schema.org markup such as Organization or LocalBusiness, Service, FAQPage and BreadcrumbList helps search engines understand who you are, where you operate and what each page is about. It must match what is visible on the page.

Technical SEO checklist for your website

• A unique, descriptive title and meta description on every page, written for people, not stuffed with keywords.
• One clear main heading per page and a logical heading order underneath it.
• Descriptive internal links, such as “online forms and payments guide”, rather than “click here”.
• An XML sitemap submitted in Google Search Console and Bing Webmaster Tools, and a robots.txt file that does not block important pages.
• One canonical address for each page, with HTTPS everywhere and permanent (301) redirects from old addresses after any move (see our website and CMS migration checklist).
• Alt text on meaningful images and captions or transcripts for video.
• Readable text without zooming, buttons large enough to tap, and no content hidden on mobile that exists on desktop.
• Working contact options on every page: a phone link that dials on a phone, and a form that is short, accessible and protected from spam (see our online forms and payments guide).

Extra points for councils and agencies

Council and agency websites carry more content, more authors and more obligations, so speed and findability tend to erode over time:

• Accessibility comes first. WCAG 2.2 AA is the usual target, and many speed fixes, such as stable layouts and fewer heavy scripts, help it directly.
• Documents are content too. Large PDFs are slow on phones and hard to search and read. Publish important information as web pages and keep PDFs as an optional download.
• Search inside the site matters. Residents often use the site’s own search box; check its top queries and zero-result searches every quarter and fix the content gaps.
• Authors need guardrails. Image size limits, heading rules and a short publishing checklist stop one oversized banner from undoing months of work.
• Trust signals protect residents. HTTPS, sensible security headers and properly configured email authentication on your domain make it harder for scammers to impersonate you (see our SPF, DKIM and DMARC guide).

What to ask your web supplier

1. What are our Core Web Vitals in the field data, not only in a lab test, and how will you report them after go-live?
2. Which third-party scripts run on our site, who added each one, and what does each cost in speed?
3. Where is the site hosted, is there a CDN with an Australian edge location, and how are pages cached?
4. Who owns our Google Search Console, Google Business Profile and domain name accounts, and do we have our own administrator access?
5. How do you keep titles, descriptions, structured data and redirects intact when we redesign or move platforms?
6. How will you test accessibility and performance on a real mid-range phone before launch?
7. What will this cost to run each month, and what happens to the site if we change suppliers?

A 30-day plan

1. Week 1: measure. Set up or confirm access to Google Search Console, run PageSpeed Insights on your home page and your three most important service pages, and note the field data where it exists.
2. Week 2: fix the obvious. Compress and resize images, remove unused plugins and scripts, and set image dimensions to stop layout jumps.
3. Week 3: local listings. Complete your Google Business Profile, check your details match everywhere, and start a simple routine for asking customers for reviews.
4. Week 4: content and structure. Rewrite titles and descriptions for your key pages, add internal links between related services, submit your sitemap, and set a reminder to review results in eight weeks.

This article reflects common practice as at late 2026. Search engine guidance and Core Web Vitals thresholds change, so check Google Search Central and web.dev for current definitions before setting contract targets.

Talk to an Adelaide team

If your website is slow, hard to find or due for a rebuild, talk to us about a website speed and SEO review or call 0402 401 584. We can start with a short, fixed-price review of your key pages, hosting, scripts and search setup that produces a prioritised list of fixes your team or any supplier can act on. Learn more about our website design and development and DevOps and cloud engineering services.