Site Traffic Analytics

The Analytics tab shows the traffic your site actually served at the edge: request counts, bandwidth, cache hit ratio, visitor countries, and response codes. This guide explains what the numbers mean, what they do not include, and why the tab needs the CDN enabled.

Where Analytics Lives in KPanel

1. Sign in to KPanel.
2. Click Websites in the left sidebar, then click the site.
3. In the site's tab strip, open Performance, then Analytics.

The direct address is /websites/<site-id>/analytics.

What Powers It, and What That Means

Traffic analytics are collected at the edge by Kapsule CDN. That has two consequences worth understanding before you read a single number.

The tab needs the CDN enabled. If it is not, the page shows CDN not enabled with a button that takes you to the site's Kapsule CDN tab.

The CDN needs a custom domain. A site still on a shared *.kapsulesites.com address cannot use the CDN, so it cannot collect edge analytics either. In that case the page shows Analytics needs a custom domain with a link to the site's Domains tab.

Choosing a Period

Three buttons select the window: 7d, 30d, and 90d. Every panel on the page follows the selection, so switching period changes the totals, the daily chart, the country breakdown, and the response codes together.

The Three Headline Numbers

Requests are requests, not visitors and not page views. A single page load that pulls in a stylesheet, four scripts, and a dozen images is one page view and roughly seventeen requests. Do not compare this number with a page-view figure from a script-based analytics tool and expect them to match.

Bandwidth is what actually went down the wire, so it reflects compression and caching. It is the number to watch if you serve large media.

Cache hit is the one you can most directly influence. A high ratio means most requests never touch your server, which makes the site faster and reduces load. A low ratio on a mostly static site usually means cache headers are working against you. See Purging the CDN Cache for the controls.

Daily Requests

The Daily requests panel draws one bar per day, scaled against the busiest day in the period, with the exact count on the right.

This is where you spot the shape of your traffic: weekday peaks, campaign spikes, and the slow decline that follows a search ranking change. A sudden spike with no matching business event is usually a bot, and the response codes panel will normally confirm it.

Edge Locations

The Edge locations panel lists the top countries by bytes served, up to eight, each with a bar and its byte total.

It is measured in bandwidth rather than requests, so it answers "where is my traffic going" rather than "who visits most". A country near the top that has nothing to do with your business is worth investigating: it is often scraping.

If most of your bandwidth goes to a region far from where your site is hosted, that is a strong argument for the CDN doing its job, and for checking that your origin region is the right one. See Cloud Server Regions and Availability.

Response Codes

The Response codes panel groups responses into 2xx, 3xx, 4xx, and 5xx, each with a count.

• 2xx is success. It should dominate.
• 3xx is redirects. A large share can mean a redirect chain that is slowing every request. Check Site Redirects.
• 4xx is client errors, mostly 404s. A rising 4xx count after a site restructure means links are broken and you need redirects. See Custom Error Pages to make the landing softer, and redirects to fix the cause.
• 5xx is your application failing. Any sustained 5xx share needs attention now. Go to Site Performance and APM and your logs.

Exporting the Data

Click CSV in the page header to download the daily series. The file has four columns: date, requests, bandwidth in bytes, and cached bytes. It is named analytics-<site>-<period>d.csv.

The button is disabled when there is no daily data to export.

What This Is Not

Edge analytics answer infrastructure questions, not marketing questions. The tab does not report unique visitors, sessions, referrers, campaign attribution, bounce rate, or conversions, and it cannot, because it never runs anything in the visitor's browser.

The upside is that nothing is lost to ad blockers or consent banners: every request that reached the edge is counted, including bots, feeds, and API calls. Use this tab for load, bandwidth, cache efficiency, and error rates. Use a dedicated analytics product for audience behaviour, and expect the two to disagree.

Troubleshooting

The page says CDN not enabled. Enable it from the site's Kapsule CDN tab. Analytics start collecting once edge traffic flows. See Enabling the CDN.

The page says analytics needs a custom domain. The site is on a shared domain. Connect your own domain from the site's Domains tab first.

No data for this period. Either the CDN was enabled recently, or the site had no traffic. Try a longer period. Edge certificate issuance after enabling the CDN can take a few minutes, and nothing is recorded before traffic actually flows through the edge.

Numbers look far higher than my analytics script. Expected. Requests are not page views, and bots are counted here but usually excluded there.

Cache hit ratio is near zero. Your responses are probably telling the edge not to cache them. Check for cache-control headers set by your application or a plugin, and confirm the content is genuinely cacheable.

Analytics unavailable. A transient error reading edge data. Use the refresh icon in the page header, and if it persists, open a ticket.

Related Pages

• Site Uptime Monitoring for availability and response times.
• Site Performance and APM for what is slow inside your application.
• Site Caching for server-side caching on WordPress sites.
• Purging the CDN Cache when the edge is serving something stale.