Site Health Doctor for OpenCart

What it checks

• PHP errors. Reads the OpenCart error log and the PHP error log, catches errors on the pages itself, groups the same error and tells which extension it comes from. A sudden spike of errors or a new fatal error becomes a problem on the Issues screen and an e-mail.
• Server time. Measures 1 request in 10: time and memory, separately for store pages, administrator pages, AJAX, the API and the cron. Shows the slowest addresses and warns when the store became slower than its own normal.
• Database. Table sizes and growth, MyISAM tables, unused space, expired sessions and old "Who's Online" rows, and the version of the database server.
• Files and disk. Free disk space, the largest files, archives and database dumps in the web root, PHP files in the image folder, server tools left on the site, the install folder, and the storage folder of OpenCart inside the web root.
• Security. Display Errors on a live store, an administrator called admin, the administrator folder with its default name, disabled extensions that are still installed, files such as .env open to anyone, attacks and password guessing seen in the server access logs, HTTPS, HSTS and the SSL certificate expiry.
• E-mail. SPF, DKIM, DMARC and MX records of your domain, whether OpenCart sends mail through PHP mail or SMTP, and a test message to check that mail from the store arrives.
• Server and OpenCart. PHP version and its end of support, memory limit, OPcache, missing PHP extensions, Log Errors switched off, a store left in maintenance mode, and whether the background checks run on time.

What you get

• A health score from five areas: errors, performance, security, database and files, server and configuration. An area without data says "not measured" instead of pretending to be fine.
• Every problem with the fix. What was found, why it matters and the steps to fix it, with the place in the OpenCart administrator. Hide an item for 30 days if you decided to live with it.
• Alerts by e-mail for critical problems, without the same alert again and again, and a message when the problem is gone.
• A weekly e-mail with the score, new and fixed problems, errors and server time.
• A printable report of the last 7 days: print it or save it as PDF from your browser.
• Its own item in the left menu of the OpenCart administrator.

Light on your server, private by design

• A customer request never waits for the module: no database query and no outside request runs during a visit. Only 1 request in 10 writes one line to a file.
• The analysis runs in the background in short portions: in OpenCart 4 from the cron of OpenCart (cron.php), and in OpenCart 3 and 4 after the administrator pages. For checks and alerts on time in OpenCart 3, turn on the cron address of the module in Settings and call it from a cron job every 5 minutes.
• Everything is collected and stored on your own server. No account and no connection to SiteGuarding are needed; the module only asks siteguarding.com, from the administrator pages, whether a new version is out.
• Visitor addresses are shortened before they are stored, page addresses are kept without the query string, and full log lines are never kept.

• Fix it for me. Our engineer checks the problem and tells you the price before any work starts. Price after review.
• Emergency help. The store is down or shows fatal errors: we bring it back online and find the cause. Price after review.
• Site health audit. Our engineer reviews the whole store and sends you a report with the causes and a fix plan. Price after review.