Your prompt

Audit every plugin on my site: what it does, when it was last updated, and whether it slows the front end. Recommend which to keep, replace or remove.

What this prompt does

This prompt has your assistant go through every installed plugin, describe its purpose, note when it was last updated and judge whether it affects front-end speed. It finishes with a keep, replace or remove recommendation for each.

Many sites carry plugins nobody remembers installing. A written inventory is the first step in cleaning that up, and it often turns up duplicates and abandoned tools.

Pay attention to the last updated date. A plugin that has not been updated for a long time is not automatically broken, but it deserves a closer look, especially if it handles forms, logins or payments.

Before you run it

Auditing is safe. Acting on the audit is not, so keep the two steps separate.

  • Ask for the report before any deactivation.
  • Take a backup before you remove anything.
  • Test removals on staging, since some plugins leave content or shortcodes behind.
  • Make sure inactive plugins are included in the review.
  • Check whether any plugin is a must-use plugin or is managed by your host, since those cannot be removed from the normal plugins screen.
  • Keep a note of which plugins are tied to a licence key, so you do not lose access by deleting one.

What to check afterwards

  • Compare the list with your plugins screen.
  • Check that nothing marked for removal is still used by a page, form or shortcode.
  • Look up the last update date on each plugin’s page.
  • Test the front end after every removal.
  • Keep a list of everything removed so you can reverse it quickly.
  • Ask for the full list in a table you can sort, then walk through it with whoever else uses the site.

Ways to adapt it

  • Add security: Also flag plugins with known vulnerabilities.
  • Group the output: Group the list by the job each plugin does.
  • Narrow the job: Only audit my inactive plugins.
  • Add usage: Tell me which plugins no page, form or widget seems to use.

If it goes wrong

  • Removing a plugin breaks a page. Restore the plugin from backup or reinstall it, then find what used it.
  • The speed claims feel guessed. Ask how it measured, or run a before and after test yourself.
  • Two plugins do the same thing. Pick one and migrate its settings before removing the other.

For more background, read our guide to plugins you can delete and plugin conflict troubleshooting.

← Every prompt on WPMusk

SponsoredNibWP

Stop clicking. Start telling.

Ask your AI to build pages, fix speed and nail SEO, and NibWP does it on your WordPress site in minutes.

Try NibWP.com

Get the WPMusk Sunday brief

One email a week with our newest tutorials, honest tool reviews and resources you won’t find on the blog. No spam, unsubscribe in one click.

Newsletter (Sunday brief)