Skip to main content
web60

SEO & PageSpeed

Core Web Vitals Not Enough Data? Google Is Not Checking Your Speed. Your Customers Are.

Ian O'Reilly··13 min read
Flat illustration of teal and navy lines sweeping upward towards an empty outlined circle on a warm stone grey background

A Core Web Vitals report that says "Not enough data" is not a pass mark, and reading it as one is how small business websites stay slow for years without anyone noticing.

Most owners meet this message the first time they open Google Search Console. The speed panel is empty. No red, no amber, no list of failing pages. That looks like good news. Strictly, it is not bad news either. What you are looking at is an absence, and an absence of measurement means exactly one thing in operations: nobody is watching this system, so if it is failing, the failure is silent.

That is the position most small business websites are in today. I think it deserves a plainer explanation than Google gives it, and a short routine to replace the report you are not getting.

What the Message Actually Means

Search Console does not time your website itself. Its Core Web Vitals report is built from the Chrome UX Report, usually shortened to CrUX, which gathers anonymised timings from real Chrome users as they visit pages [1]. That data source has entry rules.

Google's CrUX documentation sets two conditions for a page, or a whole site, to be included [2]:

  • Publicly discoverable. The page has to be one a search engine could index, so a page marked noindex or returning an error is never counted.
  • Sufficiently popular. The page has to reach a minimum number of visitors. Google does not publish the exact number.

You cannot submit your site to be included, either. Eligibility is reassessed automatically.

When a group of similar pages falls short, Search Console tries again one level up, combining every page on your domain into a single origin group. If the whole site still falls short, the report simply shows nothing [1]. PageSpeed Insights follows the same ladder: page data first, then site-wide data, then a blank where real-user results would sit [3]. That blank is the main reason owners mistake a lab score for the whole story, and the gap between a PageSpeed score and real-user data is worth understanding before you act on either.

So what does this mean for a business site with a few hundred visitors a week? An empty report is the normal state. Nothing is broken and nothing in the report needs fixing. But no one is measuring anything, either.

The Customers Chrome Data Never Counted

Even a full report is a sample, and a narrower one than most people assume. CrUX is Chrome data. Google lists who is excluded: Chrome on iPhone, Android apps using an in-app browser view, and other Chromium-based browsers such as Microsoft Edge [2]. Safari is not Chrome, so it was never in the dataset to begin with. The users who are included must also have opted into usage statistics and browser history sync [2].

Now set that against the Irish market. According to StatCounter, iOS accounted for a little over 48% of mobile operating system share in Ireland in October 2026, with Android just under 52% [5]. Those figures drift a point or two from month to month. The direction does not change: close to half of your mobile visitors are on iPhones, and none of their visits feed Google's field data.

The practical consequence is straightforward. A site with a populated report is reading a partial sample of its visitors. With "Not enough data", there is no sample at all.

Rankings Are the Smaller Worry

The first question owners ask is whether an empty report hurts their position in Google. Mostly, no.

John Mueller of Google addressed this on Mastodon in 2023, as reported by Search Engine Roundtable. Where Google does not have full CrUX data for a site, that data is not used, and for most small and local businesses he said Core Web Vitals work "shouldn't be top of the list" [4]. I agree with him. I would go further: the ranking question is a distraction from the cost that does apply.

That cost is customers. A study commissioned by Google and carried out by Deloitte across large retail, travel, luxury and lead generation brands in Europe and the US found that shaving a tenth of a second off mobile load times was associated with retail conversions rising by roughly 8% [6]. These were big brands with big traffic, measured over four weeks, so a small shop should not expect the same figure. The direction is the useful part. Speed and sales move together, whether Google is measuring you or not.

A Composite Case: The Enquiry That Never Arrived

Consider a composite, built from a pattern that comes up regularly rather than from any one business. A farrier in Carlow gets most new customers the same way: a horse owner in a stable yard, a thrown shoe, a phone with one bar of signal, a search for a farrier nearby.

