Contents
A WordPress audit inventories the site: WordPress and PHP versions, every plugin (useful, up to date, maintained or abandoned), the theme and modified files, accounts, backups and real-world speed. It ends with a clear list of what to update, replace, delete or monitor. In 2025, 91% of new WordPress vulnerabilities were found in plugins.
WordPress is solid when it is looked after. Problems almost always come from what piles up around it: plugins installed “to try”, a theme edited directly, a former provider who kept their access. A WordPress audit puts everything back on the table and says, plugin by plugin, what to keep.
Why plugins are the central issue
According to Patchstack’s annual report (accessed November 17, 2026), 11,334 vulnerabilities were recorded in the WordPress ecosystem in 2025: 91% in plugins, 9% in themes and only 6 in WordPress core. 46% had no patch when they were made public. Risk is therefore managed plugin by plugin.
What the audit checks
| Area | Checks |
|---|---|
| Core | WordPress version, core files modified compared with the official release |
| Plugins | Usefulness, version, last update date, known vulnerabilities, inactive plugins to delete, duplicates |
| Theme | Parent theme up to date, child theme in use, changes made directly in the theme |
| PHP and hosting | A maintained PHP version, server limits, caching |
| Accounts | Admins, roles, former contractors, two-factor authentication |
| Security | Login page, exposed files, headers, security plugins that actually help |
| Backups | Off-server copy, tested restore |
| Speed | Real-world measurements, scripts loaded on every page, images, database |
| Updates | The process: who updates, when, with which backup beforehand |
Each plugin gets a recommendation: keep, update, replace with a maintained alternative, or delete.
A real example: 46 active extensions, 3 modified core files
Before migrating a car club’s forum (phpBB, software that works much like WordPress with its extensions), the audit found 3 core files edited by hand over the years and 46 active extensions, some of them with no version compatible with the target release. After the migration: 29 active extensions, each updated or replaced with a maintained version, and no changes to the core code. The project is described in car club forum. The logic is exactly the same on WordPress.
The most common mistakes
- Editing the parent theme: the next update wipes out the work, so updates stop.
- Keeping deactivated plugins: deactivated, they still sit on the server and can still be exploited.
- Never testing a restore: the backup exists, but nobody knows whether it works.
- Updating without a backup or a check: the update breaks a page and nobody notices for days.
- Stacking caching plugins: two conflicting caches slow the site down instead of speeding it up.
Process and pricing
The WordPress audit runs on a copy of the site or in read-only mode, as part of my technical audit:
- Express audit at $650 (€589)excl. VAT: plugin inventory, priority security points, speed measurement, fix plan.
- Full audit at $2,200 (€1,990)excl. VAT: everything in the table above, a costed action plan, a 2-hour debrief and 30 days of support.
For day-to-day updates and monitoring, I also build tools for agencies that manage many WordPress sites: a secure connector, updates with automatic rollback, backups tested every month (see NooxPress and Le Hub). If speed is the priority, the performance audit page covers the measurements.
Frequently asked questions
How many plugins can a WordPress site have?
There is no maximum. What matters is that each plugin is useful, maintained and up to date. Ten abandoned plugins do more damage than thirty serious, well-maintained ones.
My WordPress site is slow: will the audit find out why?
Yes. The audit measures real-world speed and traces it back to the causes: a heavy theme, a page builder, plugins loading their scripts on every page, unoptimized images, undersized hosting, a cluttered database.
Should I leave WordPress after a bad audit?
Rarely. Most sites recover by cleaning up plugins, updating WordPress and PHP and reviewing the theme. Leaving WordPress is mostly worth discussing when the site has turned into a business application.
My site uses Divi or Elementor: is that a problem?
Not in itself. These builders are maintained. The audit checks their version, their settings and their impact on speed, and flags third-party add-ons, which are not always maintained.