How fast should my agency website load on a phone?

The main content of your page should be on screen within 2.5 seconds on a phone, for at least three out of four real visits. That's Google's published "good" line for Largest Contentful Paint, and it's the number worth chasing. Add two more targets and you're done: the page answers a tap within 200 milliseconds, and nothing jumps around while it loads. Hit those for real visitors and your site is fast enough. A perfect 100 in PageSpeed Insights isn't the goal, and chasing one is usually a waste of an agent's afternoon.

What does "fast enough" actually mean?

Google measures page experience with three Core Web Vitals. Each has a "good" threshold, and each is judged at the 75th percentile of real page loads, split by mobile and desktop. In plain English: three out of four visitors have to get the good experience, not just you on office Wi-Fi.

Thresholds are from Google's LCP and INP documentation on web.dev. INP replaced the older First Input Delay metric in March 2024, so a vendor report that still talks about FID is out of date.

Why these and not "total load time"? Because a visitor doesn't wait for the last tracking pixel to finish. They decide whether to stay when they can see your headline and your phone number. LCP measures that moment. A page can take eight seconds to fully finish loading and still feel fast, or take three and feel broken because the hero image arrived last.

What PageSpeed score should an insurance website have?

According to Google's PageSpeed Insights documentation, a performance score of 90 or above is good, 50 to 89 needs improvement, and below 50 is poor. On mobile, that score comes from a simulated load on a single mid-tier phone over a throttled mobile connection. It changes from run to run, and mobile scores almost always come in lower than desktop because the test is built to be harder.

Here's the part most agents miss: the score isn't the verdict. At the top of the PageSpeed report there's a separate section that says whether your page passes the Core Web Vitals assessment. When Google has enough traffic data, that section uses the previous 28 days of real Chrome visitors. When a single page doesn't have enough visits, it falls back to data for the whole site. A small agency site often has no field data at all, and then the lab score is the only signal you get.

Does speed affect where you rank?

Less than vendors selling speed fixes tend to suggest. Google's page experience guidance says Core Web Vitals line up with what its core ranking systems seek to reward. In the same document it says Google "always seeks to show the most relevant content, even if the page experience is sub-par," that good Core Web Vitals results don't guarantee top rankings, and that "trying to get a perfect score just for SEO reasons may not be the best use of your time."

For a local agent, that adds up to two jobs speed actually does:

• Tie-breaker. When several agencies have similar pages for the same county, page experience is one of the things that can separate them.
• Conversion. This is the bigger one. Medicare and final expense prospects are disproportionately on phones, often on cellular data, sometimes on older devices. A page that shows a blank white screen for five seconds loses the visitor whatever position it ranked in.

Think of it this way: ranking gets you the visit, and speed decides whether the visitor ever sees your phone number. That's also why speed sits alongside tap-to-call in our breakdown of what belongs above the fold.

Does speed matter for ChatGPT and AI search?

Not in the way it matters for Google, as far as anyone can document. No AI company publishes load time as a citation factor, and we won't pretend otherwise. But there is a related problem that's well documented. In a December 2024 study of crawler traffic, Vercel found that "none of the major AI crawlers currently render JavaScript," naming OpenAI's GPTBot, OAI-SearchBot and ChatGPT-User, Anthropic's ClaudeBot and PerplexityBot among them.

So the heavy, script-built page that's slow on a phone is often the same page whose text an AI crawler never sees, because the words only appear after JavaScript runs. A page that ships its content as plain HTML tends to be both faster and readable to every crawler. That's one of the structural reasons we cover in our AEO guide for insurance agents.

How do you test your own site in five minutes?

1. Run PageSpeed Insights on your homepage and your most-visited county or Medicare page, on the Mobile tab. Run each one twice and note whether the Core Web Vitals assessment passes, fails or says there's no data.
2. Turn Wi-Fi off on your own phone and load your site on cellular, from a search result, the way a prospect would. Count how long until you can see your headline and tap your phone number.
3. Tap the call button and the menu as soon as they appear. If nothing happens for a beat, or the button jumps as you tap, that's INP or CLS in the real world.
4. Check Search Console. If you have it set up, the Core Web Vitals report groups your pages by "good," "needs improvement" and "poor" using real visits.

What usually slows an agency site down?

In the sites we audit, it's rarely the hosting and almost never anything exotic. It's usually one of these:

• A huge hero photo. A 4 MB stock image of a smiling couple, shown at phone width. Resize it and serve a modern format such as WebP. This one fix often moves LCP more than everything else combined.
• Autoplay background video. Beautiful on a desktop, expensive on cellular data. Use a still image on mobile and let people tap to play.
• Sliders and carousels. Five rotating banners mean five images and a script, for a message almost no one reads past slide one.
• Widget pile-up. Chat bubble, review badge, quote widget, two analytics tags, a heatmap tool and a pop-up. Each one is small; together they make every tap feel sluggish. Keep the ones that earn leads.
• Page-builder bloat. Some drag-and-drop builders load code for every feature on every page. You can trim it, but there's a limit to how fast those pages can get.

The honest counterpoint: if your site already passes Core Web Vitals on mobile, stop here. Your time is better spent on content, reviews and the trust items in our insurance agent website checklist than on squeezing another 300 milliseconds out of a page that's already fast.

Frequently asked questions

Where we fit

We build agency sites as lightweight pages with the content in the HTML, compressed images, a still hero on mobile and only the scripts that bring in leads. Speed is part of the build, not an add-on. Our demo sites are public, so you can run them through PageSpeed Insights yourself before you talk to us. What's included with each plan is on the what you get page.