His website's Core Web Vitals report has said "Not enough data" since launch. The homepage opens with a full-width video of the forge, and the phone number sits below it. On the office broadband it looks impressive. In the yard, the page is still filling in when the horse owner gives up and rings the next name in the results.

Nothing flagged it. Not one customer complained, because customers who leave do not write in. The enquiry went to a competitor, and the farrier never knew it existed. That is what an unmeasured slow site costs: not a penalty you can see, but work that quietly stops arriving.

Flat illustration of a simple phone outline with teal signal arcs rising and fading upward on a warm off-white background
When Google has no field data for your site, the only real-world speed test is the one you run on a phone yourself.

Five Checks to Run in Place of the Missing Report

You do not need a developer for this. You need a phone, twenty minutes and a note you can find again.

  1. Run the lab test. Put your homepage into PageSpeed Insights, ignore the empty real-user panel at the top and scroll to the lab results, which simulate a mid-range phone on a mobile network [3].
  2. Verify on a real handset. Load your homepage and your most important page on an ordinary Android phone with wifi switched off, in a private browser tab so nothing is remembered from a previous visit.
  3. Measure the first useful moment. Count the seconds until a customer could act, meaning they can see your phone number, your prices or your booking button, rather than waiting for the page to finish.
  4. Record a baseline. Write the lab results and your phone timings into a dated note, so you have something to compare against next time.
  5. Re-verify after every deploy. Repeat the checks whenever a new plugin, theme, video or gallery is pushed to production, and roll back the change if the numbers jump.

What These Checks Cannot Tell You

Be clear about the limits. The lab test is one simulated device on one fixed set of network conditions, and Google says plainly that it may not capture real-world bottlenecks [3]. Run it twice and the score can move by a few points. Your own phone test is a sample of one person, in one place, on one day.

Neither replaces thousands of real visits. What they do catch is the large slowdowns, the five-second homepage and the gallery that loads forty full-size photos, and the large slowdowns are the ones that lose enquiries. Do not chase a perfect score. Chase the moment a customer can see your number.

Flat illustration of stacked teal layers forming a solid base with a single teal ribbon rising from the top on a warm grey background
Measurement finds the slowdowns. The layers underneath the site decide how many there are to find.

What a Fast Site Is Built On

Measurement tells you whether you have a problem. It does not fix one. Before naming any platform, it helps to set out what a properly built small business site should have underneath it:

  • A server close to the people using it. Every request your visitor's phone makes has to travel there and back, so a server in Ireland answers Irish visitors faster than one on another continent.
  • Pages served from a cache. A fast site hands out a ready-made copy of each page instead of rebuilding it from the database on every visit, which is the difference between a page appearing and a page being assembled while the customer waits.
  • Database lookups held in memory. The parts of WordPress that cannot be cached as a whole page, such as a shop basket, still answer quickly if frequent queries are kept in memory.
  • A safe place to test changes. A staging environment lets you try that new plugin or homepage video before it reaches production, so the slowdown happens where no customer can see it.

Web60 was built to meet that list. Sites run on SmartHost's sovereign Irish cloud, so your data and your visitors' requests stay in Ireland. The stack is Nginx with FastCGI page caching and Redis object caching, which in practice means a visitor on a weak signal gets a ready-made page rather than waiting for one to be built. One-click staging is included, so the five checks above can run on a copy before anything is deployed. All of it comes as part of Web60's Irish hosting stack, with page and object caching built in, for €60 a year, alongside the AI builder that puts a WordPress site in place in about a minute.

One honest caveat. Caching cannot fix content. If the homepage carries a large autoplay video, the server will deliver it quickly, and the phone will still struggle to download it on one bar of signal. That part of the job belongs to whoever decides what goes on the page, which is why our complete guide to WordPress performance for business owners spends as much time on images and plugins as on hosting.

The concession runs the other way too. If you run a busy online shop with enough traffic for a fully populated CrUX report and a developer on staff, enterprise managed hosts that bundle application performance monitoring and real-user monitoring genuinely suit that workload better. That is a different business from a farrier answering calls in a yard.

When the Report Finally Fills In

