Sample WordPress Health Check: Sample Customer

This is a sample

Sample Customer is a made-up business, and everything in this report is fictional. The issues are ones WordPress sites commonly run into, so you can see exactly what our WordPress health check covers and what you get at the end.

πŸ“‹ At a Glance#

ItemDetail
BusinessSample Customer (fictional), a local trades business with 5 staff
WebsiteWordPress with a page-builder theme, a contact form and a quote request form
HostingBudget shared hosting, set up by a former web developer
Plugins31 installed, 24 active
Review dateNovember 2026

Summary#

The site looks good and works, but it is slow on mobile, behind on updates, and at real risk of being hacked. Two plugins have known security problems with fixes available, and one plugin has been abandoned by its author. Quote request emails are unreliable, which may be costing the business enquiries.

Everything we found can be fixed in about 8 hours of work, with no redesign needed.

🚦 Scorecard#

AreaRatingIn one line
SecurityπŸ”΄ Act nowTwo plugins with known vulnerabilities, and an abandoned plugin
UpdatesπŸ”΄ Act nowWordPress core, 17 plugins and the theme are out of date
Form emailπŸ”΄ Act nowQuote requests sent without authentication; some never arrive
Speed🟑 ImproveSlow on mobile: large images and no caching
Backups🟑 ImproveWeekly only, and stored on the same server
Hosting and PHP🟑 ImprovePHP version no longer receives security fixes
Access and accounts🟑 ImproveSix admin accounts, including a former developer and a former staff member
SSL and domain🟒 GoodValid certificate; domain in the business’s own account
SEO basics🟒 GoodPage titles, descriptions and sitemap in place

πŸ” Key Findings#

1. Plugins with known security problems πŸ”΄#

What we found: two active plugins (a slider and a form add-on) are on versions with publicly known vulnerabilities. Fixed versions are available. A third plugin, used for a gallery, hasn’t been updated by its author in over two years.

Why it matters: out-of-date plugins with known holes are a common way small WordPress sites get hacked. Attackers scan for them automatically.

What to do: update both plugins straight away (after a backup), replace the abandoned gallery plugin with a maintained one, and delete the 7 inactive plugins, which can still be attacked even when switched off.

2. Updates are well behind πŸ”΄#

What we found: WordPress core is two minor versions behind, 17 plugins and the theme have updates waiting, and automatic updates are switched off.

Why it matters: updates carry security fixes. Leaving them too long also makes the eventual update bigger and more likely to break something.

What to do: take a full backup, apply updates on a staging copy, check the key pages and forms, then apply them to the live site. Set up a regular, supervised update routine.

3. Quote requests aren’t reliably reaching the inbox πŸ”΄#

What we found: the forms send email straight from the web server, “from” the business’s address, without SPF or DKIM authentication. Test submissions to Gmail and Outlook went to spam or didn’t arrive.

Why it matters: every missed quote request is a missed job, and nobody knows it happened.

What to do: send form email through an authenticated email service, add it to SPF and DKIM, and store a copy of every submission in WordPress as a safety net. See why emails go to spam.

4. The site is slow on phones 🟑#

What we found: the home page loads about 6 MB, mostly full-size photos straight from a camera. There’s no page caching, and the page builder loads scripts on every page.

Why it matters: most local searches happen on phones. Slow pages lose visitors and can hurt search rankings.

What to do: resize and compress images (and convert them to a modern format), turn on caching, put the site behind Cloudflare’s CDN, and stop unused page-builder features loading.

5. Backups wouldn’t survive a hack 🟑#

What we found: backups run weekly and are stored on the same hosting account. No restore has been tested.

Why it matters: if the site or hosting account is compromised, the backups can be lost with it, and up to a week of changes would be gone.

What to do: move to daily backups stored off-site, keep 30 days of history, and test a restore.

6. Outdated PHP and too many admins 🟑#

What we found: the site runs on a PHP version that no longer receives security fixes. There are six administrator accounts, including the former developer and a former staff member, and no login protection.

Why it matters: old PHP versions stop getting security patches. Every unused admin account is another password that could be stolen.

What to do: test the site on a supported PHP version and switch over, remove or downgrade unused accounts, turn on two-factor login for admins, and add login rate-limiting.

⚑ Quick Wins (This Week)#

TaskEffortWho
Full backup, copied off-site30 minutesUs
Update the two vulnerable plugins30 minutesUs
Delete the 7 inactive plugins15 minutesUs
Remove former staff and developer admin accounts15 minutesUs, with the owner’s approval

πŸ—ΊοΈ The Fix Plan#

Now (next 2 weeks)#

  • Vulnerable plugins updated and inactive plugins removed
  • All updates applied via a staging copy
  • Form email authenticated, with submissions also saved in WordPress
  • Daily off-site backups, and a test restore

Next (2 to 6 weeks)#

  • Abandoned gallery plugin replaced
  • PHP upgraded to a supported version
  • Images optimised, caching and Cloudflare CDN switched on
  • Two-factor login for admins and login rate-limiting

Ongoing#

  • Supervised updates every month
  • Uptime monitoring and a monthly security scan
  • A quick plugin review every quarter

🧾 Plugin Register (Extract)#

Every health check includes a full plugin register. Here’s an extract:

PluginPurposeStatusAction
Slider pluginHome page bannerπŸ”΄ Known vulnerabilityUpdate now
Form add-onQuote request formπŸ”΄ Known vulnerabilityUpdate now
Gallery pluginProject photosπŸ”΄ Abandoned by its authorReplace
Page builderPage layouts🟑 Update availableUpdate via staging
SEO pluginTitles and sitemap🟑 Update availableUpdate
Old backup pluginNot in useβšͺ InactiveDelete

What Happens Next#

The report is yours to keep, whatever you decide. You can:

  • Hand it to your own developer to work through.
  • Have us do the fixes through Cloud Experts, as a fixed price or by the hour.
  • Move the site to our WordPress hosting, so updates, backups, security and monitoring are looked after from then on.