Hosting, performance, and the tech that holds up under real load.
Most WordPress form plugins store submissions as plaintext. For a clinic site, that is a problem. Here is how I encrypt form data with PHP’s built-in libsodium, and what the encryption actually buys you.
Most clinic sites have a backup. Almost none of them have a backup that would restore at 3 AM on a Sunday when the server is on fire. Here is the gap, and the strategy that closes it.
Self-hosting your fonts saves a few hundred milliseconds on LCP and drops a third-party dependency in the process. Here is how to do it, plus a few other small Core Web Vitals wins that add up.
WordPress is great at request-response. It is worse at long-running background work. Here is when adding a small Go service alongside PHP makes sense for a small business, and when it does not.
Stale content at 9 PM is almost always a cache problem. Here is how the five layers of cache between database and browser actually work, and what to configure so the front desk stops calling.
Every WordPress install hits a wall around month 18. Plugins drift, PHP versions move, and the staff who set it up has changed jobs. Here is what that looks like, and what to do before it costs you a Saturday.
The clinic was paying $11 a month for hosting and losing more than that every week in front desk time. Here is the honest framework: shared vs managed vs VPS, and when each is right.
The PageSpeed Insights score is a proxy. Chasing it chases a moving target. Here is what to actually optimize on a clinic site, in the order that moves the metrics that matter.