Web vitals · For body shops

A phone, in the lot, on 4G.

That is the device you're being judged on. Paid traffic lands on it. Google ranks you on what it does there. Two-week sprint: images, scripts, fonts, caching, deferred third-party, and a before/after report your Google Ads manager will quote back to you.

Live sample

Carrera Auto Body — before and after.

Lighthouse mobile scores for the home page. Day 0 audit vs day 14 handoff. Images were 68% of the problem. Deferring the chat widget and third-party booking script closed the rest.

CPC change−28%

Same ad spend, same ad groups. Lower CPC from Quality Score lift.

Form conversion+41%

Fewer abandons on the first screen when LCP drops below 2 seconds.

Mobile bounce−19%

Phones in parking lots on 4G stay long enough to read the page.

Illustrative sample · fictional shop · representative result

What you'd get

Everything in the sprint.

  • Day-0 Lighthouse audit of your top 3 pages (home, repairs, intake)
  • Image conversion to AVIF/WebP, responsive sizing, lazy loading below the fold
  • Font subsetting, self-hosting where it beats third-party, preload for the hero font
  • Script defer + async pass, chat widget and third-party booking deferred to idle
  • Server-side caching, edge rules, HTTP/2 or HTTP/3 verification
  • Mobile tap-target cleanup and CLS fixes (hero image dimensions, font swap, sticky nav)
  • Day-14 Lighthouse re-report plus a plain-English change log
  • Google PageSpeed and CrUX monitoring configured for 30 days post-handoff
Why body shops need this

Shop sites are slow for reasons shops do not notice.

  • Shop photos are the biggest offender

    Bay shots dragged in from a camera at 6000x4000 pixels and 8MB each are the top-10 Lighthouse finding on every shop site we audit. The fix is five lines of config and a batch conversion. Twenty-point score lift in a day.

  • Chat widgets and booking scripts eat INP

    Every third-party script fires a main-thread burst. Shops that bolt on Podium, Tidio, or a third-party booking widget without deferring it will see INP above 300ms. The sprint defers them to idle and lets them hydrate on interaction.

  • Paid traffic punishes slowness 2x harder than organic

    Google Ads Quality Score weights landing page experience, and that score multiplies into every CPC bid. A LCP drop from 5s to 1.5s typically cuts CPC 20-35 percent at the same spend. The sprint pays itself back inside one billing cycle for most shops running paid.

Related reading: Collision Bureau on the Google Ads buy that depends on page speed, and the landing page build target of LCP under 1.8s.

FAQ

What shops ask before the sprint.

How long is the sprint?

Two weeks from kickoff. Week 1 is audit and the heavy lift (images, scripts, fonts, caching). Week 2 is retesting, cleanup, and a before/after report.

What score target do you commit to?

LCP under 2.5s, INP under 200ms, CLS under 0.1 on mobile 4G against your top three pages. If the target is not hit at the sprint end, work continues at no additional charge until it is.

Will this break my current site?

No. All changes are made on a staging copy, QA'd against the live site, and pushed in a maintenance window. Rollback is one click.

Does this help with Google Ads?

Yes. Quality Score factors landing page experience, which is driven by Core Web Vitals. Shops that take LCP from 5s to 2s typically see 20-35% CPC reduction at the same ad spend.

Do you work with WordPress, Squarespace, or custom sites?

Yes to all three. WordPress gets caching, image optimization, script defer, and plugin audit. Squarespace gets what Squarespace allows (headers, images, deferred third-party). Custom sites get a code review.

What if my site is on a page builder we can't change?

We say so upfront. If the builder caps performance below target, the sprint recommendation is a site rebuild instead and the audit becomes a credit toward it.

Start it

Ship a measurable score in two weeks.

$495/month ongoing monitoring and tuning. Bundled into Pro and Elite subscription tiers.