Case study: Enterprise publishing

Speeding up Are Media's high-traffic, multi-brand publishing platform

Are Media's high-traffic, multi-brand publishing platform was slowing down under editorial load and years of accumulated code.

The situation

Are Media ran several brands and business units on one WordPress Multisite platform. Years of features, brand-specific changes and tight deadlines had left a codebase that was slow to change and slow to load, especially at peak editorial times.

Editors on different brands worked in different ways, and the platform reflected that: similar features were built several times, each slightly different.

What was breaking

The symptoms were visible to readers and to the newsroom:

  • Slow pages and admin screens when editorial activity peaked
  • Database queries that grew heavier as the content archive grew
  • Duplicate components per brand, so every fix had to be made several times
  • A team wary of touching older code because changes had side effects

What I did

As architecture lead at Are Media in 2024, I ran the architecture and performance work. We started with measurement: deep analysis of the database queries behind the slowest pages and screens, then optimising them rather than guessing.

To stop the duplication, I designed a scalable Gutenberg component system for editors, so every brand shared one set of well-tested building blocks and differed only where it genuinely needed to.

Finally, code quality standards and a structured refactoring programme: structured reviews, a ranked list of the riskiest code, and improvements made a piece at a time alongside normal feature work. Product, editorial and infrastructure teams agreed the priorities together, so technical work stayed tied to business outcomes.

The result

Faster response times, a consistent editorial workflow across brands, and a platform the team could keep modernising.

  • Faster response times for readers and editors
  • One consistent editorial workflow across brands
  • Fixes made once instead of once per brand
  • A platform the team could keep modernising without a big rewrite

What other teams can take from this

  • Measure before optimising: a few queries usually cause most of the slowness.
  • Shared components are an architecture decision, not just a design one.
  • Refactoring works best as a steady programme next to feature work, not a separate project.

Services behind this work

Architecture Clarity Sprint

4 to 6 weeks, fixed scope

An architecture review and technical debt assessment: a clear picture of what your system supports today, where it will break next, and what to fix first. The best place to start, and the groundwork any future CTO will need.

  • Map of your current system and its real constraints
  • Risk list ranked by business impact
  • Scale roadmap for the next 12 to 18 months
  • A prioritised plan your team can act on
Architecture Clarity Sprint: details

MVP to Production Rescue

Project based

For products that proved the idea but cannot carry the growth. I turn the MVP into a system that is safe to build on.

  • Re-architecture of the weak parts, not a rewrite
  • CI/CD, release standards and observability
  • Database and performance tuning
  • Cloud cost reduction on AWS and GCP
MVP to Production Rescue: details

Tell me what is breaking.

I will tell you honestly whether I can fix it.