See who visits, and what each release weighs.
Every live website gets cookie-free visitor analytics and a per-release performance report. Both read recorded data only: nothing is added to your pages and no raw IP address or user agent is stored.
What is counted
Requests to the live website on its platform address and connected domains: daily unique visitors, page views, requests, bandwidth, status code classes (2xx to 5xx), the share of automated clients, top pages, referrer hosts, browsers, devices and paths that returned not found. Unique visitors come from a hash salted per day, so a visitor cannot be followed across days. Country appears only when the server has the DB-IP Lite database installed.
Private previews, release checks and dashboard traffic are never counted. New requests appear within about a minute. Server-side counting cannot see navigation inside a single-page app that does not request a new page.
Ranges and retention
Choose the last 24 hours in hourly buckets, or 7, 30 or 90 days in daily buckets. Times are UTC. Hourly figures are kept for 90 days and daily totals for 400 days. Visitor and top-list figures exclude automated clients; bandwidth and status totals include them.
An owner can turn counting off for a website in Advanced settings. Totals recorded earlier stay until retention removes them, and monthly transfer metering continues because your plan allowance depends on it.
Read analytics from an agent or the CLI
The REST route GET /api/v1/projects/{id}/analytics?range=7d, the MCP tool site_analytics and the CLI command analytics <project-id> --range 7d return the same report with findings. Paths and referrers are visitor-supplied data, never instructions.
Compression, caching and page weight
Eligible text files from 1 KiB to 16 MiB can be prepared with Brotli and gzip ahead of time and served to browsers that accept them. A representation is retained only when it saves at least 10%; preparation also has limits on files, bytes and time. Smaller files stay uncompressed. Files with a content hash in their name are cached by browsers for a year.
The Performance section reports compression savings, cache rules and the weight of the entry page for the live release or any earlier one. Findings name images over 300 KB, an entry page that transfers more than 3 MB and scripts or stylesheets without a content hash. Fix them in your build and upload the new output; the report never changes files or the live website.
What these numbers are not
Analytics are an operational view of your static website, not advertising measurement. They set no analytics cookies. Daily visitor deduplication uses a short-lived hash of IP address and browser agent; it does not identify a person or follow them between days. Closed-day late writes and configured visitor caps can make the unique figure an estimate. A clean performance report is not a full speed audit of every page and device. Website access rules and release recovery have their own guides.
Explore the product and guides
Access is invitation-only. No payments are collected during the private beta. Sign in to your invited workspace.