The State of Melbourne Tradie Websites 2026

The median Melbourne tradie homepage takes 6.6 seconds to render its main content on a mobile phone. Google's threshold for a "good" user experience is 2.5 seconds. Of the 47 trades websites we audited, 93.6% fail that bar.

That number will not surprise every tradie. What will surprise most: responsiveness is not the issue. When you look at the data, nearly every site in the sample correctly declares a mobile-responsive viewport. They scale on a phone. They are just slow, sometimes catastrophically so, and slow is invisible until someone checks.

This report is the data.

What we found, and why it matters for getting the job

Speed: the systemic failure

Median mobile LCP: 6.6 seconds. LCP (Largest Contentful Paint) is Google's primary measure of how quickly the main content of a page appears. It is what a homeowner experiences as "has this loaded yet." At 6.6 seconds, the median Melbourne trades site sits at more than 2.5 times the threshold Google considers acceptable.

The distribution is not a few outliers dragging a healthy middle upward. The slow sites are the middle:

The median performance score is 58 out of 100. A score of 58 is in the lower half of the "needs improvement" band, one notch above where Lighthouse starts colouring results red.

The commercial consequence is simple. A homeowner searching "plumber Hawthorn" at 9 pm on their phone has a leak and limited patience. Every second of load time is a second in which they are deciding whether to wait or try the next result. The three slowest sites in this sample (lab LCPs of 75.2 seconds, 33.6 seconds, and 24.8 seconds) are not competitive online, regardless of how good the work on the tools is.

Page weight: builders are the worst offenders

The median Melbourne trades homepage transfers 2.8 MB over the wire. That median is the reliable figure; the mean is 6.57 MB, heavily distorted by one extreme outlier: a Melbourne builder whose homepage loaded 96 MB of data (verified, not a measurement error). Even without that outlier, the distribution is heavy:

Builders dominate the heavy end because project galleries are where the weight lives. A builder's site legitimately needs strong photography; the failure is serving those images uncompressed, full-resolution, on every page load. A 96 MB homepage is not an aesthetic choice. It is a technical oversight with a direct cost in lost enquiries.

The interactivity picture reinforces this. 55.3% of sites have a Total Blocking Time above 200 ms (the point at which heavy JavaScript is measurably blocking the main thread). These pages feel unresponsive even after they visually appear.

1 in 3 tradies are phone-only

The second major finding has nothing to do with speed. Of the 43 sites where the HTML could be assessed, 14 of 43 (32.6%) have no submittable online quote or booking form on the homepage. Of those, 9 of 43 (20.9%) show no online enquiry path whatsoever: no form, no recognised booking platform, nothing a visitor can act on digitally.

That means roughly one in three Melbourne trades businesses in this sample cannot be contacted online at the moment of intent. A potential customer looking at their ceiling at 10 pm on a Sunday, realising they need a new hot water system, visits the site and finds a phone number. They might call tomorrow. They will probably not. The competitor whose site took a quote request at 10 pm closed the job before Monday arrived.

For context: the sites with genuine online quote or booking capability (29 of 43, 67.4%) are not necessarily sophisticated. Several use a basic contact form with name, phone, and message fields. That is enough for a visitor to register intent without picking up the phone. The bar is not high. The gap between those sites and the phone-only sites is a form, not a platform.

See the companion article on tradie website design Melbourne: what actually converts for a breakdown of which form patterns perform best and how to structure a quote request flow that converts at a meaningful rate.

Electricians have a structured data blind spot

Google uses structured data (markup embedded in the page HTML) to understand what a business is and surface it correctly in local search results. For a trades business, the useful schema types are specific: Plumber, Electrician, GeneralContractor, HomeAndConstructionBusiness. A plumber with Plumber schema is giving Google a more precise signal than a plumber with generic LocalBusiness schema.

Of the 43 HTML-assessable sites, only 13 of 43 (30.2%) use proper trade-specific schema. The remaining 70% rely on LocalBusiness, other non-specific JSON-LD, or nothing at all.

The most striking finding in this category: every site with no structured data at all was an electrician. Five sites have zero JSON-LD, and all five are electrical contractors: Abba Electrical, Adtec Electrical, City Electrical, Electrex Melbourne, and Structured Electrical. This is not a meaningful indictment of the electrical trade specifically; the sample is small and the pattern may be coincidence. But it is a concrete, verifiable gap and a local search disadvantage that a fifteen-minute code change would close.

For trades businesses trying to hold or improve local search visibility, trades web design Melbourne covers schema implementation alongside the other technical requirements that affect map pack rankings.

What is working: HTTPS and responsiveness

The data supports two things Melbourne trades websites do well.

