HOSTING TIPS ARCHIVE
Monitoring: 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.
14 guides, newest work first.
One WordPress command centre that every plugin reports to
A WordPress command centre where every plugin contributes one card, and every card says where its figures came from and when they were true.
Cron locks stop overlapping runs. Make sure they do not hide skipped ones
Per-site flock locks stop scheduled WordPress runs stacking up. Why I removed a shared lock, and how a background lease skipped thousands of runs unnoticed.
Audit the tipping record before anyone sees the headline number
A tipping record's profit figure looked good. A settlement audit found tips matched to the wrong race. What went wrong, and why waiting is an honest state.
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.
The data behind data-led design
Source health, content freshness, honest forecasts and separate site boundaries: the backend decisions that make data-driven maps, campaigns and creative useful.
An AWS bill review that leads to useful decisions
Review an AWS bill using a complete-month baseline, resource owners and practical checks. Separate estimated savings from changes that are safe to make.
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.
Diagnose Linux bottlenecks before changing settings
Use a small repeatable baseline to distinguish CPU work, memory pressure, storage waits and application queues before tuning a Linux web server.
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.
Ten Linux server habits: disk, logs, updates, SSH and timers
Simple, repeatable checks for anyone running a Linux server: what is listening, what is filling the disk, automatic security updates, SSH keys, systemd timers and more.
Show what your monitoring has actually checked
Make the scope, age and missing evidence visible in a hosting status summary, so a reassuring label has something useful behind it.
Check the Apache configuration that is actually loaded
Before changing an Apache limit, I trace the running service to the configuration it reads. A plausible file in the right directory can still be inactive.
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.