Rule: a contractor's own website Core Web Vitals (LCP, INP, CLS) is a LOAD-BEARING trust signal — it is the 2nd or 3rd surface in the buyer journey; >50% of WordPress contractor sites currently fail mobile CWV; the HomeStars lead is wasted at the contractor's own front door

A contractor's own website Core Web Vitals (LCP, INP, CLS) is a load-bearing trust signal. It is the 2nd or 3rd surface in the buyer journey (Multi-touch buyer journey for residential construction / major renovation: 4-touch sequence (discovery → validation → verification → contact); the contractor's own website is the 2nd or 3rd surface, not the 1st) — after discovery (referral, directory, ad) and before contact.

The structural reality (Mobile Core Web Vitals reality 2025: only 48% of mobile sites and 43.44% of WordPress mobile origins pass; INP replaced FID March 12 2024; Dec 2025 Google core update increased page-experience weight; 53% of mobile visits abandoned if site takes >3 seconds (Google/DoubleClick 2016); 58% of Google searches now zero-click):

• 48% of mobile sites pass CWV (mid-2025)
• 43.44% of WordPress mobile origins pass (June 2025; ~45–46% by late 2025)
• Most contractor sites are WordPress + heavy page builders + shared hosting — they cluster on the fail side
• 53% of mobile visits are abandoned if the site takes >3 seconds (Google/DoubleClick 2016, canonical)

Why:

A buyer who finds the contractor on HomeStars, then Google-searches their name on mobile, then clicks through to their site — abandons before the LCP renders if the site is slow. The HomeStars lead is wasted at the contractor's own front door. Paying HomeStars $7K/year to drive traffic to a site that can't convert it is the structural failure mode.

How to apply:

• In any contractor client audit, run PageSpeed Insights against the homepage AND a representative deep page (a service page, a case-study page) on mobile. If LCP > 2.5s, INP > 200ms, or CLS > 0.1, CWV is the highest-priority technical work.
• Diagnose the cause — typically: heavy page-builder JavaScript (Elementor, Divi, WPBakery), unoptimized hero images, shared hosting with poor TTFB, render-blocking third-party scripts. WordPress's primary failure mode is LCP and TTFB, NOT INP (Mobile Core Web Vitals reality 2025: only 48% of mobile sites and 43.44% of WordPress mobile origins pass; INP replaced FID March 12 2024; Dec 2025 Google core update increased page-experience weight; 53% of mobile visits abandoned if site takes >3 seconds (Google/DoubleClick 2016); 58% of Google searches now zero-click).
• Treat CWV as a hard prerequisite before pitching content cadence or schema markup work. A fast site with okay content beats a slow site with great content for trust-signal purposes.
• For new builds (Astro, Next.js, similar modern stacks): bake CWV testing into the build pipeline — the B&J marketing site is the worked example (B&J — build performance (v2, Turbopack, verified 2026-05-24)).
• Caveat for any consumer-facing article: run a field sample of 25 Ontario GC websites before publishing the "60–70% likely to fail CWV" figure. Estimated [Directional] until the audit happens.