The plugin question, answered category by category
Every plugin is code someone else maintains, running with full access to your database. Click a category — this is where we say yes, where we say no, and why.
Use sparinglyPage builders
They let non-developers move things, which is genuinely valuable. They also ship heavy CSS and JavaScript on every page and lock your content into shortcode soup that is painful to migrate later. We use one where the client truly needs drag-and-drop, and hand-code the templates that matter for speed and SEO.
Verdict: allowed for editable marketing pages, never for the whole site.
YesForms
One well-maintained forms plugin, configured with spam protection, server-side validation and a real delivery path (SMTP, not the server's default mail). Form submissions that silently vanish are the single most common thing we find on inherited sites.
Verdict: one plugin, tested end-to-end, with a copy of every submission stored.
YesSEO
One SEO plugin for titles, descriptions, schema and sitemaps. Two SEO plugins is a classic inherited-site problem: they fight over the same output and produce duplicate tags. We also keep an eye on what it emits rather than trusting the green lights.
Verdict: exactly one, audited against the rendered HTML.
YesCaching & performance
Page cache, asset optimisation and image conversion do more for Core Web Vitals than any theme choice. The risk is aggressive settings that break carts, forms or logged-in views — so every rule gets tested against real user journeys before launch, not just against a score.
Verdict: essential, but configured deliberately and re-checked after every major change.
Yes, but not instead of updatesSecurity
A firewall plugin raises the floor: login limiting, file-change alerts, brute-force blocking. What it cannot do is patch an out-of-date plugin with a published vulnerability. Most WordPress sites that get compromised were not out-hacked, they were simply out-of-date.
Verdict: worth having — and no substitute for the monthly update pass.
Yes, off-siteBackups
A backup stored on the same server as the site is not a backup. We run daily off-site copies of files and database, keep a rolling history, and periodically restore one to a staging environment — because an untested backup is a hope, not a plan.
Verdict: mandatory, off-site, and restore-tested.
Usually noSliders & effect plugins
Heavy, rarely clicked, and a frequent source of layout shift that costs you on Core Web Vitals. Almost everything a slider plugin does can be done with a fraction of the code. We remove more of these than we install.
Verdict: removed unless there is a real, measured reason to keep it.
No“All-in-one” kits
Bundles that promise SEO, security, speed, backup, analytics and social in one install. They overlap with everything else, are hard to remove cleanly, and when one part breaks you cannot swap just that part. They are also how sites end up with three caching layers fighting each other.
Verdict: no. Individual tools that do one job are replaceable.