Google AdSense pushes bfcache, speculation rules, and AI debugging to publishers Google AdSense today urged publishers to implement bfcache, speculation rules, and Chrome DevTools AI debugging to boost page views and ad revenue efficiency.

FYI: Google AdSense pushes bfcache, speculation rules, and AI debugging to publishers #GoogleAdSense #bfcache #SpeculationRules #AIDebugging #Publishers

Google AdSense pushes bfcache, speculation rules, and AI debugging to publishers Google AdSense today urged publishers to implement bfcache, speculation rules, and Chrome DevTools AI debugging to boost page views and ad revenue efficiency.

FYI: Google AdSense pushes bfcache, speculation rules, and AI debugging to publishers #GoogleAdSense #bfcache #SpeculationRules #AIDebugging #Publishers

Google AdSense pushes bfcache, speculation rules, and AI debugging to publishers Google AdSense today urged publishers to implement bfcache, speculation rules, and Chrome DevTools AI debugging to boost page views and ad revenue efficiency.

ICYMI: Google AdSense pushes bfcache, speculation rules, and AI debugging to publishers #GoogleAdSense #bfcache #AI #ads #digitalmarketing

Google AdSense pushes bfcache, speculation rules, and AI debugging to publishers Google AdSense today urged publishers to implement bfcache, speculation rules, and Chrome DevTools AI debugging to boost page views and ad revenue efficiency.

ICYMI: Google AdSense pushes bfcache, speculation rules, and AI debugging to publishers #GoogleAdSense #bfcache #AI #ads #digitalmarketing

Google AdSense pushes bfcache, speculation rules, and AI debugging to publishers Google AdSense today urged publishers to implement bfcache, speculation rules, and Chrome DevTools AI debugging to boost page views and ad revenue efficiency.

Google AdSense pushes bfcache, speculation rules, and AI debugging to publishers #GoogleAdSense #bfcache #AdRevenue #WebDevelopment #Publishing

Google AdSense pushes bfcache, speculation rules, and AI debugging to publishers Google AdSense today urged publishers to implement bfcache, speculation rules, and Chrome DevTools AI debugging to boost page views and ad revenue efficiency.

Google AdSense pushes bfcache, speculation rules, and AI debugging to publishers #GoogleAdSense #bfcache #AdRevenue #WebDevelopment #Publishing

With #CoreWebVitals data, we usually help agencies and merchants improve their sites and shops. But sometimes the data helps browsers too.

An example:
We recently spotted very inflated INP numbers across many sites on mobile (P75) specifically for `back-forward-cache` aka #BFcache navigations.

1/5

Chasing BFCache navigations What is BFCache? The Back/Forward Cache, or BFCache, is a browser mechanism that allows a page to be restored instantly when a user uses the browser's Back or Forward buttons. Unlike a simple HTTP cache, BFCache preserves the entire state of the page in memory: DOM, JavaScript, application state,

Chasing BFCache Navigations, by @perfplanet.bsky.social:

calendar.perfplanet.com/2025/chasing-bfcache-nav...

#performance #bfcache #caching

Instant Back/Forward Navigations in WordPress The new No-cache BFCache plugin enables instant back/forward navigations, particularly while logged in. See demos below for the impact this has on brow...

#WordPress #bfcache #performance #speculative-loading

Origin | Interest | Match

Instant Back/Forward Navigations in WordPress The new No-cache BFCache plugin enables instant back/forward navigations, particularly while logged in. See demos below for the impact this has on brow...

#WordPress #bfcache #performance #speculative-loading

Origin | Interest | Match

Instant Back/Forward Navigations in WordPress The new No-cache BFCache plugin enables instant back/forward navigations, particularly while logged in. See demos below for the impact this has on brow...

#WordPress #bfcache #performance #speculative-loading

Origin | Interest | Match

Instant Back/Forward Navigations in WordPress The new No-cache BFCache plugin enables instant back/forward navigations, particularly while logged in. See demos below for the impact this has on brow...

#WordPress #bfcache #performance #speculative-loading

Origin | Interest | Match

