60-Day Free Trial · Nothing Up Front · Month-to-Month · Cancel Anytime — No Reason Required How it works →
← All Insights
Websites & Conversion  ·  9 min read

What your PageSpeed report is actually telling you.

Google grades every page you publish, free, in under a minute. It helps you quickly determine if your content is optimized for the buyer deciding whether to stay, the search engine deciding whether to show you, and the AI now reading your page on the buyer's behalf. Here's what each number means, and which ones actually cost you business.

Actual result · our live demo

Google PageSpeed Insights

eaglehealthcaresecurity.com

Desktop

100
Perf.
96
Access.
100
Best Pr.
2/2
Agentic

Mobile

93
Perf.
96
Access.
100
Best Pr.
2/2
Agentic
LCP 0.5s CLS 0.002 TBT 0ms (desktop)
One of our own vertical-market websites, run through the free tool at pagespeed.web.dev — 100 on desktop, 93 on mobile, no drop-off between them. Target a score of 90+ across the board and a Largest Contentful Paint (LCP) of <=2.5 seconds.

The short version

  • Google's free PageSpeed Insights tool grades any page in under a minute, on both mobile and desktop.
  • It measures everything that happens before anyone reads your words — for the human, and for the AI that reads your page on the buyer's behalf.
  • Five scores matter: Performance, Accessibility, Best Practices, SEO, and Agentic Browsing — plus LCP, the one number that best answers "did it feel fast?"
  • Check mobile first — it's where the trouble hides. And remember: speed is table stakes. It keeps the door open; your content still wins the job.

A buyer — the person who decides which integrator gets the call — opens your page on a phone between meetings. If it takes too long to appear, or the text jumps around while it loads, that buyer is gone before your first sentence lands. They won't email you to say the page was slow. They'll just click back and open the next firm.

That buyer isn't your only reader anymore. Every page you publish now answers to three audiences at once: the human deciding whether to trust you, the traditional search engine deciding whether to show you — that's Search Engine Optimization, or SEO — and, increasingly, the AI assistant that reads your page on the buyer's behalf and summarizes what you offer before the human ever clicks. Getting recommended by those AI tools is its own discipline now, called Generative Engine Optimization, or GEO. You're writing for all three at the same time.

That is where PageSpeed Insights comes in. It measures everything that happens — or fails to happen — before anyone reads a word you wrote. For the human, that's the few seconds of loading that decide whether they stay. For the machines, it's something more basic: whether your words can be read at all. A page an AI agent can't cleanly read is a page it can't quote or recommend, no matter how good the writing is. Your content can be excellent, but a page that loads badly — or that a machine can't parse — never gets the chance to prove it.

Google gives the tool away free at pagespeed.web.dev. Paste in a URL and, in under a minute, you get two report cards: one for mobile, one for desktop. Read mobile first — that's the one most integrators never check, and it's where the trouble hides. Each report gives you five scores and a short list of measurements underneath. Here's what each one means, and which ones actually matter.

Score 1

Performance — the score a buyer feels

This is the speed score, 0 to 100, and it's the one a buyer feels most directly. Google colors it green at 90 and up, orange from 50 to 89, and red under 50. Don't misread those bands: they're Google's engineering buckets, not the line where buyers start leaving. The leaving starts in the first few seconds, long before a score falls into the red. Google's own research found that going from a one-second to a three-second load makes a visitor 32% more likely to bounce, and that 53% of mobile visitors abandon a page that takes more than three seconds to appear. A separate 2022 study of more than 27,000 lead-generation pages found that a page loading in one second converts about three times better than the same page loading in five — with the drop-off starting immediately, second by second, not at some cliff. None of that waits for red. A page sitting comfortably in orange is already losing people. Treat green as the goal, not a ceiling, and treat orange as a problem you haven't fixed yet — not a passing grade. Underneath the score sit three real-world measurements Google calls the Core Web Vitals:

Google's nameIn plain terms"Good" means
Largest Contentful Paint (LCP)How fast the main content shows upunder 2.5 seconds
Interaction to Next Paint (INP)How quickly the page reacts when you tapunder 200 ms
Cumulative Layout Shift (CLS)How much the page jumps while loadingunder 0.1

