You log into WordPress eager to publish new content, and then this notification on the dashboard stops you in your tracks:
"Your site has critical issues that should be addressed as soon as possible to improve its performance and security."
As you click through to visit your WordPress Site Health page, you're met with a list of errors and optimization tasks that seem to have piled up from nowhere.
It's not exactly what you wanted to deal with today. But here's the thing—ignoring these issues could do more harm than good. They could very well be slowing down your site, leaving it vulnerable to attacks, and hurting your visibility online.
What if you could resolve such errors quickly and easily—or better yet, prevent them from occurring altogether? That would mean your site will continue to be fast, secure, and optimized for users and search engines. Best of all, you'd have fewer unplanned site maintenance tasks to address on short notice, giving you more time to focus on growing your platform.
It's possible to keep your WordPress site in great shape, and in this article, you'll discover exactly how to do it. We'll also show you how to fix your WordPress Site Health status from "should be improved" to "good".
Ready to get started? Let's dive in!
1. What is Site Health in WordPress?
2. What Does WordPress Site Health Check For?
3. How to Check Site Health in WordPress
4. How to Prevent WordPress Site Health Errors
4.1. Choose a Reliable WordPress Hosting Provider
4.4. Delete Inactive Themes & Plugins
4.6. Turn Off WordPress Debug Mode
What is Site Health in WordPress?
Before diving into the nitty-gritty of preventing or solving errors flagged by Site Health in WordPress, it's essential to understand what this built-in tool does.
Essentially, the WordPress Site Health checker helps you keep track of any issues that may negatively affect your site's performance and security.
The status report it generates is also the first thing you will see once logged into the admin panel because the widget appears at the top of your dashboard.
Usually, site health check highlights potential issues by categorizing them into:
- Critical Issues
- Recommended improvements
The recommended improvements are not high-priority. However, they will be beneficial for your site if implemented. On the other hand, the critical issues are like red flags that need your immediate attention.
You should make sure to address both to avoid more problems down the road. Doing so will also go a long way in keeping your site fast, secure, and performing at its best.
Think of it this way—by regularly checking and resolving issues that Site Health brings to your attention, you're not just maintaining your WordPress site. You are also optimizing it for smoother operation and reliability.
What Does WordPress Site Health Check For?
So, what vital signs does site health check to gauge the state of your WordPress site? We now know it focuses on two critical areas—performance and security. Here's a quick rundown of the tests it runs for both categories to keep your site fast, secure, and optimized.
To ensure the best performance, WordPress Site Health check will run tests to see if:
On the security side, the WordPress Site Health tool scans for any vulnerabilities that could expose your website to potential threats. For instance, it will test to see if:
One of the good things about the WordPress health checker is that it runs in the background. That means you don't have to run a scan or initiate anything. And if it detects any vulnerabilities, it'll alert you immediately.
Even so, understanding how to use the Site Health tool effectively is crucial for maintaining your site's optimal condition. With that in mind, we'll dive into what to expect when interacting with its features in the next section.
How to Check Site Health in WordPress
Now that you understand the WordPress Site Health tool and how it works, let's shift gears to using it effectively.
WordPress first introduced Site Health in their version 5.1 release. Since then, this feature has evolved in how it gives feedback.
Initially, users would get a percentage score to gauge their sites' health. However, WordPress replaced the numerical grading in version 5.3 with a more user-friendly approach.
WordPress Site Health now only indicates whether your site is in 'good' shape or 'should be improved'. And, unlike before, where you'd only see a numerical score, you now get actionable recommendations to resolve any issues it detects.
To access the tool, first, log into your WordPress admin dashboard. Next, go to Tools > Site Health. On this page, you’ll find a comprehensive overview of your site’s health status.
The tool divides what you need to know into two main sections as you are about to find out.
1. Status Tab
When you click the Status tab, you'll see a summary of all the tests your site has passed.
This section is also where you will see anything else that requires your attention. After running a scan, WordPress Site Health color-codes the overall state of your site to highlight the urgency of any detected issues. For instance, green indicates "good" health, whereas orange suggests some critical issues detected require immediate attention, which triggers the "should be improved" status.
When you click to expand any flagged issue, you'll get detailed steps explaining how to resolve it. For instance, if you receive a notification your theme is outdated, Site Health will prompt you to install the latest version.
2. Info Tab
On the other hand, the Info tab gives you a deeper look into your site's technical setup. It lists details about your WordPress and PHP versions, filesystem permissions, server environment, database, plugins, and active/inactive themes, to name just a few.
While the Info tab won't alert you to any issues, it will come in handy when diagnosing and checking compatibility issues. It also has a handy export feature that allows you to copy all technical aspects of your site to the clipboard.
Thereafter, you can paste the details into a text file, save it on your device, or email it to your site admin or developer.
That about sums up how to navigate the WordPress Site Health tool. So, what can you do to maintain a "good" status? Let's find out in the next section.
How to Prevent WordPress Site Health Errors
WordPress Site Health check does a great job at identifying and alerting you to anything keeping your website from being secure and operating with optimal settings. But maintaining your site's health isn't just about fixing issues after they arise. It's also about taking proactive steps to prevent them from occurring in the first place.
With that in mind, here are some key strategies you can implement to keep your WordPress site running smoothly and avoid site health errors.
1 Choose a Reliable WordPress Hosting Provider
Where you host your site greatly impacts its performance. That's why choosing the right provider is so important.
Unreliable hosts can make managing your WordPress site harder. They often use outdated software, provide limited resources, and lack proper security measures, leading to slower performance and frequent site errors.
At DTS-NET, we offer WordPress-optimized hosting to keep your site running smoothly. Our plans include all necessary PHP modules and the ability to upgrade to the latest PHP version directly from the control panel.
With us, your site stays fast, secure, and up to date—so you can focus on growing your website worry-free.
2 Encrypt Your Website
The next step to avoid WordPress Site Health errors is to encrypt your site. This measure will prevent hackers from intercepting sensitive user data, such as passwords and personal information.
At DTS-NET, we offer free Let's Encrypt SSL certificates to keep your site secure. Once installed, your website will display a secure HTTPS URL and a padlock icon in the address bar, signaling trust to visitors.
The best part? Encrypting your site not only enhances security, but it will also improve your search engine rankings.
3 Keep Everything Updated
Regular updates are one of the most effective ways to keep your WordPress site running smoothly and securely. However, some users put off applying updates out of fear that they might break their site. In reality, this is rare.
Updates don't just bring new features. They also come with critical security patches and bug fixes that protect your site from emerging threats.
To stay safe, make sure to keep checking for updates. Log into WordPress, then check the side panel menu under 'Dashboard' > 'Updates.' From there, you can update WordPress core, themes, and plugins—all in one place.
Alternatively, you can enable WordPress automatic updates for plugins. While this hands-off approach is convenient, some site owners prefer more control. If that's you, consider turning off automatic updates by adding code to your wp-config.php file or using an update manager plugin.
Pro Tip: You could use the WPCode code snippets plugin to turn off specific WordPress automatic updates. This way, you can update one plugin at a time and monitor its impact on your site without risking its stability. Just remember to back up your site before making any significant updates. When hosting your WordPress site with DTS-NET, Softaculous automated weekly backups give you peace of mind, knowing you can quickly restore it if anything goes wrong.
Besides your core CMS, plugins, and themes, there are other server components you need to keep updated to avoid WordPress Site Health errors. For instance, WordPress uses databases like MySQL or MariaDB to store all your posts, comments, and site files. Using the latest version of either will boost data handling, prevent corruption, and improve site performance.
On the other hand, PHP is the programming language that powers WordPress. Using the latest stable version improves performance, security, and compatibility with new plugin features.
To check the database or PHP version you're using, go to Tools > Site Health page and click the Info Tab. You may be able to update some of these components yourself or need to contact your host to do it for you.
4 Delete Inactive Themes and Plugins
Another way to keep your WordPress Site Health in top shape is to remove any themes and plugins you do not use. You can always reinstall them later if needed, so there's no need to let them linger.
While inactive themes and plugins don't directly affect performance, they can still pose risks. Outdated code in these unused files can make your site vulnerable to security breaches. Plus, leaving them installed unnecessarily takes up space on your server.
To keep your site secure and lean, navigate to Appearance > Themes to delete unused themes. For plugins, go to Plugins > Installed Plugins, deactivate any you don't need, and then delete them.
This routine reduces security risks, shortens security scan times, frees up storage, and makes maintaining your site less confusing and more efficient.
Pro Tip: Minimize the plugins you use. Stick to only what's essential for your site, as every plugin adds extra code that can slow your site and trigger WordPress Site Health errors. Instead, handle tasks manually where possible. For instance, modify the .htaccess file for 301 redirects, use phpMyAdmin to optimize your database, or adjust the wp-config.php file to configure caching and memory limits. These tweaks keep your site lean, fast, and error-free. But if you're unsure about editing these files, consider consulting a professional to keep things running smoothly.
5 Keep REST API Enabled
Some hosting providers disable the WordPress REST API by default to prevent brute force attacks or reduce server load. However, this feature is crucial for your site's functionality.
REST API allows WordPress to communicate with other systems. It enables features like the Block Editor, automated updates, and integrations with mobile apps or third-party services.
Disabling REST API can lead to functionality issues and even trigger WordPress Site Health errors. If it's disabled on your site, you can easily re-enable it by installing a lightweight plugin like 'Disable WP REST API.'
Alternatively, you can enable it manually by adding the following code to your theme's functions.php file:
6 Turn Off WordPress Debug Mode
The next step to maintaining an error-free WordPress Site Health page is disabling debug mode. It helps developers identify issues, but enabling it on a live site can cause problems.
When active, WordPress debug mode will display warnings and error messages even on the front end, which can negatively affect the user experience and give visitors a poor impression of your site.
To disable debug mode, add the following code in your wp-config.php file:
This simple measure ensures error reporting is turned off, keeping your site professional and error-free for visitors.
Pro Tip: If you've used debug mode to troubleshoot issues, ensure to turn it off once you've resolved them. This prevents unnecessary errors and security risks from affecting your site.
7 Ensure Your Cron Jobs Are Active
Finally, make sure cron jobs are running on your WordPress site. They run automatically in the background to handle scheduled events. For example, they handle tasks like publishing scheduled posts, sending emails, and checking updates.
If your cron jobs are not running, you may encounter a WordPress Site Health error stating that 'a scheduled event is late or has failed'.
To ensure cron jobs are working, check your hosting provider's settings. Alternatively, you can use a plugin like WP Crontrol to manage them directly from your WordPress dashboard.
By applying these tips, you can maintain a "good" WordPress Site Health status and ensure a smoother, more secure experience for your site's visitors.
Over to You!
Remember, to improve your WordPress Site Health, it's crucial to stay proactive and address any arising issues.
From updating your site's core, themes, and plugins to ensuring that cron jobs are working, every outlined step is essential in maintaining your WordPress site's optimal performance.
Now that you know what it takes to boost your site health, it's time to implement these strategies and enjoy the benefits. Don't wait for problems to escalate. Take charge of your site's health today and give visitors a more secure and efficient WordPress experience.
FAQs About Common WordPress Site Health Errors
Have you recently encountered a WordPress Site Health error and don't know how to fix it? Below, you will find answers to some of the most frequently asked questions about resolving common Site Health errors.
This error indicates although page caching is active, something is causing your WordPress site to load slowly. Here’s how to fix it:
- Check your caching plugin settings: If you are using a caching plugin, ensure you've configured it correctly and it's clearing caches at suitable intervals. Consult the developer's documentation or guides that offer setup instructions for your plugin. Misconfigured cache settings can cause unnecessary delays.
- Use a CDN: A Content Delivery Network reduces server load by caching and distributing static content globally. If your caching plugin integrates with a CDN, enable it and follow the setup guidelines for optimal performance.
- Optimize images: Large images can significantly slow your page load speed. Some caching plugins, like WP Rocket or W3 Total Cache, allow you to compress photos directly from your WordPress media gallery. Use these tools to lighten server strain and improve load times.
- Test for conflicting plugins or themes: Plugins related to database optimization, security, or performance (e.g., backup plugins) might conflict with your caching plugin. Similarly, custom theme settings, like dynamic elements or poorly coded scripts, can cause interference. Deactivate plugins or temporarily switch to a default theme to identify the issue.
- Upgrade your hosting plan: If these steps don’t resolve the issue, your hosting might not meet your site's needs. Consider switching to VPS or a higher WordPress-optimized hosting plan for faster server response times.
This error indicates that your WordPress site lacks some essential security headers, which help protect against vulnerabilities like cross-site scripting (XSS) and clickjacking. Here's how to fix it:
- Understand the missing headers: Common headers include the Content-Security-Policy, X-Frame-Options, Strict-Transport-Security, and X-Content-Type-Options. You can use an online tool like Security Headers to identify the missing headers by entering your website URL.
- Add headers via server or plugin: You can add missing security headers by modifying your .htaccess file. First, log into your web hosting control panel and navigate to the File Manager. Locate the .htaccess file in your website's root directory (public_html or similar). Download a backup copy, open the .htaccess file for editing, and add the following lines to include the recommended security headers:
- Save the .htaccess file or upload the updated version in the root directory of your server if you are using an FTP client. If you prefer a simple method, consider using a security plugin like HTTP Headers (free) or Really Simple Security (premium) to configure these headers directly within your WordPress dashboard.
- Test your changes: After making updates, reload the WordPress Site Health page or use an online scanner to confirm the headers are now installed.
If you see this error, that means the post_max_size value in your server settings is smaller than the upload_max_filesize, which can prevent larger files from being uploaded to your media gallery. Here's how to fix it:
- Increase the post_max_size value: Log into your hosting control panel and open the php.ini or user.ini file (if available). Look for the post_max_size directive and increase its value to match or exceed the upload_max_filesize value. For example, enter 64M for post_max_size and key in 12M for upload_max_filesize. Save the changes and reload your WordPress Site Health page to confirm the issue has been resolved.
- Modify the values via the .htaccess file: If you don't have access to php.ini, you could try to add the following lines to your .htaccess file:
- Ensure both values are the same or that the post_max_size value is higher. After saving the file, try uploading media again or reload site health page to see if it is still reporting the error.
- Contact your hosting provider: If you're unsure how to make these changes or your hosting environment doesn't allow custom PHP configurations, contact your hosting provider's support team for assistance.
The "301 .htaccess redirect is not enabled" error indicates that your site isn't redirecting to HTTPS in the most efficient way. An easy fix is to use the Really Simple Security – Simple and Performant Security plugin (formerly Really Simple SSL). It will automatically enable a 301 .htaccess redirect.
To use the plugin:
- Install and activate Really Simple Security.
- Go to the plugin's dashboard and navigate to Settings > SSL.
- Ensure the 301 .htaccess redirect option is enabled.
This will automatically add the redirect code to your .htaccess file, ensuring your site redirects to your secure HTTPS URL.
Alternatively, you can edit the .htaccess file manually by following these steps:
- Back up your .htaccess file before making changes.
- Access your .htaccess file via your control panel's file manager or FTP client (e.g. FileZilla).
- Add the following code at the top of your .htaccess file:
- Save the .htaccess file and upload it back to the root directory if using FTP.
- Verify that the redirection is working by testing your site. It should automatically redirect to HTTPS, and you should no longer see the error once you refresh the WordPress Site Health page.
Using Really Simple Security is the simplest way to implement the 301 redirect, but manually editing the .htaccess file is a good option for those who want to keep their site lean and avoid plugins.
Is your WordPress site running at its best?
DTS-NET’s hosting is tailored to optimize your WordPress site’s health. With automated backups, enhanced security, and expert support, you’ll experience worry-free performance and peace of mind. Make the switch today for a smoother, faster WordPress website.
