Google AdSense today sent a technical guidance email to its publisher network recommending three web performance techniques - bfcache, the Speculation Rules API, and AI-assisted debugging through Chrome DevTools - with the stated aim of reducing page load times, increasing page views, and improving the efficiency of ad delivery. The communication, sent on March 24, 2026 from [email protected], is addressed to publishers and framed as a continuation of a prior series in which Google discussed Core Web Vitals as foundational signals for both user experience and AdSense revenue.

The guidance arrives at a moment when publisher economics are under sustained pressure. Network advertising revenues encompassing AdSense, AdMob, and Google Ad Manager declined 1% to $7.4 billion during the second quarter of 2025, even as Google's own properties - Search and YouTube - posted double-digit growth in the same period. Against that backdrop, technical optimizations that can recover page views or reduce bounce rates carry real financial weight for publishers dependent on impression volume.

The back/forward cache: instant page returns from memory

The first technique outlined in the email concerns bfcache, short for back/forward cache. According to the email, when a user presses the browser's back button, the page should not reload from scratch. Instead, the browser retrieves a complete snapshot of the page from memory, restoring it instantaneously without re-executing network requests or JavaScript.

According to the communication, achieving bfcache eligibility requires removing a set of specific blockers. Three categories are identified. First, unload event handlers must be removed or replaced, since browsers disqualify pages that register these listeners. Second, the Cache-Control: no-store directive must be reconsidered, as it prevents the browser from retaining a page snapshot. Third, any open connections - including IndexedDB connections and WebSocket connections - must be closed before the user navigates away. Each of these conditions, if unresolved, causes the browser to fall back to a full page reload when the back button is pressed.

For publishers running WordPress, the email references the Speculative Loading plugin developed by the WordPress Performance Team as a path to implementation, noting in parentheses that it is a third-party open-source tool that should be evaluated against internal security and maintenance standards. For custom-built sites, publishers are directed to implement a script that controls prefetch or prerender behaviour directly in the page HTML.

The performance case for bfcache is illustrated through three publisher examples cited in the email. Yahoo! JAPAN News, according to the communication, achieved a 9% increase in mobile revenue and 13% more page views per session after implementing bfcache. Monrif, an Italian media group, saw user engagement improve by 8.9%, Largest Contentful Paint (LCP) speed up by 17.9%, and creative loading times for ads improve by as much as 17.1% on mobile. Netzwelt, a German news site, reported an 18% increase in ad revenue and a 27% increase in page views specifically by optimising Core Web Vitals scores - a metric category that bfcache eligibility directly affects by reducing reload-induced LCP measurements.

The relationship between Core Web Vitals and publisher performance is well established within the industry. For publishers already contending with declining organic search traffic, recovering page views through navigation efficiency - rather than acquisition - is a meaningful lever. Teads, which works with thousands of premium publishers globally, disclosed in November 2025 that page views had declined approximately 10-15% during the third quarter of 2025, attributing the trend to AI-powered search features that retain users within search interfaces rather than directing them to publisher sites.

Speculation Rules API: loading the next page before the click

The second technique described in the email is the Speculation Rules API. The concept is anticipatory: the browser analyses the links present on the current page and begins loading the most likely next destinations before the user clicks. This can happen either as a prefetch - downloading the page's resources in the background - or as a prerender - rendering the full page invisibly in memory so that navigation appears near-instantaneous.