If your traffic grows, the data will eventually appear, and it is worth knowing how to read it. Google rates each group of pages on three measures, using the experience of the slowest quarter of visits (the 75th percentile) over the previous 28 days [3].

MeasureWhat it tracksGoodPoor
Largest Contentful Paint (LCP)Time until the main content appears2.5 seconds or lessOver 4 seconds
Interaction to Next Paint (INP)How quickly the page responds to a tap200 milliseconds or lessOver 500 milliseconds
Cumulative Layout Shift (CLS)How much the page jumps while loading0.1 or lessOver 0.25
  • LCP is the one owners feel first: the wait before the hero image or headline arrives. On small business sites the culprit is usually an oversized image or video at the top of the page.
  • INP measures the gap between a tap and a visible response, such as a menu opening or a form field reacting. Heavy plugins and third-party widgets are the usual cause of a slow one.
  • CLS catches the page that moves under your thumb, typically when a banner or image loads late and pushes everything down, so the customer taps the wrong button.

Once you fix something, Search Console's Start Tracking button opens a 28-day monitoring session to confirm the change has held [1]. Expect that to feel slow. It is measuring weeks of real visits, not one test.

The Empty Report Is a Job, Not a Verdict

"Not enough data" tells you about Google's sample, not about your website. It does not mean the site is fast, and on the evidence from Google itself it is unlikely to be holding back your rankings. It means the responsibility for knowing how the site performs sits with you, and the tools for that are free and take less than half an hour.

So pick up the most ordinary Android phone in the house, switch off the wifi and load your homepage. How long it takes for your phone number to appear is the measurement Google was never going to take for you.

Frequently Asked Questions

What does Not enough data mean in the Core Web Vitals report?

It means Google's Chrome UX Report has not collected enough real visits from eligible Chrome users to report on your pages, or on your site as a whole. Google does not publish the exact threshold. Nothing on your website is broken and there is nothing to fix in Search Console; the report will fill in automatically if your traffic reaches the minimum.

Does Not enough data hurt my Google rankings?

Not directly. John Mueller of Google has said that where full CrUX data does not exist for a site, it is not used, and that for most small and local businesses Core Web Vitals should not be the top priority. Relevance and useful content matter far more. Speed still affects whether visitors stay long enough to contact you, so it is worth measuring yourself.

How much traffic do I need to get Core Web Vitals data?

Google does not say. Its CrUX documentation states that pages and sites must be sufficiently popular, with a minimum number of visitors, and that the exact number is not disclosed. The visits also have to come from Chrome users on desktop or Android who have opted into usage statistics, so total visitor numbers in your analytics will be higher than what Google counts.

How can I test my website speed without field data?

Run your homepage through PageSpeed Insights and read the lab results, which simulate a mid-range phone on a mobile network. Then load the same page on a real Android phone with wifi switched off, in a private tab, and time how long it takes before a customer could see your phone number or booking button. Note the results with a date and repeat the checks after every significant change.

Does Core Web Vitals data include iPhone users?

No. The Chrome UX Report only includes Chrome on desktop and Android. Google explicitly excludes Chrome on iOS, and Safari is a different browser altogether. With iPhones making up close to half of mobile use in Ireland, test your site on an iPhone as well as an Android handset if you can.

Why does PageSpeed Insights show a score but no real-user data?

The score comes from a lab test that PageSpeed Insights runs on the spot, so it is always available. The real-user section comes from the Chrome UX Report, which only covers pages and sites with enough eligible visits. When neither the page nor the whole site qualifies, that section stays empty while the lab score still appears.

Sources

IO
Ian O'ReillyOperations Director, Web60

Ian oversees Web60's hosting infrastructure and operations. Responsible for the uptime, security, and performance of every site on the platform, he writes about the operational reality of keeping Irish business websites fast, secure, and online around the clock.

More by Ian O'Reilly →

Ready to get your business online?

Describe your business. AI builds your website in 60 seconds.

Build My Website Free →
Buy NowTry Free
Core Web Vitals Not Enough Data: What It Means | Web60