Service
Performance and caching
Finding out why the site is slow, fixing it, and proving the cache actually clears when content changes.
What you get
- Performance audit with profiling data
- Cache architecture review
- Purge and invalidation verification
- Redis and page-cache configuration
- CDN and edge-cache integration
- Image delivery optimisation
Two different problems get called "the site is slow". One is genuinely slow page building, which profiling finds. The other is caching that is working perfectly and serving stale content, or not working at all because a cache tag is missing — and that one is invisible until an editor complains that their change has not appeared.
We audit both, and we verify invalidation rather than assuming it: a purge that reports success while the CDN keeps serving the old page is the most common caching bug there is.
Questions we get asked
Almost always, and almost always a missing or wrong cache tag somewhere between Drupal and the CDN. It is diagnosable and fixable, and it is worth fixing — editors who do not trust the site work around it in ways that cost far more.