According to the email, the recommended configuration uses the prefetch action with an eagerness setting of "moderate". The JSON snippet provided in the communication targets all internal URLs matching the pattern /* while explicitly excluding the /logout path, a detail that underscores the need to avoid prefetching pages that trigger authentication side effects.

The email notes that publishers have control over three parameters: the mode (prefetch versus prerender), the targets(which links to preload), and the triggers (how eagerly the browser should speculate). The moderate eagerness setting represents a middle position - more conservative than "eager", which begins speculating on hover, and more aggressive than "conservative", which waits for stronger intent signals before acting.

The warning embedded in the email is explicit: according to the communication, these changes should not be pushed directly to production. Testing in a staging environment is described as mandatory because even small changes in loading behaviour can affect the functioning of analytics scripts and advertising tags. This is a particularly relevant caution for publishers whose revenue measurement depends on accurate impression tracking. An ad tag that fires during a speculative prerender - before the user has actually navigated to the page - could result in double-counted impressions or suppressed fill rates depending on how demand-side platforms handle prerendered contexts.

Google's own search infrastructure has used prefetching mechanisms to reduce perceived load times, with mobile Chrome users on Android seeing 67-millisecond reductions in loading times through a private prefetch proxy system. The Speculation Rules API extends a version of this capability to individual publishers without requiring server-side infrastructure changes.

Chrome DevTools MCP: AI agents debugging in live browsers

The third technique marks a departure from classic performance optimization and enters the territory of AI-assisted development workflows. According to the email, Chrome DevTools now integrates with a Model Context Protocol (MCP) server that connects the browser's inspection and debugging environment to external AI coding agents.

The described workflow allows an AI agent - the email specifically names Gemini CLI, Cursor, and Claude as compatible tools - to operate Chrome DevTools in a live browser session. The agent can read performance traces, inspect the console, understand third-party code side effects, and apply end-to-end styling changes. This is described in the communication as debugging at runtime rather than through static code analysis, meaning the agent has access to the actual state of a running page rather than just the source files.

The practical illustration offered in the email is a case study from CyberAgent, a Japanese digital media company. According to the communication, CyberAgent achieved fully automated error fixing using the Chrome DevTools MCP. No further quantitative details are provided for this specific example, though the result positions the tool as capable of closing the loop between error detection and code correction without manual developer intervention.

The MCP integration is notable in the context of how Chrome's architecture has evolved as a platform for advertising and publishing infrastructure. Chrome holds a browser market share that consistently exceeds 65%, making its DevTools not merely a developer utility but a practical operational tool for anyone whose revenue depends on how pages load and behave in the browser most visitors use.

The AI assistance within DevTools also connects to a broader industry shift. The ability to chat with Gemini about performance traces, as described in the email, compresses what was previously a multi-step manual process - profiling, reading flame charts, identifying bottlenecks, writing fixes - into a conversational diagnostic session. For smaller publishing operations without dedicated engineering teams, this represents a meaningful reduction in the technical overhead of maintaining performance scores.

Context for the marketing community

Google's decision to communicate these three techniques through an AdSense publisher email - rather than through developer documentation alone - reflects the platform's acknowledgement that publisher performance outcomes are tied directly to monetization. The email's framing is consistent with an ongoing pattern observed at PPC Land: Google has been systematically expanding the toolset available to AdSense publishers through both technical features and reporting capabilities, at a time when the network advertising segment faces structural pressure.

The connection between site speed and AdSense revenue is not new. But the specific combination of techniques outlined today - memory-based navigation, anticipatory loading, and AI-assisted debugging - represents a more technically sophisticated set of recommendations than publishers have typically received through promotional channels. Implementing all three requires meaningful engineering work, and the email's own caveats about staging environments reflect awareness that careless deployment carries risk.

The AdSense anchor ad rendering bug that persisted for six days across iOS devices in February 2026 illustrated how quickly a technical malfunction in ad delivery can affect publisher revenue. The Chrome DevTools MCP, in principle, offers a mechanism for catching similar issues earlier - before they manifest as audience-facing failures. Whether that claim holds across the diversity of publisher setups remains to be seen in practice.

What makes this communication notable is not any single technique in isolation. The bfcache has been documented as a performance lever for years. The Speculation Rules API has been available in Chrome for some time. AI debugging in DevTools is relatively new. Together, however, they describe a publisher that has implemented a coherent and layered approach to page performance - one where navigation is fast by default, the next page is already loading, and errors are caught and corrected without extended engineering cycles.

Publishers operating under the combined pressures of declining network advertising revenues, reduced organic search referrals, and constrained engineering resources may find the efficiency gains worth the implementation investment. The metrics cited in the email - 13% more page views per session at Yahoo! JAPAN News, 27% more page views at Netzwelt, 18% higher ad revenue at Netzwelt, and 8.9% engagement improvements at Monrif - are specific enough to suggest these results have been measured rather than estimated, though they reflect individual implementations that may not generalise uniformly.

Timeline

  • March 2024 - Google introduces site-level approval process for AdSense for Search publishers, establishing a pattern of tightened configuration standards across publisher products (PPC Land)
  • February 12-13, 2024 - Chrome announces optimization of Safe Browsing for speed and efficiency, reducing sub-resource checks and PDF scan frequency (PPC Land)
  • February 12, 2025 - Google speeds up search through a new prefetching system reducing mobile load times by 67 milliseconds (PPC Land)
  • February 4, 2025 - Google AdSense announces merger of email communication categories, effective April 2025 (PPC Land)
  • May 9, 2025 - Google updates AdSense Auto optimize feature to give publishers site-level control over experiments (PPC Land)
  • May 21, 2025 - Google introduces display ads option for AdSense ad intents format (PPC Land)
  • July 3, 2025 - Google launches automatic fill feature for empty in-page ad spaces with 30-day rollout (PPC Land)
  • August 7, 2025 - Google network advertising revenue share from owned properties reaches 90% for the first time, with network segment declining 1% to $7.4 billion in Q2 2025 (PPC Land)
  • September 26, 2025 - Google AdSense launches traffic source breakdown feature for publishers (PPC Land)
  • November 6, 2025 - Teads discloses 10-15% page view decline in Q3 2025 across publisher network attributable to AI search features (PPC Land)
  • November 25, 2025 - Google adds policy insight tools to AdSense reporting, covering policy ad serving status and confirmed click status (PPC Land)
  • December 10, 2025 - Google AdSense announces automatic enrollment in Offerwall machine learning optimization effective January 10, 2026 (PPC Land)
  • December 11, 2025 - Google expands AdSense privacy compliance messaging to Indiana, Kentucky, and Rhode Island (PPC Land)
  • January 13-14, 2026 - Google Ad Manager and AdSense experience simultaneous technical failures causing publisher revenue declines of 50-90% (PPC Land)
  • February 13-18, 2026 - Google AdSense anchor ad bug renders close button invisible on iOS for six days (PPC Land)
  • March 5, 2026 - Google notifies AdSense for Search publishers of a 100 native style ID cap per account, effective June 3, 2026 (PPC Land)
  • March 24, 2026 - Google AdSense sends email to publishers recommending bfcache, Speculation Rules API, and Chrome DevTools MCP for site performance and ad revenue improvement

Summary

Who: Google AdSense, the display advertising monetization platform operated by Google Ireland Ltd from Gordon House, Barrow Street, Dublin 4, Ireland, addressing its publisher network.

What: A technical guidance email outlining three web performance techniques - back/forward cache (bfcache) eligibility optimisation, the Speculation Rules API with prefetch and prerender configurations, and AI-assisted debugging through a new Chrome DevTools MCP server - with the stated purpose of reducing page wait times, increasing page views per session, and improving ad delivery efficiency.

When: The email was sent on March 24, 2026 at 10:26, framed as a continuation of a prior communication series about Core Web Vitals.

Where: Delivered via email from [email protected] to AdSense publishers globally. The technical implementations described apply to publisher websites running on any infrastructure, with specific paths outlined for WordPress sites and custom-built properties.

Why: Google presented the guidance as a means for publishers to improve user experience metrics and AdSense earnings simultaneously - citing publisher case studies with figures including a 27% increase in page views at Netzwelt and 9% mobile revenue growth at Yahoo! JAPAN News - at a time when network advertising revenues are under structural pressure from AI-driven search features that reduce external traffic referrals.

Share this article
The link has been copied!