Headless architecture, performance, infrastructure
Making a newsroom fast without making it expensive
Led the technical rebuild of a high-traffic news site onto headless SvelteKit.
The problem
A monolithic WordPress site was serving a high-traffic news audience. Pages were slow to first byte, and every traffic spike landed on the same server that editors used to publish.
What I did
- WordPress becomes a headless CMS behind GraphQL; SvelteKit renders the reader-facing site.
- Incremental Static Regeneration regenerates only the pages that change.
- Edge caching absorbs reads so the origin mostly handles publishing.
- Redis for caching, Meilisearch for search, Garage for self-hosted S3 media storage.
What changed
- Substantially lower TTFB and faster page loads.
- Publishing and reading traffic no longer compete for the same resources.