Beyond automation
—
Non-bot page loads
May include owner and development activity.
Analytics · transparent measurement
Measurable wake.
See where attention lands across Diamond Gate Bridge, with the evidence and its limits in view.
Loading the latest snapshot…
Data through —Last checked —
Source collection is scheduled hourly. This page checks every minute while open.
Rolling 30 days
Loading reporting window…
—
Total page loads
All recorded activity.
—
Bot-classified page loads
Excluded from the non-bot figure.
—
Google-referred visits
Visits are not unique people.
Activity over time
The shape of the wake
30 UTC calendar days · includes bot and owner activity.
Last 7 complete days · all traffic
Loading comparison…
Selected dayPartial day
Waiting for daily history from the collector.
View daily values
| Date | Page loads |
|---|
Destinations
Where attention lands
Top destinations · page loads, including bot and owner activity.
Arrival points
How visits arrive
Visits from up to eight reported sources · not a complete traffic breakdown.
How we count
Page loads count page activity. Visits are a separate measure; neither is a unique-person count. Non-bot totals exclude traffic Cloudflare classifies as automated.
Current measurement boundary
The summary and rankings cover a rolling 30-day window, ending at the snapshot time. The chart shows 29 complete UTC days and the partial final day. Their start times differ, so the bars need not add up to the summary total. Weekly comparisons use complete UTC days only.
Home combines / and /index.html. Each ranking entry discloses its recorded sources. “No referrer reported” means the source was not supplied; it does not establish how someone found the site.
— of three registered development-device heartbeat paths were observed in the snapshot’s six-hour check.
A heartbeat confirms activity on that dedicated path. It does not identify all visits made by that device elsewhere. Owner traffic has not been deterministically subtracted from the totals shown here.
Historical owner activity is uncertain. Source processing, collection, and publication can introduce delays.
Source: Cloudflare Web Analytics. “Data through” is the requested reporting-window end, not a guarantee that all recent activity has finished processing.