Site Health Doctor for Magento 2

What it checks

• PHP errors. Reads the Magento logs (var/log) and the PHP error log, catches errors on the pages itself, groups the same error and tells which module or theme it comes from, and counts the error reports in var/report. 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 shop pages, the admin, REST, GraphQL and the cron. Shows the slowest addresses and warns when the shop became slower than its own normal.
• Magento speed settings. Cache types that are switched off, indexers that need attention, index updates that fall behind, the hit rate of the full page cache, blocks that switch the page cache off, sessions stored in files, no shared cache for configuration, OPcache settings that do not fit Magento and Xdebug left loaded.
• Cron and scheduled tasks. Whether the cron of Magento runs on time, tasks that are stuck or failed, and a task table that grew too large.
• Database. Table sizes and growth, unused space, character sets, log and visitor tables that grew for nothing, and the version of the database server.
• Files and disk. Free disk space, the largest files, archives and database dumps in pub/, PHP files in pub/media, foreign PHP files in pub/, server tools left on the site and an oversized var folder.
• Security. A shop that is not in production mode, two-factor sign-in that is off, the default admin address, an administrator named admin, files such as auth.json or logs open to anyone, attacks and probes seen in the server access logs, password guessing on the customer and API logins, HTTPS, HSTS and the SSL certificate expiry, and the end of support of your Magento version.
• E-mail. SPF, DKIM, DMARC and MX records of your domain, whether Magento sends mail through the sendmail program or SMTP, and a test message to check that mail from the shop arrives.
• Server and PHP. PHP version and its end of support, memory limit, missing PHP extensions, a shop 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 Magento admin. 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 admin menu: System > Tools > Site Health Doctor.
• A command line check: bin/magento sgshd:status prints the score, the open problems and the state of the cron job.

Light on your server, private by design

• A visitor 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 from the cron of Magento.
• 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 admin 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 shop 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 shop and sends you a report with the causes and a fix plan. Price after review.