HOSTING TIPS ARCHIVE
WordPress: hosting guides
Practical steps and checks for hosting, WordPress and performance. Browse a topic or use the dates to explore the experience behind the advice.
24 guides, newest work first.
PHP 8.6 for WordPress: compatibility checks
What I check before moving WordPress to PHP 8.6: plugin and extension compatibility, Redis formats, OPcache memory, background jobs and a tested rollback.
Audit a WordPress network before every deploy, and after
A read-only WordPress multisite audit before and after each deploy: what it checks, what its first run found, and the two checks that were wrong.
MCP: from an AI prototype to a managed website
How MCP connects AI-assisted work to hosting, servers, WordPress and static builds, with ChatGPT Sites, Claude Artifacts and clear access boundaries.
How to contribute to WordPress and write a better plugin
A practical guide to WordPress and open source contributions: reproduce bugs, test patches, review well and build plugins people can install and trust.
Check-then-set is a race: atomic locks in WordPress
Get-then-set locks, dedupe and balances break under concurrency. Fix them with SET NX, wp_cache_add, GET_LOCK or a ledger, and test with parallel wp eval-file runs.
Get more from Cloudflare without making WordPress fragile
A practical Cloudflare setup for WordPress: cache boundaries, Turnstile, analytics, Varnish, Redis and honest measurements from TalkFuse and Sheffield Events.
What a WordPress login lockout should actually do
Eight checks for a WordPress login lockout: count per account and per address, see the real IP behind Cloudflare, never reveal usernames, and never lock out the owner.
Keep PHP up to date and why it matters
PHP fixes only protect you once the PHP actually serving your site is running them. Here is how I keep that under control.
Test WordPress forms through to email delivery
Check the whole enquiry journey, from validation and confirmation to the right inbox, so a working form does not hide a broken handover.
Serve photography galleries without heavy downloads
Keep photographs clear while reducing unnecessary downloads, with sensible image sizes, loading priorities and a recoverable publishing process.
Check hosting and tracking before rewriting falling content
Work out whether falling traffic points to a content problem, a broken page or missing measurement before you change your articles.
Self-hosted WordPress: eight WP-CLI checks for speed and safety
Eight practical checks for WordPress on your own server: verify core files, run cron properly, find autoload bloat, lock down editing, use an object cache and update with a way back.
Running Varnish in front of a Redis page cache, without stale pages
Varnish and a Redis page cache can make WordPress very fast together, but only if they purge as one. The VCL and purge rules that keep both caches honest.
Move WordPress media off your server safely, then review its size
Plan WordPress media offload without broken images or exposed private files. Include CDN and backup costs, then measure before reducing server capacity.
Caching a WordPress block means keeping more than its HTML
A block can register scripts, styles and interactive state while it renders. I need those effects back on a cache hit too.
Atomic deploys with automatic rollback for PHP and WordPress
Release folders, a symlink swap that is truly atomic, rollback when a post-deploy step fails, and the OPcache and permission traps that catch people out.
Deployment configuration needs one clear owner
Define which source owns each deployment configuration file, then test that old local copies cannot silently override an intended change.
Cron, wp-admin and the front end need to agree where temporary data lives
A site can have a persistent object cache and still repeat the same remote calls if some request types quietly keep transients only in memory.
Move large cache clears into a background queue
Clear large caches in bounded batches, keep the admin request short and show whether the job has finished.
Test the oldest PHP version your site actually runs
A clean local lint is useful, but I also check the runtime that receives the deployment.
A shared Redis service needs boundaries for clearing as well as storing
I make a site’s cache clear stay inside that site. Prefixing writes is only half of the job.
PHP in the browser and PHP in cron must agree on the cache
The same cache key is not enough. Every process that reads it has to understand the value written underneath it.
Keep a rollback route when moving PHP
I move the web server onto a separately tested PHP runtime, keep a clear route back, and check cron and background work as part of the change.
Check that scheduled WordPress jobs actually finish
Moving WordPress cron to a server timer can make the trigger more dependable. I still check the queue, the job’s progress and the result people see.
No guides match those filters. Try another topic or reset the filters.