Loading, responding, holding still. A page that shows up fast, answers a tap without lag, and doesn't shove the text down as an image drops in — that page feels solid. One that fails any of the three feels broken, even if the visitor couldn't tell you why. Of the three, LCP is the one to watch: it's the single number that best answers "did this feel fast?" If you only fix one thing, fix that.

Score 2

Accessibility — the score that's also a tell

Whether the page works for everyone — someone using a screen reader, navigating by keyboard, or reading with low vision who needs real color contrast. Two reasons to care. First, it's a legal exposure; accessibility complaints are a real and growing category. Second, it's a tell: a site built with accessibility in mind is a site built by someone who did the job properly. A buyer reading your page can't see the score, but the same care that earns it is the care they sense you will bring to their security project. And of course, the opposite is also true. A slow, laggy site doesn't send the right signal from the start.

Score 3

Best Practices — "is this site kept up?"

The technical housekeeping underneath — a secure connection, no broken or out-of-date code, images sized correctly instead of shrunk down from something huge. Think of it as the "is this site kept up?" score. A low number here rarely loses a deal by itself, but it's the quiet evidence of a site nobody has maintained in years. Again, it's a subliminal signal that can either help or hurt you just when it matters most.

Score 4

SEO — found before they know your name

How easily a traditional search engine can find, read, and rank the page. This is the search a buyer runs before they've ever heard your name — the kind of query that starts with a problem stated in the form of a question. A weak score here means you're invisible at the exact moment someone is looking for a firm like yours, and whoever shows up instead gets the call.

One thing to check first if your SEO score comes back low: the most common cause, by far, is that the page is blocked from search engines entirely. It's a single line of code — a "noindex" tag — usually left on by accident from when the site was being built and never turned off. PageSpeed flags it as "Page is blocked from indexing." If you see that, nothing else about your SEO matters, because Google isn't allowed to list the page at all. It's also the easiest fix on this entire list: one setting, and you go from invisible to found. (Fair disclosure — you may notice our own demo page scores lower here for exactly this reason. That one's on purpose: a showcase site shouldn't compete in Google against the integrators we're trying to help, so we keep it hidden from search. On a real, live page you'd do the opposite.)

Want to see exactly what Google has actually indexed from your site? There's a quick, free check that needs no tools or logins: go to Google and search site:yourwebsite.com (using your own domain, no space after the colon). Google returns every page from your site it currently has in its index. Skim the list — if pages you care about are missing, they aren't being found; if pages you thought were hidden show up, they're exposed. You can narrow it too: site:yourwebsite.com/services checks a single section. It's the fastest way to confirm that the page a buyer needs to find is actually findable.

Score 5

Agentic Browsing — can an AI read your page?

This one is new — Google added it in May 2026, and most sites have never been checked against it. It measures something different from the others: how well an AI agent can read and use your page.

Here's why it exists. More and more, a buyer doesn't visit your page first — an AI assistant does it for them. It fetches your page, reads it, and tells the buyer what you offer before the human ever clicks. This score checks whether your page is built so that machine can actually parse it: is the underlying structure clean, are your forms labeled in a way an agent understands, do you provide the plain-text summary files the new tools look for, and does the layout hold still instead of shifting around while the agent tries to read it.

It's the technical half of what we call GEO — getting recommended by the AI tools, not just the search engines. (We wrote about the content half separately; see our GEO vs SEO piece.) The good news: you don't need any fancy AI features to pass. A cleanly built page clears it. A messy one doesn't — and it fails silently, because the buyer never sees the assistant skip you.

Check this first

The mobile cliff. Desktop scores often look respectable while mobile scores fall off a cliff. When we measured a sample of ten integrator sites, the middle desktop score was around 88 — not optimal, but relatively solid. The middle mobile score was around 57 — orange, sliding toward red. Four of the ten were in the red on mobile.

There's a reason it's this common. A lot of these sites run on themes designed and previewed on a big desktop monitor, over fast office internet, where everything loads instantly and looks great. The phone is an afterthought. So the heavy images, stacked plugins, and wall of text that a desktop shrugs off all land at once on a phone over a cellular connection — which is exactly where most of your buyers actually are. If you check one thing after reading this, check your main page on mobile.

