One content tree, one API call, six ways of reading it. Switch the lens to change how the catalogue is arranged — by shape, by owner, by audience, by relationship. Open any service for the full record as the mobile app receives it.
Bilingual, governed content published once in Umbraco and consumed consistently by the Health SuperApp, web portals, campaigns, notifications, and future digital channels.
Open a record to preview the structured information delivered to downstream applications.
Run equivalent full-response calls from this browser to the Umbraco origin and to Azure Front Door. Each sample records direct-origin latency, an edge cache miss, and the immediately repeated cache hit so the CDN benefit is visible under the same network conditions.
The test warms both TLS connections, then interleaves the three paths. Results are browser observations, not an Azure SLA. Automatic monitoring pauses while this tab is hidden.
Timing-Allow-Origin. Browser downlink and RTT values are coarse network hints, not capacity measurements.
Watch each direct, cache-miss, and cache-hit request develop in real time. The pending point rises with elapsed time, then locks into the series when the full response body arrives.
Bypasses Front Door, WAF, CDN, and APIM.
Edge traversal plus APIM and origin work.
Served from the nearest populated edge cache.
Median bars and sample distribution show both typical speed and run-to-run variability. Lower and tighter are better.
Every measured request, with p50 and p95 guides.
Median time to first byte versus body download time from Resource Timing.
Compression ratio, transfer volume, and effective body throughput.
Status, payload size, and browser-visible Azure cache headers for every measured request.
Useful when comparing runs from different devices or networks.
Only timing summaries are stored locally in this browser. Credentials and response bodies are never persisted.