Most people who visit a pharmacy website do it on a phone, often on mobile data, often in a hurry. If the page takes too long to appear, jumps around while it loads or ignores the first tap, they leave — and Google notices. Core Web Vitals are how Google measures that experience. Here is what they are, the numbers to aim for and what usually goes wrong on pharmacy sites.
The three numbers
Google’s Core Web Vitals are three measurements taken from real visits to your site in Chrome:
| Metric | What it measures | Good | Poor |
|---|---|---|---|
| LCP | How long until the main thing on the page — usually the hero photo or headline — has appeared | 2.5 s or less | Over 4 s |
| INP | How quickly the page responds when someone taps a button or opens a menu, across the whole visit | 200 ms or less | Over 500 ms |
| CLS | How much the layout jumps around while loading | 0.1 or less | Over 0.25 |
INP replaced an older measure, First Input Delay, in March 2024. Unlike its predecessor it counts every interaction, not just the first, which is why sites stuffed with chat widgets and pop-ups tend to fail it.
Why it matters for a pharmacy
Speed is one of many signals Google uses, and good content still matters more. But a slow site loses patients before ranking even comes into it: someone who taps your link from the map pack and stares at a blank screen goes back and taps the next pharmacy. For nomination and repeat forms, a page that jumps as it loads means mis-taps and abandoned forms.
What slows pharmacy sites down
- Huge photos. A shopfront photo straight off a phone can be several megabytes. It should be resized and served in a modern format such as WebP or AVIF.
- Page builders and heavy themes. Generic website builders load code for features you never use on every page.
- Third-party widgets. Chat bubbles, review carousels, social feeds and multiple tracking scripts each add delay, and they are the usual cause of a poor INP.
- Cookie banners and pop-ups that shift the layout. A banner that pushes the page down after it has loaded is a classic CLS failure.
- Web fonts loaded late. Text that appears in one font and then swaps to another makes the page jump.
How to check yours
Google’s PageSpeed Insights shows two kinds of results. Field data comes from real Chrome users visiting your site over the previous 28 days, and is what Google actually uses. Lab data is a one-off simulated test, which is useful for spotting problems but can vary between runs. Smaller sites often don’t have enough visits for field data, in which case the lab score is your best guide. Search Console’s Core Web Vitals report shows which pages need work across your whole site.
Fixes, roughly in order of impact
- Compress and resize every image, and give each one a width and height so the browser reserves space for it.
- Remove widgets you don’t need. Every script should earn its place.
- Load the hero image early and lazy-load images further down the page.
- Host your fonts yourself and limit them to one or two families.
- If your site is built on a heavy theme or builder, the honest fix may be a lighter site rather than more plugins.
Every PharmGrowth website is built to pass Core Web Vitals on a phone: self-hosted fonts, compressed images with set dimensions, and no third-party widgets you didn’t ask for.