Two kinds of data

One honest read of field vs. lab

PageSpeed can show two results that don't always agree. Field data is what real visitors lived through over the last 28 days — it only appears once a page has had enough traffic to measure. Lab data is a single controlled test on a simulated mid-range phone, identical every time, which makes it the fair way to compare one page against another, and the only data you have on a page that's new or low-traffic. When you run your own page, look at both if they're there. Field tells you what your visitors are living. Lab tells you what's fixable.

What it buys you

Speed is table stakes. Content wins the job.

Be clear-eyed about what this buys you. A perfect score does not make you the expert, and it does not win the job. A fast, clean, accessible page with nothing to say is still a page with nothing to say. Speed is table stakes. It's the price of being in the room — it keeps the door open long enough for your content to do the real work. A 100 across the board is worth nothing if the page underneath doesn't teach the buyer something. But a 40 on mobile quietly costs you buyers who never reach the part where you're good.

Never brag about being the fastest. Just don't be the one that loses people at the door.

One practical warning while you're here: getting a page out of the red is urgent, and getting it out of orange and into the green is worth doing. Paying someone to chase the last few points from 90 to 100 is not — a buyer can't feel that difference, and neither can the machine reading the page. Spend the effort where a person would notice, and stop.

Do it now

Run your own — right now

  • Go to pagespeed.web.dev.
  • Paste in the exact page a buyer lands on — the service or vertical page you actually send people to, not just your homepage.
  • Read the mobile result first.
  • The benchmark: 90 or better on Performance, Accessibility, Best Practices, and SEO; a pass on Agentic Browsing; and LCP at 2.5 seconds or under — on mobile as well as desktop.
  • Hand anything red or low-orange to whoever maintains your site, by name. "LCP, CLS, mobile" — those words tell a competent developer exactly where to look.

Then check it again after any redesign or big content change, and glance at it once a quarter. A plugin update, a new banner, or a page someone added last month can quietly undo a good score — and the tool is free, so there's no reason to find out from a buyer instead.

It's free, it takes a minute, and it's the cheapest problem on this list to fix. Good content is the hard part. This is just housekeeping — but a buyer feels it first.

Not happy with what you see?

Send us your URL, we'll check it ourselves.

Run your page through PageSpeed and don't like the numbers? Drop the link below and we'll run it, read the results, and send back specific guidance on what to fix. No meeting required — just help.

This goes to a real inbox read by a human. No sequence, no CRM, no newsletter — you get an answer, not a follow-up campaign.

Websites & Conversion PageSpeed Performance
Greg Rankin

Written by

Greg Rankin

Greg is the founder of SMR and its sister company, Security Sales Training (SST). He has spent decades inside the security industry working with dealers, integrators, and providers on sales effectiveness, marketing strategy, and go-to-market execution — with leadership experience spanning manufacturing, monitoring, and systems integration. Connect with Greg on LinkedIn.

Run it yourself

Now go check your own page.

It's free and it takes a minute. Paste the page a buyer actually lands on into PageSpeed Insights, read the mobile result first, and see where you stand against the benchmark. If you'd rather see how a page built to pass on every score is put together, take a look at how we build them.

Sources & references

  1. Google, PageSpeed Insights and Core Web Vitals thresholds — LCP under 2.5s, INP under 200ms, CLS under 0.1, measured at the 75th percentile over a 28-day window. pagespeed.web.dev · web.dev/vitals
  2. Google Lighthouse 13.3 (May 2026) added an "Agentic Browsing" category, currently marked under development — checks the accessibility tree, form annotation for agents, an llms.txt summary file, and layout stability. Category scores and score bands (90 = green, 50–89 = orange, under 50 = red) per Lighthouse documentation.
  3. Mobile/desktop medians ("~88 desktop, ~57 mobile, 4 of 10 red on mobile") are from SMR's own sample of ten integrator sites; framed as a sample, not a census. Demo-page scores shown are for our own demo site, run 2026-07-19.