I work on OnePassApps, so this is our own site, and everything below is a measurement of the live responses from app.onepassapps.com taken on 4 November 2026 - plain HTTPS requests from outside the browser, no JavaScript, one build, one day.
The last few posts in this series looked at what a browser fetches ( sitemap.xml , robots.txt , the web app manifest, the Open Graph tags, the route map and browser storage). This one looks at the other half of the conversation: the headers the server sends back before any of that arrives. It is the layer you never see in a screenshot, and it is where the caching, compression and browser-security policy of a site actually live.
One header set for every page
I fetched every URL in the site's sitemap.xml - the home page, the seven studios, the two hosted apps, /guides , /guides/newsflow , /guides/movie-tracker , /plans , /terms and /voting - plus /support and one URL that does not exist, /nonexistent-xyz .…