Free 20-point conversion & SEO audit for export stores — Free website audit — claim yours

hello@woo.one Mon–Fri · 9:00–18:00 (UTC+8)

Choosing Plugins: Six Checks Before You Install

Maintenance signals, page cost, lock-in and the commercial questions. Plus when custom code is the lower-risk choice, and why an inventory matters more than a review.

Most plugin problems are not discovered by reading reviews. They are discovered eleven months later, when the plugin stops being maintained and the store cannot update WordPress without breaking something.

This is the evaluation we run before installing anything, and it takes about ten minutes per plugin.

Criterion 1: is it maintained, really

Signals that matter, in order:

  • Last update date — under six months is healthy; over a year is a warning; over two years is abandoned
  • “Tested up to” — should match or be within one major version of current WordPress
  • Support threads — unanswered threads about critical issues are worse than no support at all
  • Changelog quality — regular releases with real notes indicate active development; “minor fixes” every release indicates none

A plugin with 100,000 installs and no update in two years is riskier than one with 2,000 installs updated last month.

Criterion 2: who maintains it

Three categories, with different risk profiles:

Company-backed — a business whose revenue depends on it. Stable, but be aware of what the monetisation is: upgrades, a service, or your data.

Small team or solo developer — often excellent, sometimes fragile. The question is what happens if they stop. Check whether they have other active plugins, whether they respond in support, and whether the code is on a public repository.

Abandoned — no updates, no responses, often acquired by someone selling “premium support”. Avoid, even if it currently works.

Criterion 3: what it does to the page

Functionality is easy to assess; cost is not. Before installing, check:

  • Does it load assets on every page, or only where used?
  • Does it register AJAX handlers that fire for anonymous visitors?
  • Does it run cron jobs, and at what interval?
  • Does it add database tables, and does it clean them up on uninstall?

A plugin that loads 200KB of CSS on every page to render one element is a permanent tax on every visitor. Five of those is a slow store that no caching plugin fixes — see the plugin performance notes.

Criterion 4: does it lock you in

The test: if this plugin disappeared tomorrow, how much work would it be to move on?

  • Data in its own tables, exportable — manageable
  • Data in post meta with a documented structure — manageable
  • Data only readable through the plugin’s own UI — lock-in, and a business risk
  • Page content stored in shortcodes that render nothing without the plugin — serious lock-in, and common with page builders

The last case deserves attention. A store whose product pages are built with a page builder that stops being maintained has a rewrite project, not a migration. Before adopting a builder, ask what happens if it is abandoned with 5,000 pages already built on it.

Criterion 5: does it belong in a plugin at all

Some things are better as 40 lines of code in a child theme than as a plugin:

  • A small display tweak
  • A custom field on the checkout
  • Disabling a feature you do not use
  • A shortcode for one block of content

Every plugin is a dependency with an update path you do not control. For small, stable changes, custom code is lower risk — and it does not need to be maintained against someone else’s release cycle.

The inverse is also true: do not build a custom payment integration or a custom tax engine. Those are exactly the problems where maintained software wins.

Criterion 6: the viability questions for commercial plugins

For paid plugins, four questions:

  1. What is the renewal price, and does the licence stop working if you do not renew?
  2. Does the licence cover staging and production, or one site?
  3. Is there a lifetime option, and what does “lifetime” mean in their terms?
  4. If the company is acquired, what happens to existing licences?

The second and fourth are where stores get surprised. A licence that silently deactivates on a staging copy can block a deployment at the worst moment.

The install process that prevents problems

  1. Check maintenance signals
  2. Install on staging, not production
  3. Test the specific feature, plus three unrelated pages
  4. Measure page weight and query count before and after
  5. Check for conflicts with existing plugins doing something adjacent
  6. Write down what it does and why it is there

The last step is the one nobody does, and it is why stores end up with 40 plugins where nobody can explain the purpose of eight of them. A one-line note in a maintenance document — “installed for X, replaces Y, owner Z” — makes the next audit possible.

The inventory nobody keeps

If you inherited a store, the first useful artefact is not a performance report. It is a list: every plugin, what it does, when it was last updated, whether the licence is active, and who decided it was needed.

Building that list takes an afternoon and answers most of the questions a new developer, an auditor or a buyer would ask. It is also the basis for deciding what to remove — and removal is usually the highest-value change available on an over-plugged store.

We build this inventory as the first step of maintenance, because everything else — updates, security, performance — depends on knowing what is actually installed.

S

Infrastructure and security engineer at woo.one, based in Foshan, China. Works on WordPress, WooCommerce and OpenCart systems, self-hosted mail, and the operational side of running stores for exporters.

More about the team

No pressure · No sales script

Ready for a store that sells while you sleep?

Send us your current site or product list. You will receive a fixed-scope proposal, a 20-point audit and a realistic timeline within two business days.

Reply within 1 business day NDA on request 100% code ownership
Chat with us
WhatsApp Get a quote