Field Guide (Web): A one-hour performance build sheet for your marketing homepage

Slow homepages leak leads before your contact form ever loads. Run this numbered build sheet once a week on staging or production: measure Core Web Vitals, fix the top two regressions, and log what changed.

Published Nov 5, 2026 · By Matt Potter · 3 min read

Google’s November Core Web Vitals report is a reminder that speed is a trust signal, not a vanity metric. Owners still tell us the site “feels fine” on office WiFi while mobile visitors bounce on a four-second hero. This Field Guide is a build sheet: one hour, repeatable, no redesign required.

Tie it to this week’s Swift Brief if your board is asking about risk scorecards. Slow pages hurt conversion before any agent or chat widget gets a chance to help.

What happened

Search and ad platforms keep weighting Largest Contentful Paint (LCP) and Interaction to Next Paint (INP) on landing URLs. Marketing stacks added chat, analytics, and font loaders without a weekly owner check. The result: contact forms that work in testing but sit behind heavy heroes on real phones.

Why you should care

Revenue: Every extra second on the homepage costs form starts and quote requests.
Risk: Mixed content, expired TLS, or broken CSP warnings erode trust on first visit.
Time: A one-hour ritual beats emergency fire drills when ads suddenly stop converting.

Build sheet (run in order)

Baseline measure (10 min). Run PageSpeed Insights or Lighthouse on your homepage URL in mobile mode. Save LCP, INP, and CLS. Note the LCP element (usually hero image or H1 block).
Hero and fonts (15 min). Serve the hero in WebP or AVIF with explicit width/height. Preload only the LCP image, not every carousel slide. Self-host critical fonts or swap to a single variable face; drop duplicate weights.
Third-party audit (10 min). List every script on the homepage (tag manager, chat, heatmaps). Defer non-critical tags until after load or first interaction. If chat is below the fold, lazy-load its bundle.
Form path (10 min). Load /contact on throttled 4G. Confirm the form appears before ancillary widgets. Submit a test row; verify webhook or mail log entry within one minute (see your server log, not just inbox).
Security headers (5 min). Check HTTPS redirect, HSTS, and that no active page loads http:// assets. Fix one mixed‑content URL if flagged.
Ship two fixes (10 min). Pick the two highest‑impact items from steps 2–4. Commit, deploy, re‑run Lighthouse. Log scores in a shared doc with date and deploy hash.

Decision cues (when to stop tweaking)

If mobile LCP is under 2.5s and INP under 200ms on your homepage, shift effort to agent safety or content, not micro‑optimizing bytes. If LCP stays above 4s after two weekly cycles, consider a hero redesign or moving chat to a secondary page rather than endless script whack-a-mole.

What we would build at Swift Media

On PHP marketing sites we pair this build sheet with monitored contact pipelines, cached partials for listing pages, and optional Website Agent guardrails so chat and forms do not ship without a performance check. Hosting on our stack includes TLS renewal alerts so step 5 is rarely a surprise.

This week

Block 60 minutes on the calendar, run the sheet on production, and post before/after scores to whoever owns ads or SEO. Next Thursday we rotate Field Guide pillar to software; use the saved minutes to fix one integration debt item instead.

Want a second set of eyes on your homepage metrics or form pipeline? Talk with us.

Matt Potter · Swift Media