Summary: Test loading, interaction and movement on the pages customers use. Fix the largest practical obstacles first, then recheck the enquiry journey rather than chasing a score alone.
Tradie website speed becomes a business problem when someone cannot read the service, tap the phone number or finish the form without waiting. A performance report is useful, but the customer experiences a sequence of moments rather than a single score.
Start with the pages that receive enquiries or advertising traffic. Improving an unused page while the quote form struggles is a poor trade-off for a small business.
Test a realistic visit
Open the site on a phone using an ordinary connection. Start from the same link a customer would use, rather than a page already loaded in your browser.
Watch for three things: how soon the main information appears, whether controls respond when tapped, and whether content jumps as extra elements load. Google's Core Web Vitals address loading, interaction responsiveness and visual stability through LCP, INP and CLS respectively.
Do not assume a single laboratory result represents everyone. Device, connection, page state and third-party services can change the experience. Compare repeat tests and real-user data when available.
Prioritise the obstruction
| What the visitor notices | Possible contributor | First investigation |
|---|---|---|
| Main banner takes time to appear | Oversized or poorly delivered image | Image dimensions, format and loading |
| Page jumps while reading | Unreserved image or widget space | Layout dimensions and late inserts |
| Button reacts slowly | Heavy scripts or interface work | Interaction behaviour and script load |
| Form waits after submission | Integration or server delay | Submission path and acknowledgement |
| Mobile page feels crowded and slow | Too many competing elements | Remove nonessential components |
These are diagnostic starting points. Ask the person maintaining the site to confirm the cause before removing scripts or changing hosting.
Start with the hero image
A full-width photograph does not need to be delivered at the size of the original camera file. Export an appropriate version, use supported compression and check that responsive sizes work.
Keep the focal subject clear at mobile width. Performance should not come from making the picture so degraded that it stops communicating anything useful.
Reserve the image's display space so text does not shift when it arrives. Be careful with automatic lazy loading: an image visible at the top of the page may need different treatment from one far below it. The implementation should reflect what is actually above the fold.
Review third-party additions as a group
Chat widgets, review sliders, tracking scripts, booking embeds and videos may each seem small in isolation. Together they can make the page do substantial work before a customer has read the first paragraph.
List each addition, its purpose and its owner. Check whether it duplicates another tool. Remove abandoned integrations through the proper settings, preserving anything still needed for forms, measurement or consent choices.
For example, a fictional business may discover two chat tools left active after a redesign. Keeping one maintained system can simplify the page and the handling process. That is an operational finding, not a promise of a particular speed improvement.
Do not break enquiries while improving scores
After a change, test click-to-call, the quote form, confirmation messages and booking links. Check desktop and mobile. A faster page that fails to deliver enquiries is not an improvement.
Keep a short change log with the affected page, action, test result and rollback option. Where the platform permits it, preview changes before applying them to the live page.
Ask for a plain-language explanation of any proposed fix: what causes the delay, what will change and how the enquiry journey will be checked afterwards. Avoid approving a full rebuild merely because one report highlights a problem.
Decide when the job is done
Once the core journey is responsive and stable, return to content and enquiry quality. Performance needs maintenance, especially when new images and widgets are added, but it should not become an endless pursuit of a perfect laboratory score.
Set a repeatable check after major updates. A small routine that catches regressions can be more useful than a one-off speed project nobody revisits.
For help improving the customer journey on your website, see Tradie Local’s functional websites.
Sources & further reading
Frequently asked questions
Does a perfect speed score guarantee rankings?
No. Performance is one part of the page experience. A useful, relevant page and a working customer journey remain essential.
Should I remove every video?
Not automatically. Keep media that genuinely helps, and review how it loads. An unnecessary autoplay banner is different from an optional explanatory video.
Why do speed test results vary?
Testing conditions, device capability, connection and page resources differ. Look for repeated issues rather than treating one test as a complete diagnosis.
Can compressing images fix everything?
No. Images are a useful starting point, but scripts, embeds, server responses and layout behaviour can also contribute.
What should I test after a speed update?
Recheck the main pages, phone links, forms, confirmations and booking steps on mobile and desktop. Preserve enquiry delivery while improving performance.
