WordPress site health

As of version 5.2 (Mid 2019), WordPress includes its own tool to diagnose the health of your site.

Many admins continue to use a third party plugin to check for errors on their site, unaware that WordPress already includes a tool extremely complete to take a look at the heart of our website.

To access it, simply search for the tool within Tools » Site Health as indicated in the screenshot below.
Note: the tool divides its benefits into two tabs, "Status" and "Information".

The health tool checks for any security and performance issues that may occur on a site, and provides instructions and remedies to improve them.

Basically, this native tool checks the status of your website, displaying clear information about global settings. It not only detects conflicts, but also provides measures you can take to resolve them.

The site's health tool neatly arranges your notices, noting warnings, recommendations, tests completed, and explanations of what can be improved, and how.

Let's see:

“Status” tab

Site Health Status displays critical information about your WordPress setup and items that require attention.

There are two categories into which the report is broken down: performance Y security.

Performance it involves both WordPress and PHP versions, SQL Server, required or recommended PHP modules, UTF8MB4 support, scheduled events, HTTP requests, REST API, and loopback requests. On your side, security controls active themes and plugins, HTTPs connection, secure communication security, whether debugging mode is disabled, communication with WordPress.org, and status of background updates.

There are three levels of possible improvements, divided into critical issues, recommended actions, and tests completed.

critical issues: is what should focus your attention. Here we will find serious speed and security issues, PHP conflicts, and holes in the site's defense. Of course, always tells you the solution. For example, you are allowed to enable PHP 7.4, imagick, opcache, or any other PHP extensions you need to use.

Recommended enhancements: Shows all the general recommendations to improve the health of the site, providing instructions on how to address them individually.

Tests passed: shows the number of elements that do not require any attention since they are in optimal state.

When all your web is optimal, you will see the following screen:

"Information" tab

The “information” tab shows an assortment of data covering various general aspects. Each category is packed into its own drop-down drawer.

Let's break down the screenshot above by ranking it:

  • WordPress: version, site and user language, start URL, site URL, permalink structure, multisite check, etc.
  • Directories and sizes: directory location, size, upload limit location and size, active theme location and size, plugin location and size, etc.
  • Dependents: dependents are single files that are located in the directory wp-content; they replace or enhance WordPress features in ways not possible with traditional plugins. Ex.: advanced-cache.php
  • active topic: theme name, version, author, author's website, parent theme, theme features, theme location (directory).
  • Inactive Topics: Themes that are installed, taking up space on the server, but are not currently in use.
  • Active plugins: names of all active plugins, versions and author names.
  • Inactive plugins: list of all installed but inactive plugins (they are harmless, but take up space on the server).
  • media management: active editor name, ImageMagick version number, string, resource limits, GD version, Ghostscript version.
  • Server: server architecture, web server, PHP version, time limit, memory limit, maximum input time, maximum upload size, maximum post size, Imagick library status, rules .htaccess and more.
  • Database: extension, server version, client version, database user, host, name and prefix.
  • WordPress constants: ABSPATH, WP_HOME, WP_SITEURL, WP_CONTENT_DIR, WP_PLUGIN_DIR, WP_MAX_MEMORY_LIMIT, WP_DEBUG, WP_DEBUG_DISPLAY, WP_DEBUG_LOG, SCRIPT_DEBUG, WP_CACHE and more.
  • File system permissions: Determines whether or not WordPress is able to write to the directories it needs access to. Examples: WordPress home directory, directory wp-content, upload directories, plugin directory and theme directory.
  • MPA: When your site supports official AMP, all debugging information for the AMP plugin for WordPress will be listed here.

Copying the information

If you need to export the list of all the health information of your WordPress site, simply click the “Copy site information to clipboard” button. Once this is done, you can paste it in a Word file, in an email, in a file in your notepad or wherever you want.

Many times, a technical support technician of a product you use, plugin, component or other, will ask you for this information by mail, so it is good that you know how to reproduce it.

Conclusions

Once again, WordPress shows love for its users and ability to develop native tools that save admins from having to resort to third party plugins. Remember that everything native to WordPress (for example, the comment box in posts, or the Gutenberg editor) will always have 100% compatibility with the rest of the features, as well as being extremely secure.

If until now you have been using a component to check and correct errors in your WordPress, it is time for you to consider removing it from your installation.

As always, if you have any questions about a specific error or warning, feel free to email us at [email protected] because, If your site is hosted on Duplika, we will solve it for you.

You can also leave us a message in our comments; forever we are eager to help our readeris, and we are honored to be able to guide you.

Our greetings, and thanks for reading.

We are Duplika

Give your site the hosting it deserves

,
no comments on WordPress site health

back to blog

Duplika

Duplika

We are online, we are not a bot :)

I will be back soon

Duplika
Hi 👋
Select the prefered contact method to get in touch.
Connect via:
chat