Stax

Every Microstax project and monthly plan comes with its own Stax workspace.

Take the tour

Case study · e-architect.com

The slow site wasn't the image. It was one header.

e-architect.com is an architecture publication with a deep archive and heavy traffic, and it was failing Core Web Vitals. Everyone suspected the hero image. The real cause was a cache header that stopped every page from being cached.

  • WordPress on Cloudflare
  • Speed fix, then ongoing care
  • Client agreed to be named

One publication, one root cause, one fix at the source

Core Web VitalsTime to first byteCache-ControlCloudflareCloudflare APOWordPressEdge cachingDeep archiveHeavy trafficRoot cause first
0.35sserver response, down from 0.865s
2.5×faster time to first byte
0%of pages cached before the fix
1headerbehind the whole problem

How it was found

The obvious suspect, then the real one.

  1. 01

    The symptom

    A busy architecture publication, with a deep archive and heavy traffic, failing Core Web Vitals.

    Failing Core Web Vitals
  2. 02

    The obvious suspect

    The hero image looked guilty. It's the first thing anyone would optimize, and it wasn't the problem.

    Ruled out
  3. 03

    The real cause

    Every response was marked no-store, so nothing was being cached at all. Every visit made the server build the page again.

    Root cause found
  4. 04

    The fix

    Corrected at the source, so pages could finally be cached.

    Fixed at the source
  5. 05

    Then APO on top

    Cloudflare APO now serves cached pages from its edge, close to each reader, so requests no longer wait on the server.

    Served from the edge

What we changed

Fixed at the cause, not around it.

No plugin pile, no image tweaks.

  • Traced the slow responses to the cache header, not the image
  • Corrected the header at the source, so pages can be cached
  • Switched on Cloudflare APO to serve pages from the edge
  • Measured time to first byte before and after
  • Kept on a care plan, so it stays fast
See Speed and SEO

The result

Less than half the wait, on every page.

Time to first byte

Before0.865s

After0.35s

2.5× faster to first byteThe server stops rebuilding pages that haven't changed.
Cached at the edgeCloudflare APO answers readers from a location near them.
Still looked afterAn ongoing care plan keeps it from quietly slipping back.

Microstax took on e-architect, a site that runs to more than 49,000 pages, and sorted out problems that had built up over years. They made it noticeably faster, cleared a long backlog of technical SEO issues, and have kept everything running smoothly since. They're responsive, reliable, and clearly know their way around large WordPress sites. Happy to recommend them.

Adrian WelchFounder, e-architect.com

Adrian has agreed to take a call if you'd like to ask him about the work.

Ask for an introduction

Find what's really slowing your site.

Send the URL. You'll get a written reply the same day and a fixed price within 24 hours.