HOSTING TIPS ARCHIVE
Caching: 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.
8 guides, newest work first.
Turning live sports data into pages people and search engines can use
Odds, a multi-source sports calendar, a map and racing results as server-rendered pages with ages on every value, one address per view and one canonical tag.
Give every Redis key a lifetime, even when the code asks for a week
Ace Redis Cache now caps every object cache lifetime so cold keys stop crowding shared Redis, and why values over 64 KB were never being stored.
Cache the page, not the reader: a Redis page cache on a busy news site
Nothing per-reader in cached HTML, time windows in cache keys, and a newsroom-aware most popular list that stays live inside a cached page.
Moving assets to a CDN? Keep your Web Workers at home
A 302 from /assets/ to a media host silently breaks Web Workers. Spot it in the console and with curl, keep worker files on the origin and purge the CDN.
Warm every cache variant you actually serve
A deployment can refresh the desktop page while a phone still receives an older cached copy. I make the warmer follow the same choices as real requests.
The first add to basket is a cache test
I test the moment an anonymous browser becomes a shopper with a basket. A fast cached product page does not prove that transition works.
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.
Stock changes need their own cache invalidation
An order can change what a shop should display without anyone pressing Update on the product. I make the cache listen to those changes too.
No guides match those filters. Try another topic or reset the filters.