Store Sheriff
No login · No credentials · Nothing leaves your browser

Is anyone actually looking after your store?

Most online stores don’t break on the day they’re built. They rot quietly — a year of skipped updates, a backup nobody ever restored, a checkout that got half a second slower every quarter. Answer 18 questions about your store and find out how much risk has piled up, what it’s plausibly costing you, and what to fix first.

The check

Want some of this filled in for you?

The free store scan looks at your store from the outside — certificate, redirects, platform, leaked version numbers, security headers, compression, server speed — and sends you here with those answers already filled in. Then you only answer the ones that need inside knowledge.

Scan my store first →

Answer what you know. “I don’t know” is a valid answer — and it’s scored honestly, because not knowing the state of your own store is itself a risk. Nothing is sent anywhere; the scoring runs in this page.

1. Software currency

Outdated store software is the single most common reason a working store suddenly stops working. Once a version stops receiving security fixes, every newly published vulnerability stays open on your store permanently.

What does your store run on?
How current is that software?

Not sure which version you are on? SwiftForge’s version checker reads it off a public store page. For what each version still gets fixed, see is your store platform still supported?

Which version of PHP does the server run?

PHP is the language WooCommerce, PrestaShop and Magento are written in. Each version gets security fixes for a fixed window, then nothing, permanently. We keep the full list here: which PHP versions still get security fixes — and which are dead.

When was the store software and its plugins last updated?
2. Can you actually get the store back?

A backup you have never restored is a hypothesis, not a backup. The expensive question is not “do backups exist” but “how many hours of trading would you lose proving it”.

What backups exist?
Has a backup ever been restored successfully?
Is there a staging copy where changes get tested before they go live?
3. Security and access

Stores are attacked by automated scanners, not by people who chose you. Scanners look for known-vulnerable plugin versions and weak admin logins — which is why abandoned plugins and unused admin accounts matter more than most owners expect.

Does the whole store load over HTTPS, with no browser warnings?
Do admin logins require two-factor authentication?
How many people have full admin access?
Are there plugins or themes installed that are inactive, unused, or no longer maintained by their author?
Does anything scan the store for malware or unexpected file changes?
4. Speed on a phone

Most store traffic is mobile, and most store owners judge speed on a desktop with a warm cache — which is the one experience almost none of their customers have. Speed is also the only item on this list that Google uses directly as a ranking signal.

What is your mobile PageSpeed score for the home page?

Takes 30 seconds to find out: Run Google’s test ↗ Opens Google’s own tool in a new tab. We never see the address you type.

How does add-to-cart and checkout feel on a phone, on mobile data?

Checkout can’t be cached the way a product page can, so it’s usually the slowest part of a neglected store — and the part where a slow page costs you an order outright. Background: why checkout is slow.

What kind of hosting is it on?
5. Oversight

The costliest failures are the quiet ones: a payment gateway that stopped working, a checkout that throws an error on one browser, a store that was down all weekend. What matters is how quickly you’d find out.

Would you be told automatically if the store went down?
Who is responsible for the store’s technical health?
When did someone last deliberately test a real purchase end to end?
6. Context (optional)

Used only to put the findings in money terms. Pick a band — this stays in your browser.

Roughly what does the store turn over per month?

0 of 18 answered

This is a self-assessment based on your own answers, not an inspection of your store. It cannot see your code. It is deliberately conservative about what it claims.

How the score works

Five areas, weighted by how much damage each one does when it fails. Within an area every question counts equally, and an “I don’t know” scores as poor rather than neutral — because an unknown you haven’t checked behaves exactly like a problem you haven’t found.

AreaWeightWhy that weight
Software currency25%Unsupported software is the root cause behind most “the store suddenly broke” and nearly all compromises. It also blocks every other fix.
Recoverability20%Determines whether a bad day costs you an afternoon or your business. An untested backup counts for very little.
Security & access20%Abandoned plugins and stale admin accounts are what automated scanners actually find.
Mobile speed20%The only area here that costs you money every single day rather than on the day it fails.
Oversight15%Decides how long any of the above runs unnoticed. Low weight, high multiplier on everything else.

The bands