"Buggy" bfcache Behavior For anyone who doesn't know, bfcache is the Back/Forward cache in browsers. I recently fixed an unusual issue in a page that I host that was caused by this. For multiple years, this site ran without fine until suddenly it started misbehaving. Navigating back to a page after following a link would occasionally just reload the current page. Originally I thought this was something wrong with my service worker cache. However, after careful analysis, I discovered the true root of the issue, bfcache. When a page is restored from bfcache, it is **NOT** rebuilt using `DOMParser`. The page is loaded back to the same state at which you left it including any modifications to the DOM and even the console log history is maintained. In this project, I have animations that were running during a `beforeunload` event. This chain eventually lead to a `tranistionend` event that would trigger the actual page navigation. The issue I was having was that the `transitionend` event handler which I was adding just before leaving the page was remaining active on page restore, and thus, when the page load animations ended, that would trigger an immediate navigation away, back to the page that was just active. This `transitionend` handler was not properly cleaned up as the expectation was for the page to be unloaded immediately after it fired. Adding a call to `removeEventListener` before the actual navigation cleared the issue right up. Now this is a pretty specific and unusual issue, but if you are noticing unexpected behavior in your web apps after page navigation, bfcache restoring your page instead of it reloading may be your issue. To confirm if bfcache is the issue, it can be disabled by adding an `unload` event handler. window.addEventListener('unload' () => {}); On desktop browsers this makes the page ineligible for bfcache. Of course, disabling bfcache is not the right approach to fix this, I had to dig deeper. What I found is that, use of the `unload` and `beforeunload` events are no longer recommended and the best way to address this was by handling any state cleanup inside a `pagehide` event handler and set everything back up in a `pageshow` event handler. window.addEventListener('pagehide', event => { console.log('page saved to bfcache, perform state saving here'); }); window.addEventListener('pageshow', event => { if (event.persisted) { console.log('page was restored from bfcache, restore state here'); } else { console.log('normal page load, do fresh page setup'); } }); For the best user expereience, the above approach is reccomended. However, if you absolutely MUST start with a fresh page load for whatever reason. This can be accomplished by triggering a reload after a `pageshow` event. window.addEventListener('pageshow', event => { if (event.persisted) { location.reload(); } });

"Buggy" bfcache Behavior For anyone who doesn't know, bfcache is the Back/Forward cache in browsers. I recently fixed an unusual issue in a page that I host that was caused by this. For multiple years, this site ran without fine until suddenly it started misbehaving. Navigating back to a page after following a link would occasionally just reload the current page. Originally I thought this was something wrong with my service worker cache. However, after careful analysis, I discovered the true root of the issue, bfcache. When a page is restored from bfcache, it is **NOT** rebuilt using `DOMParser`. The page is loaded back to the same state at which you left it including any modifications to the DOM and even the console log history is maintained. In this project, I have animations that were running during a `beforeunload` event. This chain eventually lead to a `tranistionend` event that would trigger the actual page navigation. The issue I was having was that the `transitionend` event handler which I was adding just before leaving the page was remaining active on page restore, and thus, when the page load animations ended, that would trigger an immediate navigation away, back to the page that was just active. This `transitionend` handler was not properly cleaned up as the expectation was for the page to be unloaded immediately after it fired. Adding a call to `removeEventListener` before the actual navigation cleared the issue right up. Now this is a pretty specific and unusual issue, but if you are noticing unexpected behavior in your web apps after page navigation, bfcache restoring your page instead of it reloading may be your issue. To confirm if bfcache is the issue, it can be disabled by adding an `unload` event handler. window.addEventListener('unload' () => {}); On desktop browsers this makes the page ineligible for bfcache. Of course, disabling bfcache is not the right approach to fix this, I had to dig deeper. What I found is that, use of the `unload` and `beforeunload` events are no longer recommended and the best way to address this was by handling any state cleanup inside a `pagehide` event handler and set everything back up in a `pageshow` event handler. window.addEventListener('pagehide', event => { console.log('page saved to bfcache, perform state saving here'); }); window.addEventListener('pageshow', event => { if (event.persisted) { console.log('page was restored from bfcache, restore state here'); } else { console.log('normal page load, do fresh page setup'); } }); For the best user expereience, the above approach is reccomended. However, if you absolutely MUST start with a fresh page load for whatever reason. This can be accomplished by triggering a reload after a `pageshow` event. window.addEventListener('pageshow', event => { if (event.persisted) { location.reload(); } });

Nejrychlejší e-shop roku 2024: časté chyby, co funguje a čím se vyznačuje vítěz? | PageSpeed.cz Nejrychlejší e-shop roku 2024 je iWant.cz, jehož autorům srdečně gratulujeme, stejně jako autorům webů Hornbach.cz a Altisport.cz, kteří skončili na stupních vítězů. Co ale data říkají a co si z nich ...

The #WebPerf optimization is unique for each website.

But what works every time?

🔘 #WebP Images.
🔘 loading=lazy on all <img> below the fold.
🔘 <link preload> on important webfonts.
🔘 size-adjust on webfonts.
🔘 Optimisation for #BFcache.

Translated text:
pagespeed-cz.translate.goog/blog/nejrych...

Nejrychlejší e-shop roku 2024: časté chyby, co funguje a čím se vyznačuje vítěz? | PageSpeed.cz Nejrychlejší e-shop roku 2024 je iWant.cz, jehož autorům srdečně gratulujeme, stejně jako autorům webů Hornbach.cz a Altisport.cz, kteří skončili na stupních vítězů. Co ale data říkají a co si z nich ...

Co vždy pomůže rychlosti e-shopu? 🚀

— Obrázky ve formátu WebP.
— loading=lazy na všechny <img> pod zlomem.
— <link preload> na důležité webfonty.
— size-adjust u důležitých webfontů.
— Optimalizace pro #BFcache.

V textu se dozvíte i časté chyby:
pagespeed.cz/blog/nejrych...

#RychlostWebu