Every extra second on mobile increases bounce probability. For emergency trades — plumbing, HVAC, towing — speed is not branding; it is whether someone calls you or scrolls to the next result.
What this guide covers
Google publicly ties experience metrics to rankings. Customers tie slow pages to “this business is probably a mess too.” Technical SEO — schema, canonical tags, crawl hygiene — is how you make sure machines describe you accurately. This guide connects those dots without turning you into a full-time engineer.
You'll learn:
- What Core Web Vitals measure and why mobile LTE is the real test.
- How images, fonts, and third-party scripts steal load time — and what to do about each.
- Structured data basics: LocalBusiness, FAQ, and breadcrumbs without spamming.
- Security hygiene: HTTPS, backups, and why “nobody would hack us” is false comfort.
- Accessibility overlaps that help everyone: contrast, tap targets, and form labels.
- How to read a Lighthouse report without drowning in acronyms.
The core explainer
Performance is conversion
Core Web Vitals in one paragraph
Largest Contentful Paint (LCP) measures how fast the main content shows up. Interaction to Next Paint (INP) captures responsiveness. Cumulative Layout Shift (CLS) tracks visual stability. Nail those and you have satisfied both Google and impatient humans.
Technical SEO is truth maintenance
Search engines and AI systems ingest what you publish. If your schema says you are open Sundays but your footer says otherwise, you are training machines to distrust you. Technical SEO is keeping facts aligned across HTML, JSON-LD, GBP, and reality.
Security as reputation insurance
Small sites get compromised to host phishing pages and crypto miners. Defacement still happens. Backups plus patching plus least-privilege admin accounts are the boring hero work nobody applauds until disaster strikes.
Performance tier targets (practical)
Targets, not guarantees — network and content vary. Aim here before chasing 100/100 vanity scores.
| Metric | Good enough (mobile) | Strong |
|---|---|---|
| LCP | ≤ 2.5s | ≤ 2.0s |
| INP | ≤ 200ms | ≤ 150ms |
| CLS | ≤ 0.10 | ≤ 0.05 |
| HTTPS | Required | Required |
Common mistakes and red flags
Testing only on Wi‑Fi
Half your traffic is on variable mobile networks. Throttle Chrome DevTools and test cold loads.
Uploading 4MB hero images “because Retina”
Serve responsive images with modern formats and dimensions matched to layout. Bigger files are not sharper — just slower.
Installing analytics and chat widgets blindly
Third-party scripts are the silent LCP killer. Load non-critical tools after interaction or defer entirely.
Fake LocalBusiness schema
Do not invent addresses or review counts. Rich result spam can earn manual penalties and erodes trust with AI parsers.
Skipping alt text on project photos
Alt text is accessibility and image search relevance. One sentence per important image is enough.