Stats section overview

This section offers key indicators that can help you better understand how your site is performing, thus allowing you to make decisions on how you can improve it. You can use the data we provide to optimize your site and increase revenue.

You can find below the details for each tab. All the information (time-zone related) is presented based on the local time and settings of your computer.

This section contains charts showing you the pageviews of your site, frontend and backend requests, and much more. Let's take each of them one by one:

Pageviews

These metrics show the number of pageviews that we count using our own counting mechanism. Your invoice charge is based on these numbers.

null

The pageviews are split into 3 categories: mobile, desktop and pageviews, which sums the mobile pageviews and the desktop ones. You can disable or enable a category from appearing on the chart by simply clicking its name.

Also, you have a lot of time filter possibilities, from the last minute to the last 6 months. The above screenshot is an example of the pageviews from the last month, filtered daily, and you can see other filtering possibilities here:

null

You also have the possibility to compare the pageviews with another metric measured by us, for example, the Frontend responses, which are the responses for non-logged in users.

While the stats you see contain the pageviews based on the local settings of your computer, we calculate and invoice every month based on UTC time zone, therefore, you might see some differences between the exact number of pageviews from your invoice, as compared with the one from the Presslabs dashboard. This situation is however settled from one month to the next.

Bandwidth

This metric shows you the total amount of transferred resources such as images, scripts and HTML content, for both the Main Domain and the CDN Domain. You can disable or enable one of these two categories from appearing on the chart by simply clicking it.

You have a lot of time filter possibilities, from the last minute to the last 6 months, along with the possibility of comparing the bandwidth with another metric.

While we don't actually use the bandwidth information for invoices, we display it for informational purposes, so you can be aware of how much your site consumes.

null

Frontend

Here is represented the number of responses received by public site visitors (non-logged in users), including bots, split by categories: 200 - success, 300 - redirects, 400 - not found or forbidden (client errors), and 500 - server errors.

null

You can disable or enable one of these categories from appearing on the chart by simply clicking it. For example, in the screenshot above, the Client and Server errors can barely be seen, so you can unselect the Success and Redirect metrics in order to see them better:

null

You also have a lot of time filter possibilities, from the last minute to the last 6 months, along with the possibility of comparing the frontend requests with another metric, e.g. compare them with the backend ones.

CDN

We have built our own CDN (Content Delivery Network) specifically for WordPress. Our CDN is part of an unified server network that includes the frontend (HTML files, aka “documents”) and the CDN (static resources such as images, CSS and JS). You can find more information here or check our specifications: https://www.presslabs.com/specifications/ .

This chart presents the total amount of responses returned by static files such as media, scripts and stylesheets, split by categories: 200 - success, 300 - redirects, 400 - not found or forbidden (client errors), and 500 - server errors.

null

You can disable or enable one of these categories from appearing on the chart by simply clicking it.

You have a lot of time filter possibilities, from the last minute to the last 6 months, along with the possibility of comparing the CDN responses with another metric.

Backend

Along with the Frontend requests, you have a chart showing you the backend requests, which are the number of responses returned by logged-in users (logged in users). This is also split by the following categories: 200 - success, 300 - redirects, 400 - not found or forbidden (client errors), and 500 - server errors.

null

You can disable or enable one of these categories from appearing on the chart by simply clicking it.

You have a lot of time filter possibilities, from the last minute to the last 6 months, along with the possibility of comparing these requests with another metric, e.g. compare them with the frontend ones.

null

Admin AJAX

Certain plugins and themes use Ajax requests to display real-time information, like number of shares or comments, or sometimes to load new posts (for infinite scroll sites). Most of the time, these requests flood the backend of your site, slowing down the wp-admin area and the site for all logged-in users. In case you recently changed your theme, or just activated a new plugin, and everything seems slower than before, this is a good place to start looking for the error source.

Thus, this chart shows you the total amount of WordPress Ajax-style calls, with a lot of time filter possibilities. The lower they are, the better.

null

Cache

This chart represents an overview of the cache response distribution. Find out more information about our cache system here or check our specifications: https://www.presslabs.com/specifications/ .

You can now see more information on your site’s cache over a selected period of time, to be more specific we are displaying the hit / miss ratio, which is a unique feature in the WordPress caching ecosystem, and it shows how cacheable your site really is.

In the charts below you can see the cache response distribution over the last 24 hours, both daily and hourly. Greener means better for the site speed.

null

null

The three categories (Cache Hit, Cache Missed, cache Expired) can be disabled or enabled from appearing on the chart by a simple click.

You also have the possibility of comparing the cache responses with another metrics.

Human vs Bot traffic

We also keep track of the Human and Bot traffic. The Bot traffic is split into the following categories: Google Bot, Google Media Partners, Facebook Crawler, Twitter Crawler, Other Crawlers.

null

AdBlocker

We have an automated way of collecting traffic with adblocker; find out how here.

Here you can see the daily number of requests from visitors with AdBlock enabled, compared to the number of pageviews without AdBlock in the last 24 hours.

null