A Tale of Two Sites: SSR Delivers 4.5× More Traffic Growth YoY

◆ The Mission

A major e-commerce retailer operating several child brands was dealing with slow, inconsistent site performance across their portfolio — hurting both user experience and organic visibility. A platform migration was on the horizon, and the window to act was narrow.

The team identified Server-Side Rendering (SSR) as the most defensible architecture going into the transition. The question was whether to move fast or wait for the platform rollout.

---

◆ The Setup

Heading into 2024, one child brand implemented an SSR solution ahead of the broader platform change. The remaining brands stayed on legacy architecture and held for a planned SPA/MWP rollout in late Q2.

This wasn't designed as an experiment — but it became one.

---

◆ The Catalyst

When the SPA/MWP rollout launched in June, most child brands experienced significant performance disruptions. Crawlability issues, slower rendering, and Core Web Vitals regressions compounded during a critical traffic period.

The exception: the brand already running SSR. It absorbed the platform transition without the same degradation — its traffic trajectory stayed intact while sister sites fell.

---

◆ The Divergence

The YoY traffic chart told the story clearly.

The SSR site maintained positive growth through the SPA rollout and held its trajectory through the rest of the year. The non-SSR sites experienced sharp YoY declines following June — dipping as far as -40% YoY during the disruption window.

The SSR site grew 4.5× faster year-over-year than its sister site on the same CMS — the only meaningful variable being rendering architecture.

By late November, a second child brand adopted SSR to stabilize performance following ongoing MWP disruptions. It saw comparable recovery.

---

◆ DAC's Role

This wasn't a passive observation. The team was embedded in the decision-making process throughout:

• Identified SSR as the most effective mitigation path ahead of the MWP rollout — before the risks materialized
• Prioritized the brand most at risk and guided the early SSR implementation timeline
• Monitored cross-brand performance to isolate MWP-related issues from SSR stability, creating a clear attribution model
• Supported a second brand's rapid migration to SSR to offset MWP performance failures mid-cycle

---

◆ The Takeaway

Architecture decisions made months before a platform migration determine whether a site weathers it — or gets buried by it.

This case study is a direct proof point for pre-emptive technical SEO: the work that protects organic performance isn't always visible until something goes wrong for everyone else. SSR wasn't a reaction to the platform failure — it was the reason one brand didn't experience one.

The controlled nature of the outcome — same CMS, same platform rollout, same time period, different architecture — makes this one of the cleaner performance attribution cases in the portfolio.