speed up your site: measure, images, delivery, weight

web · 2026-10-13 · 6 min

speed is a funnel: measure, fix images, fix delivery, then code — in that order, because earlier steps capture most gains for least skill. google's good thresholds (75th percentile): LCP ≤2.5s, INP ≤200ms, CLS ≤0.1. here's the sequence that gets small sites there.

step 0: measure the right thing

pagespeed insights field data (real chrome users, where available) over lab scores — lab lies about phones and networks. test money pages (homepage, top service, contact/checkout), mobile first. record before/after every change or nothing happened. google's owner guide frames causes for non-developers; start there, not in forums.

step 1: images (the giant's share)

resize to display size (4000px uploads for 800px slots are the classic sin). modern formats (WebP/AVIF compress better — web.dev's explicit guidance). compress (~80% quality, invisible difference). lazy-load below fold, prioritize hero (LCP is usually an image — 73% of mobile pages per web almanac). one image pass: the highest ROI afternoon in web performance.

step 2: delivery (caching + CDN + host)

caching (serve finished pages instead of rebuilding per visit — plugin or host-level). CDN (cached content from nearby servers — free tiers cover small sites). hosting floor (slow time-to-first-byte indicts the server: how much does hosting cost). each halves perceived waits for different visitors; stacked, they transform.

step 3: weight (scripts and code)

fewer plugins/widgets/fonts (each loads everywhere). defer non-critical JS (break up long tasks — responsiveness lives here). builder bloat acknowledged (some weight can't be removed — platform ceilings are real). developer territory begins here; steps 0-2 are owner territory. wordpress specifics: why is my wordpress site so slow. diagnosis generally: why is my website slow.

FAQ

perfect pagespeed score — required?

no: field data and business metrics outrank lab perfection. chase green on money pages, not 100 everywhere.

one plugin to fix it all?

caching plugins help hugely but hide unfixed causes — images and hosting first, cache second. magic-plugin marketing is the performance equivalent of diet pills.