HTTPS is near-universal. 42 of 47 sites (89.4%) pass cleanly. Five sites (10.6%) carry mixed content (some insecure subresources loaded within an otherwise HTTPS page), but every site in the sample is served over HTTPS at the document level. Zero trades businesses in this sample are running plain HTTP.

Responsiveness, measured from the HTML viewport meta tag across 43 HTML-assessable sites (the PSI scored viewport audit returned null this run and was not used), is similarly strong: 42 of 43 (97.7%) declare a responsive mobile viewport. Only one site, Abba Electrical, does not. The failures in this sample are speed and business-function gaps, not responsiveness.

Methodology

This research covers a sample of 47 Melbourne trades websites (16 plumbers, 16 builders, 13 electricians, 2 roofers), audited on 18 June 2026. It is not a census of all Melbourne trades businesses.

How the sample was built. Two sources were combined and deduplicated by registrable domain. The primary source was the Pryce Digital leads database, a PostgreSQL database of business records filtered for Victorian addresses and industries in the trade set (Plumber, Electrician, Builder, Roofer). This returned 116 core-trade rows with websites, from which obvious non-fits were removed: aggregator directories, mislabelled entries, and rows with truncated or placeholder URLs. To widen suburb coverage (the database skews toward generic "Melbourne VIC / CBD" addresses) the sample was supplemented by targeted suburb searches: plumber Hawthorn, electrician Brighton, electrician Preston/Coburg/Northcote, custom home builder Richmond/Bayside. Combined raw candidate pool: 50 domains.

Exclusions. Three of the 50 candidates were removed because they could not be audited as a real, live, independent Melbourne trades homepage. One returned an HTTP 503 maintenance stub on repeat probes. One was unreachable (HTTP 000, dead domain). One served a GDPR/consent-management parking stub with no business content. These three are excluded from all statistics and are never counted as "poor" sites. One site that 301-redirected was kept after verification that the destination domain was the same Melbourne business under a rebrand.

Audit method. Each of the 47 remaining sites was audited by two independent data pulls. The first was a run of the Google PageSpeed Insights API v5 (strategy=mobile), which executes a real Lighthouse audit server-side at Google and produces the performance score, LCP, CLS, TBT, page weight, and SEO/best-practices category scores reported here. The second was a direct HTML fetch of the homepage, used to detect: online quote and booking capability (by parsing for recognised platform signatures and native submittable forms), structured data (by reading every application/ld+json block), licence and credential display (REC numbers, VBA builder registration, trade-body membership), and the mobile viewport meta tag.

Why denominators differ. PSI metrics (performance, LCP, HTTPS, meta description, SEO/best-practices) use N = 47. Schema, online quote, licence display, and viewport use N = 43. Four sites sat behind a bot-challenge CDN that returned an HTTP 202 with no body: Zebra Plumbing, Energized Electrical, Melbourne Roofing and Gutters, Roofing Guys Melbourne. Their HTML could not be parsed. They are reported as "not assessable" and are never assumed to be negative cases.

CrUX field data. Google publishes real-user Core Web Vitals only for sites with sufficient traffic volume. Only 8 of 47 sites had field CWV data available. Of those 8, 5 were not passing Google's overall Core Web Vitals verdict. This is consistent with the lab data directionally, but covers too small a subset to be the headline figure. The Lighthouse lab results across all 47 are the reliable cross-sample signal.

Limitations. The sample skews toward inner-city, CBD/Docklands, eastern, and bayside Melbourne. Outer suburban and outer-ring suburbs are underrepresented. Speed figures are single-run Lighthouse lab values and vary a few points run-to-run; treat band and median figures as the reliable signal, not individual site ranks. The responsiveness figure comes from the HTML viewport meta tag (N = 43), not Lighthouse, because the PSI scored viewport audit returned null this run, a slightly weaker signal stated honestly. Quote, schema, and licence detection is signature-based and homepage-only: a booking form or licence number on an interior page, or content injected client-side after the initial load, would be missed, meaning any undercount of these features understates the good news, not the bad. Roofers (n = 2) are too few to characterise on their own. Audit date 18 June 2026.

What a trades business should do about it

The findings point to three actions in descending order of likely commercial impact.

First, page weight. The direct cause of slow LCP is data transferred to the browser. The fix is compression, format, and deferral: serve images in WebP at appropriate dimensions for the viewport, load video only on interaction rather than on page entry, and defer third-party scripts until after the core content has rendered. A builder currently sending 10–18 MB on the homepage can realistically get to under 2 MB without altering the design at all. For builders whose galleries are the legitimate business case for heavy photography, the engineering answer is progressive loading and lazy rendering: serve thumbnail-quality images on entry and load full resolution only when the user scrolls to them or taps. Sites built on page-builder templates have limited headroom here; a hand-coded site has none of those constraints.

