Plain answers to fair questions.
No jargon without an explanation attached. If a question you have isn't here, that's a gap on our side — tell us.
What does SwiftQueue actually do, in one sentence?
It makes WordPress do its background chores — sending emails, backups, publishing scheduled posts — in the background, instead of while one of your visitors waits for a page.
Wait, WordPress makes visitors wait? Really?
Really. Out of the box, WordPress checks its chore list during page loads and works through anything that's due before finishing that page. It's a reasonable design for tiny sites and an odd one for everything else. Most visitors never notice; the unlucky one does.
Do I need to know how to code?
No. Install, activate, done — the plugin starts working with sensible settings. Everything else is optional. The guides are screenshot walkthroughs of every step.
Can it break my site?
It's built not to. The key safety design: if SwiftQueue's background worker can't run for any reason — some hosts block the technique it uses — it hands the chores straight back to WordPress, which does them the normal way. The failure mode is "works like before you installed it," not "chores stop happening." And deactivating the plugin returns WordPress to stock behaviour immediately.
What happens if I uninstall it?
WordPress goes back to exactly how it worked before, and SwiftQueue removes every setting and record it created. No leftovers in your database, no features held hostage.
Is it free?
The core is free and genuinely solves the problem — it's the whole background engine, not a teaser. The paid version adds things stores, agencies and networks need: checkout protection for WooCommerce, priority lanes, alerts, a multisite dashboard. See pricing. If the paid licence ever lapses, the plugin keeps working.
Will it make my site faster?
Honest answer: your typical page load barely changes, because most page loads never collided with a chore in the first place. What improves is the worst case — the visitor who used to arrive at the wrong moment. If someone promises you "40% faster," they're measuring something dishonest. Our benchmarks page explains exactly what we measure and publishes the scenarios where SwiftQueue doesn't help.
What's "WP-Cron"? The plugin mentions it.
It's WordPress's name for the chore system — the scheduler that keeps the to-do list. "Cron" is an old Unix word for things that run on a schedule. Wherever you see it, read "the chores."
My hosting company says they "handle cron." Do I still need this?
Maybe not — and the plugin will tell you. If your host runs a real server schedule, the biggest problem is already solved, and SwiftQueue's checklist detects that (it turns the item green only when it has observed the host's schedule actually working — not when a box is ticked). You'd still gain the dashboard, the Task Inspector, and the failure alerts, but the core pain may already be handled.
Does it work with WooCommerce? Elementor? My contact form plugin?
Yes. SwiftQueue doesn't change how other plugins work — it changes when their scheduled work runs. WooCommerce gets extra, specific support (checkout protection, Action Scheduler visibility). Anything that schedules chores benefits automatically.
My scheduled posts say "missed schedule." Will this fix it?
Very likely, and if not, it will tell you why. Missed schedules happen when nothing triggers the chore list at the right time — quiet sites, or a misconfiguration where the chore system was turned off without a replacement. SwiftQueue detects both cases and gives you the exact fix, with copy-paste instructions for your host.
Where do I start?
The install guide — every step is a screenshot. Ten minutes, no code.