What PageSpeed score does an insurance agency website actually need?

A mobile performance score of 90 or above is the working pass line — because Google's ranking systems do not use the score at all, they assess the three Core Web Vitals underneath it (LCP within 2.5 seconds, INP within 200 milliseconds, CLS within 0.1, each at the 75th percentile of real page loads, per web.dev's published thresholds), and a site that scores in the 90s on mobile typically clears all three with room to spare.

The qualifier: the number that matters is the mobile score, from field data where your site has enough traffic to show it. A desktop 95 proves little — PageSpeed Insights tests mobile on a simulated mid-range phone over a throttled connection precisely because that is the hard case, and it is the case most insurance shoppers are in when they search from a phone at night. And the Lighthouse score is lab data; it can legitimately differ from what real visitors experience.

The thresholds behind the score

So why do we build to 99-100 instead of stopping at 90? Headroom. A score is not static: every tag, chat widget, and tracking pixel an agency adds after launch spends performance budget. Our own production client builds measure 99-100 on mobile PageSpeed from clean builds — justinbrock.com at 100, brockpartners.com at 100, bobbybrockinsurance.com at 99, and a 15-page agency rebuild at 99 mobile on 14 of 15 pages with a CLS of 0 (SAA build measurements, July-August 2026). A site that starts there can absorb a year of real-world additions and still pass; how those builds get to 99+ is its own question. A site that launches at 90 is one plugin away from failing, and what failing actually costs in rankings is smaller than what it costs in abandoned quote forms.