Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsTo audit a WordPress site, create a recoverable baseline, review Tools > Site Health, prioritize findings by their real impact, isolate suspected plugin or theme conflicts safely, and then verify each fix on the site. Site Health is a diagnostic aid—not proof of a specific cause—so confirm that the change actually resolves the problem users encounter.
How do I audit my WordPress site safely?
Start by making sure you can restore the site before changing plugins, themes, updates, or server settings. WordPress recommends regular backups and advises confirming that rollback is possible before enabling automatic plugin and theme updates. See the WordPress guidance on plugin and theme auto-updates.
As an Amazon Associate I earn from qualifying purchases.
- Confirm a recent backup and a workable recovery path. Know how the site can be restored or rolled back; a backup that cannot be restored is not a dependable safety net.
- Record the current state. Note the WordPress, theme, plugin, and server configuration, plus the symptoms users report. This gives you a before-and-after comparison.
- Keep the initial audit read-only. Gather findings before updating or changing settings. If remediation is needed, make one controlled change at a time and record it.
If you cannot confirm backup or rollback readiness, resolve that before making potentially disruptive changes.
Free tools Windows power users keep installed
One-click scans. No signup required.
How do I check WordPress Site Health?
In the dashboard, go to Tools > Site Health. The screen has two useful views: Status groups critical issues, recommended improvements, and passed tests; Info provides technical details about WordPress, themes and plugins, the server, database, constants, and filesystem permissions. You can export the Info data to share with support. The WordPress Site Health documentation explains the screen and its findings.
#1 Best Overall
- Keep track of everything from attendance to test scores
- Spiral bound
- Measures 8-1/2" x 11"
Start with Status
Record each finding and whether it is marked critical, recommended, or passed. Examples of issues the screen may surface include outdated PHP, pending plugin updates, failed loopback requests, background updates that are not working, blocked HTTP requests, exposed debug errors or logs, and filesystem permissions that need attention.
A warning is a lead to investigate, not a diagnosis. For example, a failed check may reflect the site’s hosting or configuration rather than a plugin fault. If a result is described as not verifiable or is otherwise incomplete, record that limitation instead of calling it a confirmed failure.
Use Info for technical context
When a status finding needs more detail—or you are asking a host or developer for help—review the relevant sections in Info and export the report. Filesystem permission issues and other server-level settings may require help from the hosting provider if you do not have the appropriate access.
Recommended Free Tools
How should I prioritize the findings?
For every finding, write down what Site Health detected, where it appears, its likely impact, possible causes to investigate, urgency, the change you propose, and how you will confirm success. Mark what is known separately from what is only a hypothesis.
A useful triage order is:
- Urgent security or availability risks. Address issues that could expose sensitive information or prevent the site from working.
- Broken key user journeys. Prioritize failures affecting essential actions such as logging in, submitting a contact form, checking out, or publishing.
- Update and configuration risks. Investigate outdated software, failed background updates, blocked requests, and related configuration findings.
- Lower-impact improvements. Plan recommended changes that do not currently disrupt security, availability, or essential site tasks.
Site Health’s categories can help seed this order, but your site’s actual behavior and purpose determine the impact.
How do I find which plugin or theme is causing a problem?
If a fault appears tied to a plugin or theme, use the Health Check troubleshooting mode where available. It is designed to let the maintainer test components without changing what normal visitors see. The Learn WordPress conflict-troubleshooting lesson and the Health Check troubleshooting guide describe this approach.
- Enable troubleshooting mode and reproduce the problem on the affected page or workflow.
- Reactivate plugins one at a time, reloading the affected page or repeating the action after each change.
- If the issue persists, test the theme as well, changing one component at a time.
- Note which activation coincides with the problem. Treat that as a strong lead to investigate, not automatic proof: interactions between components or site configuration may also matter.
Before editing files or disabling components directly on a live site, make sure your recovery path is clear. If troubleshooting mode is unavailable, avoid broad changes that could disrupt visitors; arrange a safe testing environment or get help from someone with the required access.
How should I apply a fix?
Make the smallest reversible change that addresses the best-supported cause, and record what changed. Avoid changing several plugins, settings, or server values at once: doing so makes it harder to tell which action helped or caused a new problem.
When the finding involves updates
Check that you can roll back before updating. WordPress notes that plugin and theme automatic updates rely on scheduled WordPress Cron tasks, so investigate whether scheduled updates are working if updates are not being applied. The auto-update documentation covers this dependency.
When the finding involves the server or permissions
Do not change server-level settings without the access and expertise to do so safely. For filesystem permission findings, WordPress specifically advises seeking help from the hosting provider. The host may also be the right contact for PHP, loopback, or request-blocking problems that you cannot diagnose from the dashboard.
How do I check that the fix worked?
After each change, rerun Site Health and review the relevant result. Then repeat the exact page view or action that originally failed; a cleared warning alone does not show that the user-facing problem is fixed.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- For plugin or theme changes, test the affected page and the essential actions it supports.
- For update changes, check that the intended versions are active and that the site still works.
- For loopback or scheduled-update findings, check the relevant behavior again rather than assuming that a general pass confirms every related task.
- For sites that use them, test important journeys such as contact forms, checkout, login, and publishing.
Record the result and any remaining uncertainty. The exact functional checks depend on what your site does; a general Site Health pass cannot substitute for testing its specific user journeys. For additional context on the dashboard tool, see Learn WordPress: Tools—Site Health and WordPress Support: Site Health.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
