I build websites that don't fall over.
That sounds like a low bar, but for most small businesses on WordPress, Wix, or Squarespace, it's the exact problem they've inherited. The stack they were sold as "easy" quietly became expensive, slow, and a target. When the bots arrive — and they always do — the site they paid for starts fighting back against them.
I move businesses off that stack.
I'm a webmaster who migrates small-to-medium sites from WordPress, Wix, and Squarespace onto headless architecture: Next.js on Vercel, Payload CMS, Postgres on Neon, behind Cloudflare. Once the migration is done, I keep the site secure on a monthly retainer — filtering bot traffic at the edge, tuning the WAF, watching the analytics, and reporting on it in plain English.
The stack is deliberately boring. Next.js because it's stable, Payload because it gives clients an admin panel they can actually use, Cloudflare because edge filtering is the only defence that works before a request hits the server. No experimental frameworks, no proprietary platforms, no lock-in. On handover, the client owns the repository, the Vercel project, and the Cloudflare account.
Most traffic on a modern small-business site is not human. AI crawlers train on the content, scrapers harvest it, vulnerability probes cycle through the install looking for a way in. WordPress, Wix, and Squarespace weren't built to distinguish those requests from a real visitor — they serve everything the same way, on the same shared CPU budget, until the host sends a throttle notice and asks for more money.
The KetoBible.net migration is the proof point. By the end of its WordPress era, roughly 95% of the site's traffic was automated. Ad revenue had gone to zero because the ad impressions were all bots. The host was threatening to throttle the site unless the plan was upgraded. After migrating to a headless stack behind Cloudflare, the bot problem disappeared. The hosting bill dropped to roughly the cost of the domain. Core Web Vitals came out at 100 across the board.
That's the pattern I now offer to clients. The migration is the fix. The retainer is the guarantee it stays fixed.
I take a small number of projects at a time. That's not a marketing line — it's what makes the work good. A migration is a handover, not a hand-off: I audit the existing site, plan the cutover, rebuild the frontend, configure the security layer, and walk the client through the new stack so they understand what they own.
After launch, most clients stay on a retainer. Not because they're locked in, but because it's cheaper and easier than thinking about it themselves. The retainer covers WAF tuning, dependency updates, monitoring, and a monthly report — no log files, no jargon, one message that tells you whether the site is healthy and whether anything needs a decision.
I write about migrations, edge security, and the realities of running a small business site in an era where most of the internet's traffic is automated. That content lives on this blog. It's not a pitch — it's the same thing I'd tell a client across a table, written down so the next person who searches for "why is my WordPress site so slow" finds a straight answer.
If you're running a site that's being hammered by bots, getting throttling notices from your host, or paying for plugins that don't solve the problem — that's the conversation I want to have. Book a call or send me an email.
Next.js, Payload, Postgres, Vercel, Cloudflare. No new database, no experimental runtime, no framework released last month. A deliberate argument for choosing tools that will still be supported in five years.
14 November 2026
Redirects, embedded forms, contact page plugins, and the three SEO risks nobody warns you about. A practical list of what to check before you migrate.
14 November 2026
Wordfence, Sucuri, and iThemes Security all run on your server. By the time they see a request, it's already used your CPU. Here's the difference between filtering at the edge and filtering at the origin.
13 November 2026
A real-world look at what happens when 95% of your website traffic is automated, and why moving to a headless stack was the only permanent fix.
12 November 2026
I build secure, high-performance web apps using Next.js, headless CMS, and edge delivery. View my portfolio to see what we can achieve.