Docs

Statistics and Logs

The Visitor Log and visitor summary, the Error Log, Data Transfer, downloading access logs, and finding slow PHP pages.

5 min read Updated From the panel's guide

The web server writes down every visit to your websites and every error. These tools show you who visits, which pages are popular, what goes wrong, how much data your websites send, and which PHP pages are slow.

In the modern look they are under Performance in the menu (tabs Visitors and logs and Slow pages (PHP)); in the classic look in the Statistics group on the Tools page.

Visitor Log and visitor summary#

To see your visitors, open Visitor Log (the Visitors and logs tab under Performance). Pick the Website at the top and choose Open. Three buttons switch the view: Visitors, Latest visits and Errors.

Visitors summarises the end of the website's visitor log (the most recent visits, up to about 16 MB of log):

  • Summary: the period covered, the number of requests, different visitors (counted by internet address), data sent, pages not found (404) and server errors (5xx).
  • By day: requests, visitors and data for each of the last 30 days in the log.
  • Most opened pages and files, Websites that link here, Busiest addresses and Answers by status code: the top entries of each.

Latest visits shows the newest lines of the visitor (access) log, newest first, up to 200 lines. Each line has the visitor's address, the time, the page asked for, the answer code and the size, usually followed by the linking page and the browser.

Good to know:

  • Visitors are counted by internet address, so several people behind one office connection count as one, and a person on a phone may count several times.
  • Every file counts as a request: a page with 20 images is 21 requests.
  • Many requests from one address in Busiest addresses can be a search engine or an attack. You can block an address under Block Visitor IPs.

Error Log#

The error log shows what went wrong on a website: missing files, refused requests and errors from the web server. Open Error Log, pick the website and choose Errors.

The newest lines come first, up to 200. Each line says when, from which address, and what the problem was.

PHP's own errors (warnings, fatal errors and notices from your scripts) are written to a file named error_log in the folder of the script that raised them: an error of public_html/index.php goes to public_html/error_log, one of public_html/wp-admin/admin.php to public_html/wp-admin/error_log. The file appears by itself with the first error; open it in the File Manager to read it, and delete it when you no longer need it. Visitors cannot open it.

Typical things to look for:

  • "File does not exist" for a page or image a visitor asked for: a broken link, or a file not uploaded.
  • "client denied": an address blocked by your settings, or a password-protected folder.
  • A white page or "500" error on your website: look in the error_log file in the folder of the page that failed (or the website's main folder) for a "PHP Fatal error" line at the same time.

Good to know:

  • Showing PHP errors to visitors is normally off; you can change that with Show errors to visitors in the PHP settings on Website settings, but do it only while testing.

Data Transfer#

Data transfer (bandwidth) is how much data your websites send to visitors. Open Data Transfer (the Overview tab under Performance).

  • The Data Transfer card shows this month's total, your package's monthly limit and the share used, compared with last month.
  • Data transfer by website lists this month's total per website.
  • Earlier months lists the totals of past months.

The Dashboard and the Resource Usage box also show "Data transfer this month".

Good to know:

  • The figure is counted from your websites' visitor logs every few minutes, so it may lag a little.
  • It starts again at zero each month.
  • When your account goes over its package's monthly limit, your websites answer "bandwidth limit exceeded" (error 503) instead of their pages until the next month starts or the limit is raised. Mail, FTP and the client area keep working. Ask your hosting provider for a larger limit if you need one.
  • You can get an email at 80% of the limit: tick that notice under Notification Settings.
  • To send less data, switch on compression (see Website Compression) and make images smaller.

Download Access Logs#

You can download a website's complete logs to analyse them with your own tools. Open Download Access Logs (the Visitors and logs tab under Performance) and pick the website.

Next to "Download the whole log, compressed":

  • Access log downloads the visitor log as domain-access.log.gz.
  • Error log downloads the web server's error log as domain-error.log.gz.

The files are gzip-compressed text in the usual Apache log format, which log analysers such as GoAccess or AWStats understand. On Windows, open them with a program such as 7-Zip; on macOS and Linux double-click or use gunzip.

Good to know:

  • The download holds the current log file of the website. Older log entries may already have been rotated away by the server.
  • Logs contain your visitors' internet addresses. Handle the files with care.

Slow Pages (PHP)#

Slow Pages finds out what makes PHP pages slow: which plugin, theme or file, and whether it was waiting for the database or another server. Open Slow Pages (PHP) (the Slow pages (PHP) tab under Performance) and pick the website.

To start tracing:

  1. Tick Note pages that take longer than and enter a number of seconds (1 to 120; 5 is a good start).
  2. Choose Save. PHP for that website restarts for a moment.
  3. Leave it on for a day or so, then come back.

When a page takes longer than that, PHP notes what it was doing at that moment. Where the time goes then counts the slow pages by:

  • Plugin, theme or file responsible,
  • What it was doing: waiting for the database, waiting for another server or a file, pausing on purpose (sleep, lock), or running PHP code,
  • Page that was asked for.

Latest slow pages lists each one; open a line to see the chain of functions, innermost first. Empty the list clears it.

Good to know:

  • Tracing costs almost nothing while pages are fast.
  • Mostly "waiting for the database" points at slow queries or a large database; "another server" at a plugin calling an outside service.
  • Untick the box and Save to stop tracing.
Was this article helpful?

Something missing? Ask in the community or open a ticket.