ComposableStack.AI CDP
Back to agent
Latency Tierlatency-tier.intra-page

Intra-page (< 100 ms)

Decisioning happens entirely inside the browser/app context with no network round-trip; data is already local (IndexedDB, OPFS, WASM, in-memory).

confidence 90%v1reviewed Apr 26, 2026latency, client-side, browser

Intra-page (< 100 ms)

Example. A user clicks a Banner asking for a Mortgage within the site, and page elements immediately re-render based on this expressed intent.

Technical approach. No internet interaction — the data used is already present in the browser context (IndexedDB, OPFS, Dexie JS, IDB, WASM).

Implications.

Cost relative to next tier up. Moving an Intra-page experience to the Inter-page tier typically incurs an order-of-magnitude increase in delivery cost; conversely, pulling an Inter-page experience down into Intra-page also imposes a similar order-of-magnitude jump in client complexity (source.real-time-clarity-md).

Sources

Related

This node →

  • affects-cost-oflatency-tier.inter-page— Moving up one tier ≈ 10× cost increase per Real-Time Clarity rule of thumb

← Referenced by

  • instance-ofconcept.signal-to-activation-time— Latency taxonomy enumerates this tier
  • applies-to-latency-tiermodality.web— Web supports client-side intra-page
  • applies-to-latency-tiermodality.mobile-app— Mobile apps can decision client-side
  • applies-to-latency-tiervendor.akamai— Akamai Inference Cloud is the reference architecture for ML-model-based intra-page decisioning (<100 ms) — transformer-class model inference at CDN PoPs with sub-millisecond response.