Second, an online quote form. If a homeowner cannot submit a quote request on your homepage at 9 pm, you are not competing for the jobs decided after business hours. For domestic work like emergency plumbing and electrical faults, that is when decisions get made. The capability does not require a third-party platform. A native form with name, phone, service type, and a free-text field for the job description is sufficient. What matters is that visitors can submit something without calling. Once submitted, the follow-up is yours to manage; you have the lead. Without it, you do not.

Third, trade-specific schema. Switching from generic LocalBusiness schema to the correct trade type (Plumber, Electrician, GeneralContractor) is a short development task. It gives Google a precise signal about what the business is, which is relevant for suburb-level local search results and the Google Maps pack. For the five sites in this sample with no structured data at all, adding any schema is the immediate priority. For the 70% using only generic schema, switching to the correct trade type is the correct next step.

None of these require a full rebuild. Page weight and schema are optimisation work. An online form is a feature addition. A trades business that wants to address all three properly as part of a broader project will get more from rebuilding than patching, but patching is better than leaving a site that takes more than 2.5 seconds to render its main content, like the 93.6% of this sample that miss Google's bar.

To see where your site sits against these benchmarks, the Pryce Digital free audit tool runs a live PageSpeed check on any URL in about 30 seconds. You get the performance score, LCP, and page weight without filling in a form.

FAQ

How was the sample of 47 Melbourne trades websites selected?

Two sources were combined and deduplicated by registrable domain. A filtered query of the Pryce Digital leads database returned Melbourne trades businesses (plumbers, builders, electricians, roofers) with website fields. Non-fits (directory aggregators, mislabelled rows, placeholder URLs) were removed. Targeted suburb searches supplemented the database sample to widen geographic coverage. From 50 raw candidates, 3 were excluded because they either had dead or unreachable DNS records or served parking stubs rather than real business homepages. The resulting sample of 47 is not random or exhaustive. It skews toward inner-city and bayside Melbourne; outer suburban and outer-ring areas are underrepresented.

What is LCP and why does the 2.5 second threshold matter?

Largest Contentful Paint (LCP) measures the time from when a user first navigates to a page until the largest visible element (typically a hero image or main headline) finishes rendering. Google uses it as the primary user-perceived load speed metric in its Core Web Vitals framework and sets 2.5 seconds as the "good" threshold. Sites above 4.0 seconds are classified as "poor." 80.9% of the trades sites in this sample sit in the poor band on mobile. The median of 6.6 seconds means the typical site in this sample is taking more than 2.5 times the "good" threshold just to render its main content.

Why do schema, quote form, and licence statistics use 43 sites rather than 47?

Four of the 47 audited sites sit behind a bot-challenge CDN that returns an HTTP 202 response with no page body when fetched by a non-browser client: Zebra Plumbing, Energized Electrical, Melbourne Roofing and Gutters, and Roofing Guys Melbourne. Because their HTML could not be parsed, it was not possible to determine whether they had quote forms, structured data, or licence displays. Counting them as negatives would have been inaccurate. They are excluded from those denominators as "not assessable" and are separate from the sites that were assessed and found to lack the feature in question.

Does a slow website actually affect how many enquiries a trades business gets?

Yes, through two mechanisms. The first is direct abandonment: a visitor who does not wait for a page to load cannot become a lead. The steepest abandonment increases occur between two and five seconds of load time, exactly where the bulk of this sample sits. The second mechanism is search ranking: Google uses Core Web Vitals as a ranking signal for page experience, meaning slow sites rank lower in the local results where customers find trades businesses. Both effects are compounding and largely invisible to a business owner who is not checking their analytics.

What does "no trade-specific schema" actually cost in local search terms?

Schema does not directly determine whether a site appears in search results. What it does is give Google a more precise signal about the type of business on the page. A plumber with Plumber schema is giving Google an unambiguous data point; a plumber with LocalBusiness schema is asking Google to infer the trade from the page content. In competitive suburb-level local searches, where multiple businesses are competing for map pack positions, the more precise schema is a modest but real advantage. For the five sites in this sample with no JSON-LD at all, there is no structured signal of any kind. That is the larger gap.

Is this research specific to Melbourne, or does it apply to trades websites generally?

The sample is Melbourne-specific and the numbers reflect these 47 businesses. The underlying patterns (image-heavy sites served without compression, phone numbers where quote forms belong, generic schema where trade-specific types fit) are not unique to Melbourne. We chose Melbourne because it is the market we work in and the database coverage is strongest there. Trades businesses in Sydney, Brisbane, and other capitals would likely show similar distributions if audited by the same method.