> Markdown version of [/events/conference-india-2026/sessions/2067-your-server-rendered](https://www.wearedevelopers.com/events/conference-india-2026/sessions/2067-your-server-rendered). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Your Server-Rendered App Doesn't Know Who It's Talking To


- **Event:** Conference India 2026

## Description

We discovered that 75% of our React SSR traffic wasn't human. Instead of making rendering faster, we changed who gets rendered. This talk shares practical traffic-aware SSR patterns that reduced our Node fleet 8× while keeping pages fast, fresh, and SEO-friendly.
Most SSR architectures make one assumption: every request deserves the same rendering pipeline. In production, that assumption gets expensive. While analyzing our platform, we found only ~25% of incoming traffic behaved like real users — the rest was search crawlers, AI crawlers, and scrapers, all consuming the same SSR resources as humans.
Instead of asking how to render faster, we asked which requests actually deserve server rendering. I'll cover how we classified traffic into humans, search crawlers, AI crawlers, and scrapers; built traffic-aware cache keys; applied different caching strategies per segment; safely bypassed cache for personalized experiences; reduced unnecessary SSR proxy work during client-side navigation; kept long-lived crawler caches fresh via event-driven invalidation; and why vertical CPU scaling beat horizontal pod scaling for this workload.
These changes took our average production footprint from ~400 Node SSR pods to ~50 — cutting infrastructure cost significantly while absorbing rising crawler traffic (including ChatGPT, Claude, Perplexity, and traditional search engines) without increasing origin load. The implementation is a custom React SSR platform, but the principles apply equally to Next.js, Remix, or any server-rendered app.

## Speaker

### [Anshul Bansal](https://www.wearedevelopers.com/@anshul-bansal)

Principal Engineer @ OLX India


## Related talks at this congress

- [Understanding React Performance Patterns Developers Often Get Wrong](https://www.wearedevelopers.com/events/conference-india-2026/sessions/2062-understanding-react) — Himanshu Srivastava
- [React Under Fire: Rendering Performance for Streaming Agent UIs](https://www.wearedevelopers.com/events/conference-india-2026/sessions/1992-react-under-fire) — Abhirupa Mitra
- [The Death of Manual Memoization: High-Performance React 19 for the Scaling Startup](https://www.wearedevelopers.com/events/conference-india-2026/sessions/2025-the-death-of-manual) — Vishnudhasan Govindarajan
- [How We Cut Our API's p99 Latency from Minutes to Under a Second](https://www.wearedevelopers.com/events/conference-india-2026/sessions/1987-how-we-cut-our-api-s) — Deepak Agrawal

## Watch remotely

Can’t make it to Bengaluru? Watch this session live with Pro. You also get:

- All full videos, bookmarks, and playlists
- World Congress livestreams

[See pricing](https://www.wearedevelopers.com/pricing)

## Links

- [Get tickets](https://www.wearedevelopers.com/conference-india/tickets)