Traffic Cloudflare sees at the edge. A useful signal, but not a count of unique humans — crawlers and prefetches are included.
analytics.too.foo
How this site is measured — honest numbers, plainly labelled, with the caveats kept in view. The point is transparency, not vanity metrics.
Overview
Two different systems count traffic here, and they disagree on purpose — each measures a different thing. Both are shown, labelled for what they are.
Page views inferred from Cloudflare edge analytics — requests for HTML documents, not assets.
Visits measured by Cloudflare's browser beacon (Real User Monitoring), with bots filtered out. Closer to real browser usage, but still not a unique-person count.
Page loads recorded by the browser beacon. Lower than edge pageviews because it only counts real browsers that run the beacon.
Emails submitted through the subscription form. A count only — no address, name, or message is ever exposed here.
Growth
Everything the edge has counted since this site launched. Switch between the daily rhythm and the running total, and between visits and pageviews.
— edge visits since —
Loading…
Last 30 days · browser RUM (bot-filtered)
Loading…
Pages / Projects
Most-read pages by browser-RUM pageviews. Pages with fewer than 10 views are left out.
Performance
Core Web Vitals at the 75th percentile of real visits — the field measurement Google uses to grade a page.
Loading…
Traffic Sources
Where real browser visits come from. Coarse buckets only — any slice below 10 pageviews is suppressed so it can't point at a person.
Countries
Devices
Referrers
Cache / Edge
How Cloudflare's edge handles requests to this zone (last 24h). Most traffic here is dynamic — API and worker calls that can't be cached — so a single "hit rate" would mislead; the full mix is shown instead.
Security / Bots
Automated-vs-human split from the browser beacon. Counts and trends only — never rule internals or individual actors.
Loading…
Methodology
Why two numbers, and why they disagree
Cloudflare counts traffic in two independent ways. Edge analytics tallies every request that reaches Cloudflare's network — fast and complete, but it includes bots, crawlers, prefetchers, and uptime monitors, so it overstates "people". Browser RUM (Real User Monitoring) only counts page loads where a real browser ran a small measurement script, with known bots filtered out — closer to humans, but it misses anyone who blocks scripts and undercounts.
Neither is a count of unique people. The truth sits somewhere between them, which is exactly why both are shown instead of one tidy headline. If you've ever seen a site's analytics tools disagree, this is why: they're measuring different layers of the same traffic.
Where the numbers come from
Edge figures come from Cloudflare's GraphQL Analytics API; the breakdowns and Web Vitals from Cloudflare Web Analytics (the browser beacon); the subscriber count from this site's own database. Everything is fetched live in your browser when this page loads, so what you see is current.
What is deliberately never shown
No email addresses, no subscriber messages, no IP addresses, no full user-agent strings, no raw request logs, and no security-rule internals. Any breakdown slice small enough to identify an individual is suppressed. This page is about aggregates, not people.