Plain answers to fair questions.

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.

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.

No. Install, activate, done — the plugin starts working with sensible settings. Everything else is optional. The guides are screenshot walkthroughs of every step.

No. On first open the plugin shows a licence screen, and it isn't obvious that you can walk straight past it — the way through is the grey bar at the bottom: "Don't have a license key? Activate Free Version". Click that and you're in. No card, no email needed.

Then there's one more screen asking whether to share your email for update notices. Skip is a perfectly good answer; that screen says so itself. The install guide has a screenshot of both.

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.

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.

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.

Honest answer: your typical page load barely changes — in our measured run it was about 1ms slower, because the plugin does real work on every request. What improves is the worst case: the unlucky visitor went from 835ms to 62ms. If someone promises you "40% faster," they're measuring something dishonest. Our benchmarks page has the full run, the raw data, and the rows where SwiftQueue comes off worse.

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."

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.

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.

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.

WooCommerce keeps its own, second chore list — that's Action Scheduler. Same idea as WP-Cron, built for stores that create lots of chores. SwiftQueue watches it, tells you when it's clogged with old finished jobs (a common reason store dashboards feel slow), and can ask it to tidy up — always through WooCommerce's own tools, never by poking around in its data directly.

It's designed not to: on a normal page view SwiftQueue does almost nothing — a couple of quick "anything due?" checks — and the heavy lifting happens in the background worker, which is the whole point. But you shouldn't take our word for designed. The benchmarks compare a site running SwiftQueue against an identical site without it, on the same hardware, and publish the typical (not just the flattering) numbers.

If you want the idea first, read the chore list — the simplest page on this site. If you want to just do it, the install guide — every step is a screenshot. Ten minutes, no code.