Agent view · Guides · 2026-10-02
Core Web Vitals without CrUX: field data for small sites
This is the response this server returns to a client that asks for Accept: text/markdown at https://crawlcheck.io/guides/core-web-vitals-field-data-for-low-traffic-sites-without-crux: fetched when you opened this page, shown byte for byte. An assistant, a crawler that negotiates markdown, or anything reading our feed gets exactly this. The markdown leaves signed (RFC 9421, key in our key directory), so a crawler can prove the page it read is the page this server sent; the check is shown below.
| status | 200 |
|---|---|
| content-type | text/markdown; charset=utf-8 |
| vary | Accept |
| link | <https://crawlcheck.io/llms.txt>; rel="describedby"; type="text/plain", <https://crawlcheck.io/.well-known/api-catalog>; rel="service-desc"; type="application/linkset+json", <https://crawlcheck.io/guides/core-web-vitals-field-data-for-low-traffic-sites-without-crux>; rel="cite-as", <https://crawlcheck.io/.well-known/http-message-signatures-directory>; rel="http-message-signatures-directory" |
| cache-control | public, max-age=900, stale-while-revalidate=2400 |
| bytes | 15,733 |
| words | 2,281 |
| sha-256 | 81ac8cae1f1f5698127b051bf4b1d25a9355a5ceefc63ffb31319de7ca9c681b |
| repr-digest | sha-256=:gayMrh8fVpgSewUb9LHSWpNVpc7vxj/7MTGd58qcaBs=: ← matches the body shown |
| signature-input | sig1=("@authority";req "@path";req "repr-digest" "content-type");created=1795311494;expires=1795315094;keyid="1hHmE3fo1rg5Ig70wuFtJ5wBc7G-sUTgUJkxyPWFRps";alg="ed25519";nonce="CKQyowhlWCEqPwjAJHIu5w";tag="crawlcheck-page" |
| signature | sig1=:4CIUkuzs1HEsUlWcB7pL9d4CVV9WhyoYHxXJF7vZXkfjqfPg8c2JzQNp0APhhgZUjc/tT900TdL4Lj6qcCstDA==: |
| verified | yes — signature by key 1hHmE3fo1rg5Ig70… from https://crawlcheck.io/.well-known/http-message-signatures-directory (directory valid), valid for 3600 more s. Checked here exactly as a crawler would; redo it yourself: https://crawlcheck.io/api/tool/wba |
Guides · 2026-10-02 · By [VSNARY | Emmanuel Orta](/author) · 1 view # Core Web Vitals without CrUX: field data for small sites PageSpeed Insights says "no data" for most small sites because the Chrome UX Report needs more real users than they have. Lab scores are not a substitute. How to collect your own field data, the thresholds to judge it against, and the sample size below which a percentile means nothing. Core Web Vitals field data comes from the Chrome UX Report, which only includes origins and pages with enough real Chrome traffic, so most local and small-business sites show no field data in PageSpeed Insights. A Lighthouse run is lab data from one synthetic load and is not a substitute. The alternative is first-party real-user monitoring: load the web-vitals library, send LCP, INP and CLS from each page view to your own endpoint, and compute the 75th percentile over 28 days, judged against good thresholds of 2.5 seconds, 200 milliseconds and 0.1. Below about 100 samples, report the count, not a percentile. Check your own site free Check my site About a minute. First scan free with your email, nothing installed. On this page - Why CrUX has no data for your site - Why a lab score is not a substitute - The thresholds - Collecting your own field data - The sample-size floor - Storing and reading the samples - Reading the result Run a small business site through PageSpeed Insights and the top half of the report, the part labelled with what real users experience, usually says there is not enough data. That section comes from the Chrome UX Report, and the report only includes sites with enough real Chrome visitors. Most local sites never get there. What remains is the [Lighthouse](/glossary/lighthouse) lab run underneath, which measures one simulated page load and is routinely mistaken for the real thing. This guide explains why [field data](/glossary/field-data) is missing, why [lab data](/glossary/lab-data) cannot fill the gap, and how to collect field data of your own that is honest about its sample size. ## Why CrUX has no data for your site # The Chrome UX Report aggregates measurements from Chrome users who have opted into usage statistics, over a rolling 28-day window. Google includes an origin or a page only when it is publicly discoverable and has a sufficient number of samples; the threshold is not published. A site with a few hundred visitors a month falls below it, and the PageSpeed Insights fallback queries the same dataset, so it returns nothing too. This is not a defect of the site. It is the dataset's eligibility rule, and it excludes most of the businesses that would benefit from field data. ## Why a lab score is not a substitute # Lighthouse loads the page once, on a simulated mid-range phone over a throttled connection, from one location. That is a controlled experiment, useful for finding what to fix, but it is not what visitors experience. It cannot measure Interaction to Next Paint at all, because no one interacts with a lab load; it reports Total Blocking Time as a proxy. And repeated runs vary widely. We measured the spread of a single page's lab score across runs in [one Lighthouse run cannot support a finding](/blog/one-lighthouse-run-cannot-support-a-finding-225-percent-variance); the variance was large enough that one run should never be reported as a site's performance. ## The thresholds # | Metric | Good | Needs improvement | Poor | Measured at | | --- | --- | --- | --- | --- | | Largest Contentful Paint | ≤ 2.5 s | 2.5–4.0 s | > 4.0 s | 75th percentile of page loads | | Interaction to Next Paint | ≤ 200 ms | 200–500 ms | > 500 ms | 75th percentile of page loads | | Cumulative Layout Shift | ≤ 0.1 | 0.1–0.25 | > 0.25 | 75th percentile of page loads | A page passes when all three are good at the 75th percentile. The percentile matters: it means three in four visits were at least that fast, which is a statement about the population, not about one load. ## Collecting your own field data # Google's open-source `web-vitals` library reports [LCP](/glossary/lcp), [INP](/glossary/inp) and [CLS](/glossary/cls), plus [TTFB](/glossary/ttfb) and First Contentful Paint, from real page views in any modern browser. The minimal setup loads the library and sends each page view's values to an endpoint you control when the page is hidden, which is when CLS and INP are final. Send one beacon per page view rather than one per metric, strip the query string and fragment from the [URL](/glossary/url) before sending, and set no cookies or identifiers. The attribution build also reports which element was the LCP and which sub-phase was slow, which tells you what to fix rather than only how slow it was. We run this on crawlcheck.io and on every site we operate, self-hosted rather than loaded from a third-party [CDN](/glossary/cdn), and disclose it in our privacy policy: path only, timings and a coarse element name, nothing that identifies a visitor. ## The sample-size floor # A 75th percentile computed over twelve visits is noise. One slow load on a bad connection moves it by seconds. Report no percentile until a page or origin has about 100 samples in the 28-day window, and show the sample count instead. Below the floor the honest statement is "not enough visits yet", the same thing [CrUX](/glossary/crux) says, but with a number attached and a floor a reader can see. When samples are stored in histogram buckets, interpolate within the bucket rather than reporting the bucket edge: in our tests the edge overstated the true p75 by up to 5.8 percent, always high, and interpolation brought the error within 1.8 percent. ## Storing and reading the samples # Each beacon is small, a few hundred bytes, but the storage design decides whether the numbers are trustworthy. Writing every sample to a log or an analytics table and computing percentiles at read time is the most accurate approach. Pre-aggregating into histograms is cheaper; if you do, check that simultaneous writes cannot drop samples. Losing samples at random does not bias a percentile, it only slows the approach to the sample floor, but it is worth knowing before trusting a sample count. Weight sampled data correctly. If the collector records only one page view in ten to save cost, each recorded sample stands for ten, and the sample count shown against the floor should reflect recorded samples, not the estimate. Separate mobile and desktop, because they are different populations and a site can pass on one and fail on the other. And keep the attribution: the LCP element and its slowest sub-phase, and the INP target and whether its delay was input delay, processing or presentation. The percentile tells you whether there is a problem; the attribution tells you where. ## Reading the result # Keep the three sources separate and label every number with where it came from. CrUX field, first-party field and lab are three different measurements; averaging them produces a number that describes nothing. Use first-party field data to decide whether there is a problem, and the lab run to diagnose it. If LCP is the problem on a page that is [mostly code](/guides/text-to-html-ratio-when-a-page-is-mostly-code), the payload is usually where to start. Our analytics script once added 650 milliseconds to every request on our own site, written up in [our analytics was adding 650 ms](/blog/our-analytics-was-adding-650ms-to-every-request); a measurement tool can be the slowest thing on the page. CrawlCheck’s dataset when this page loaded: 582,334 sites measured. Written by [Emmanuel Orta](/author) · VSNARY I build CrawlCheck and write everything published here, from measurements the verification layer took. Where a post got something wrong, the correction stays in the post. [Every post, and where I got it wrong →](/author) · [Follow on LinkedIn →](https://www.linkedin.com/in/emmanuelorta) Share this finding: [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcrawlcheck.io%2Fguides%2Fcore-web-vitals-field-data-for-low-traffic-sites-without-crux%3Futm_source%3Dlinkedin%26utm_medium%3Dsocial%26utm_campaign%3Dshare)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fcrawlcheck.io%2Fguides%2Fcore-web-vitals-field-data-for-low-traffic-sites-without-crux%3Futm_source%3Dx%26utm_medium%3Dsocial%26utm_campaign%3Dshare&text=Core%20Web%20Vitals%20without%20CrUX%3A%20field%20data%20for%20small%20sites)[Email](mailto:?subject=Core%20Web%20Vitals%20without%20CrUX%3A%20field%20data%20for%20small%20sites&body=https%3A%2F%2Fcrawlcheck.io%2Fguides%2Fcore-web-vitals-field-data-for-low-traffic-sites-without-crux)[Follow Emmanuel on LinkedIn](https://www.linkedin.com/in/emmanuelorta) ## Questions this post answers ### Why does PageSpeed Insights show no field data for my site? Field data comes from the Chrome UX Report, which only includes sites with enough real Chrome visitors over 28 days. Most small sites fall below the unpublished threshold. ### Is a Lighthouse score the same as Core Web Vitals? No. Lighthouse is lab data from one simulated load. Core Web Vitals assessments use field data at the 75th percentile of real page loads. ### What are the Core Web Vitals thresholds? Good is LCP at or under 2.5 seconds, INP at or under 200 milliseconds and CLS at or under 0.1, each at the 75th percentile. ### How can I measure Core Web Vitals without CrUX? Load the open-source web-vitals library on your pages and send each page view's LCP, INP and CLS to your own endpoint, then compute the 75th percentile over 28 days. ### How many samples do I need before trusting a p75? Use a floor of about 100 samples in the 28-day window. Below that, a single slow visit moves the percentile too much to mean anything, so show the sample count instead. ### Can Lighthouse measure INP? No. INP needs real user interactions. Lighthouse reports Total Blocking Time as a lab proxy. ## Related findings [2026-10-02 Content-Signal in robots.txt: search, ai-input, ai-train Content-Signal states preferences for search, ai-input and ai-train. It blocks nothing. Refusing ai-train costs no reach; refusing](/guides/content-signals-in-robots-txt-search-ai-input-ai-train)[2026-08-21 Analytics added 650 ms to every request: how we found it Our own visit recording added about 650 ms to every response. Two pages located it, one change fixed it, and how to check your ser](/blog/our-analytics-was-adding-650ms-to-every-request)[2026-08-20 AI visibility scores measure an API, not ChatGPT AI visibility scores sample a model API, not ChatGPT. The three gaps between the number and the claim, and five questions to ask a](/blog/ai-visibility-scores-measure-an-api-not-chatgpt) The main product Found this on your own site? **We fix it for $100.** Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after. [Fix it all — $100](https://buy.stripe.com/4gM00j7OjawhdLEdyR2VG0v) [What it covers](/pricing#fix) · [scan first, it is free](/) Free browser extension Check this on any site you open, **without leaving the page.** CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account. [Add to Chrome — free](https://chromewebstore.google.com/detail/plgjengobhbdmbgckiiaaflgiepdbcpi?utm_source=crawlcheck.io&utm_medium=post) [What it does](/extension) Write for the library Measured something yourself? **Submit an article.** Send your finding, the data and the method. A person reads every submission and replies by email; accepted articles are published under your name with a link to your study. Free to submit. Articles are accepted on merit; no one can pay to have one published. [Submit an article](/submit-finding#send) [How it works](/submit-finding) · a reply within about a week Spotted a mistake or a bug on this page? [Report an error](/report-error?k=article). Confirmed errors are fixed and logged on the [corrections page](/corrections). ## Comments Comments are read before they appear. Nothing is published automatically, and no account is needed. An AI agent with a published signing key can post without the queue: it signs the request and the signature is checked against its own domain ([how](/api/comment/signed)). Those appear at once, marked *verified*. Send for review Writing about this? [Facts, live figures and marks](/press) — every number on that page is dated and traceable to a scan. [All guides](/guides) · [The dataset](/data) · [How the dataset works](/policy) We read your site the way crawlers do, from our own network, and every report says exactly what was asked for and what came back. [Who runs this](/author) · [Press kit](/press) · [Videos](/videos) · [Evidence for disputes](/evidence) · [YouTube](https://www.youtube.com/@crawlcheck) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io) #### How we measure, and our own machine files CrawlCheck reads every site as itself. Its crawler-identity tests send named user-agent strings from its own network, never from an operator’s published range, so a site that verifies crawlers can tell them apart; every report says so. Results reflect what an anonymous non-browser client receives. [What we collect and how to opt out](/policy) · [how every report is timestamped](/proof) · [who runs this](/author) · [press kit](/press) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io). **Second vantage:** the [browser extension](/extension) measures what crawlers are served from your own address and after your JavaScript runs — the half this server cannot see. From 1.0.0 it sends the domain you ask about, on one button, and anonymous usage counts you can switch off; from 1.0.3 a footer switch turns off the hostname lookup for the grade on the icon; from 1.0.4 a share switch, on by default, sends a signed Two-vantages reading (status, size, words and a hash per identity; never page text); from 1.0.16 chips send the hostnames of search results and AI citations while the chips and grade switches are on; from 1.0.17 a readings switch, on by default, sends one signed page reading a day (numbers, the hostname and the page address with the query removed; never in incognito; at most 40 a day) and only while the share and grade switches are also on. Earlier versions send nothing. **Our own machine layer for the agentic web:** [llms.txt](/llms.txt) · [llms-full.txt](/llms-full.txt) · [agents.md](/agents.md) · [SKILL.md](/SKILL.md) · [entitymap.json](/entitymap.json) · [media kit](/.well-known/media-kit.json) · [MCP server card](/.well-known/mcp/server-card.json) · [API catalog](/.well-known/api-catalog) · [OpenAPI](/openapi.json) · [robots.txt](/robots.txt) · [sitemap.xml](/sitemap.xml) · [security.txt](/.well-known/security.txt) — every one named in robots.txt, which is exactly what we check for on yours. **Registry:** [AI policy](/registry/aipolicy) · [baidu.com](/registry/baidu.com) · [dimamedia.ir](/registry/dimamedia.ir) · [ilkadimlarim.com](/registry/ilkadimlarim.com) · [nikkei.com](/registry/nikkei.com) | **Pages:** [IP ranges](/data/ip-ranges) · [Keys](/keys) · [/](/) | **Glossary:** [Transactional query](/glossary/transactional-query) · [ARIA](/glossary/aria) · [self-claim ledger](/glossary/self-claim-ledger) · [OpenSearch description](/glossary/opensearch-description) [Contact](/contact) · [Partnerships](/partnerships) · [Terms of service](/terms) · [Refund policy](/refunds) · [Trust center](/trust) · [Subprocessors](/subprocessors) · [Changelog](/changelog) · [Report an error](/report-error)
Same body as a file: /guides/core-web-vitals-field-data-for-low-traffic-sites-without-crux.md · as data: /feed.json · what we tell agents site-wide: /llms.txt, /agents.md. To see any other site this way, from your own browser, after its JavaScript runs: the browser extension.