BetterShield
Appearance
HardeningSecurity auditSettings

Does a WordPress security plugin slow your site? BetterShield’s cost

· · 8 min read

A WordPress security plugin adds some work to a visitor’s page view, and BetterShield keeps that work small and measures it. It runs only the fixes you turned on, its sign-in protection and a few form limits for visitors, while audits, file checks and emails never run inside a page view.

You do not have to take that on trust. The BetterShield › Overview screen shows the cost for your own site once it has seen enough visits. This post covers what BetterShield does in a page view, how to read the figure, and how to keep a hardened site fast. If you are still choosing a plugin, our guide to choosing a WordPress security plugin comes first.

Quick summary

  • BetterShield samples one visitor page view in 20 and reports the time and work its own visitor-facing code adds.
  • For visitors it runs the fixes you turned on, sign-in protection, limits on the comment, reset and sign-up forms, the opt-in missing-page limit and a hidden bot check on three forms.
  • Audits, file checks and emails never run inside a visitor’s page view.
  • On the WooCommerce cart and checkout it adds no bot check, skips its sampling, checks and housekeeping, and only records security events.
  • The figure covers BetterShield alone. It is not a full site-speed test, so use a separate tool for total page performance.

Why the question is fair

Every plugin that touches a request costs something. A security plugin is no exception, and the honest answer to “does it slow my site?” is “by how much, and where?”. No single number settles it for every site: the cost depends on which protections you switched on and how much traffic you get.

What BetterShield can do is tell you what it adds on your site, and keep its work out of the places where visitors wait. That is the whole approach: nothing slow in the page view, and a measurement you can read for yourself.

What BetterShield runs for a visitor

The plugin’s own answer is specific about what happens while a visitor loads a page. Four things can run:

  1. The fixes you turned on. A fix you enabled under Protection does its job on the request it applies to. A fix you left off does nothing.
  2. Sign-in protection. The sign-in pauses described in our guide to sign-in lockouts run when someone signs in.
  3. Limits on the comment, reset and sign-up forms. They apply when someone submits one of those forms.
  4. A hidden bot check on the sign-in, registration and comment forms. It adds a field people never see and a signed timestamp, needs no JavaScript and no outside service. The details are in the hidden bot check doc.

There is also an opt-in limit on missing pages. It is off until you choose it.

What does not run in a page view is just as important. Audits, file checks and emails are scheduled or started by you, never by a visitor’s request. So a visitor reading a blog post is not waiting for BetterShield to scan files or send a message.

WooCommerce carts and checkouts

A store has pages where speed matters more than anywhere else. On the WooCommerce cart and checkout, BetterShield adds no bot check, skips its own sampling, checks and housekeeping, and only records security events. Because the bot check is never added to checkout, a customer paying for an order meets no extra field and no extra wait from it.

How to read the cost on your own site

BetterShield’s measurement is built in, and you do not switch it on.

Read the figure

  1. Leave the site running with its normal traffic so samples can collect.
  2. Open BetterShield › Overview.
  3. Find the card that shows BetterShield’s effect on page speed. It appears after enough visitor samples are available.
  4. Read the result and the sample context beside it.

A site with little traffic may not show a figure straight away, and that is expected rather than a fault. The doc for this card is How to measure visitor performance cost.

What the figure measures

It includesIt does not include
The time and work from BetterShield’s own visitor-facing codeWork added by other plugins
One page view in 20, sampledYour theme
Your hosting and the network

That limit is deliberate. A full speed test measures the whole page, and many things beyond BetterShield shape the result. Use the Overview card for BetterShield’s part and a separate performance tool for the page. Google’s guide to the Core Web Vitals describes the page-level measures such a tool reports.

Keep a hardened site fast

A security setup and a fast site do not pull against each other, but a few habits help.

  • Check the figure after a change. Compare it over time, and look again after you change a protection that runs on visitor requests. We recommend this over guessing which setting cost what.
  • Turn on only what you need. Each fix you enable runs where it applies. Our WordPress security plugin setup guide covers the first ones, and a security audit shows which findings are worth fixing first.
  • Keep sign-in pages out of caches. The Sign-in page cache protection fix is under BetterShield › Protection › Hardening and is off by default. It tells caching plugins, server caches and CDNs not to keep a copy of the sign-in page, and no files change. The sign-in page caching doc walks through its preview, and a cache that ignores the instruction still needs a sign-in exclusion in its own settings.
  • Set cache rules in your cache. If you use a page cache, its own rules decide what it keeps. Our sister plugin xSpeed has cache rules and bypass settings for exactly that.
  • Behind a CDN or proxy, check how addresses are read. Our post on the real visitor IP behind a proxy explains how BetterShield sees a visitor’s address there.

What it can break, and how to undo it

Sampling only measures. It does not change caching or page output, so there is nothing to undo. The Sign-in page cache protection fix is the one change in this post: turn it off to use its undo, then check the original workflow. A change is recorded in the activity log, and an undo does not erase that record.

Check it is working

After traffic supplies enough samples, the card on BetterShield › Overview should show a result and its sample context. For the cache fix, the row should show it is on. Test the affected sign-in with an appropriate account, then check the finding. The score and Findings update on their own after the change, and Check Again shows what the check still sees if a finding stays open.

We recommend leaving the measurement as it is, since it needs no switch, and reading it after any change to a protection that runs on visitor requests. We recommend keeping a working recovery method before you change anything that affects sign-in. Our advice is to enable the sign-in page cache fix on a staging copy first if your site has a page cache.

Frequently asked questions

Does BetterShield slow down my site?

It adds the work of the fixes you turned on, its sign-in protection, the form limits and a hidden bot check on three forms. Its audits, file checks and emails never run inside a visitor’s page view. The Overview measures the cost for your own site and shows it once enough samples exist.

How does BetterShield measure its own speed cost?

It samples one visitor page view in 20 and reports the time and work from its own visitor-facing code. No switch is needed. A site with low traffic may take a while before the figure appears.

Does the figure include my theme and other plugins?

No. It measures only what BetterShield’s own code adds. Other plugins, your theme, hosting and the network are outside it, so use a separate performance tool for the whole page.

Does BetterShield affect the WooCommerce checkout?

On the WooCommerce cart and checkout, BetterShield adds no bot check, skips its sampling, checks and housekeeping, and only records security events. The checkout path stays free of its extra work.

Should I cache the sign-in page?

No. Sign-in page cache protection under Protection › Hardening tells caches and CDNs not to keep a copy of it. It is off by default, so turn it on after reading its preview.

Conclusion

A security plugin does add work to a page view, and the useful questions are how much and where. BetterShield keeps its audits, file checks and emails out of the page view, leaves the WooCommerce checkout alone, and shows the cost for your own site on the Overview. BetterShield is free on WordPress.org; the full walkthrough is in the visitor performance cost doc.

Close the open doors today

Install the free plugin. The first audit runs when you activate it, and all but one of the fixes wait for your choice.

Requires WordPress 6.7 or newer and PHP 8.0 or newer.

Get BetterShield