ScoreBandWhat it usually means
85–100CleanActively maintained. Keep doing what you’re doing, and test a restore.
70–84WatchingFundamentally sound with specific gaps. Usually a few hours of work.
50–69DriftingNothing is on fire but nobody is steering. This is where most stores sit.
30–49NeglectedSeveral compounding problems. Upgrades are now risky because nothing is tested.
0–29Running on luckStill trading, but one plugin update or one bot away from a bad week.

What this is, and who pays for it

Full disclosure. Store Sheriff is built and paid for by SwiftForge Web LLC, an engineering team that rescues and maintains neglected WooCommerce and PrestaShop stores. They have a commercial interest in you discovering that your store needs work. That is exactly why this tool shows you its weightings, its formulas and its caps — so you can check its reasoning rather than take its word.

It exists because the first conversation with a store owner is almost always the same one. The store makes money. It was built years ago by someone who has moved on. Nobody can say what version it runs, when it was last backed up, or whether the backup works. The owner isn’t careless — nobody ever told them what to keep an eye on.

So this is the list. It is free, it needs no email address, and it has no upsell gate: the full result, every finding and every fix is on this page whether or not you ever talk to anyone.

What it does not do

  • It does not inspect your store. It scores your answers. If an answer is wrong, the score is wrong.
  • It is not a security audit or a certification, and it deliberately gives you no badge to display — a self-assessment is not something your customers should be asked to trust.
  • It does not store anything. There is no database, no account, no analytics on this page and no form submission. The scoring is JavaScript running on your own device. Closing the tab erases it. The “copy a link” button encodes your answers into the link itself, so only whoever you send it to can read it.
  • It does not ask for credentials, and you should be suspicious of any free tool that does.

If you only do three things

Most of the value in this list comes from a small number of fixes. In rough order of return:

  1. Restore a backup somewhere that isn’t your live store. Not “check that backups run” — actually restore one. This is free, takes an afternoon, and converts your biggest unknown into a known. Most owners who do this discover something broken.
  2. Get off end-of-life PHP. It is usually a dropdown in your hosting panel, but only after the store is on versions that can handle it — which is the part that needs care. See what end-of-life PHP means for a store.
  3. Delete every plugin and admin account nobody can justify. The cheapest security work there is. Deactivating is not enough — inactive plugin files are still reachable and still exploitable.

After that it stops being a list of tasks and becomes a habit. SwiftForge publish the schedule they actually use as a daily, weekly, monthly and quarterly checklist — worth copying whether you ever hire anyone or not.

Questions people ask

Is this really free, and what’s the catch?

Genuinely free, no email required, full result on the page. The catch, stated plainly: it is built by an agency that sells store repair work, and a low score is good for their business. Judge it on whether the reasoning holds up — the weightings, formulas and caps are all published above.

Does my data go anywhere?

No. There is no form submission, no database, no account and no analytics script on this page. Scoring happens in JavaScript on your device. The address you type for the PageSpeed button is used only to build a link to Google’s own tool and is never sent to us.

How accurate can a questionnaire be?

It is as accurate as your answers, which is its real limitation. It cannot find the things you don’t know about — an abandoned plugin with a known vulnerability, a database that has grown to 40 GB of expired session rows, a cron job that silently died. In practice a questionnaire like this catches the common, expensive problems and misses the specific ones. That’s what reading the actual code is for.

Why does “I don’t know” lower my score?

Because an unverified assumption and a real problem behave identically until the day you need them not to. If nobody can say whether backups work, you do not have working backups — you have a hope. Treating unknowns as neutral would make the score comfortable and useless.

Does it work for Shopify or BigCommerce?

Partly. The hosted platform handles your software versions, PHP and server patching, so those questions stop applying and the score adjusts. Speed, apps, admin access, oversight and the “can you leave” question all still very much apply.

My score is bad. How urgent is it?

Unsupported software plus no tested backup is the combination worth acting on this month, because the fix gets harder and more expensive the longer it waits — the further behind you fall, the more versions you have to jump at once. A slow store is costing you money daily but it is not an emergency. Everything else can be scheduled.

Can I use this with my clients?

Yes. Freelancers and agencies are welcome to run it with store owners, print the result and use it as the basis of a quote — including quotes that compete with SwiftForge’s. Link to it rather than copying it and you’ll always have the current version.