What Site Care Looks Like When It Is Measured: Ten Sites to 90+ in One Afternoon

We pulled Google’s PageSpeed Insights API for every client homepage, mobile and desktop, and read what each report pointed at rather than guessing. Five patterns covered almost everything: hero text animated in from invisible so the biggest element waited for the JavaScript; Google Fonts loaded from a third party in front of the first paint; analytics and session-recording scripts fighting the hero image for the first seconds of a phone connection; a 230 KB logo where a 21 KB one would do; and one e-commerce homepage running five database queries on every visit.

Each fix was small and specific. Hero entrances became CSS animations that paint on the first frame. Fonts were self-hosted. Analytics moved to load after the page is idle. Images were resized to what is actually displayed. The e-commerce homepage caches its data for ten minutes and renders its hero on the server. Every change was deployed and re-measured the same afternoon.

Two sites were left alone on purpose: one whose live domain still points at an old site awaiting the client’s go-live, and one where the remaining fix needs the client’s approval because it touches how their analytics loads. Site care is knowing where the line is as much as moving the number.