Develop With Faith
October 21, 2026

The Back Button Your Church Website Keeps Breaking: A Plain-English Guide to bfcache

Watch someone browse a church website on their phone and you will see a pattern. They tap into a sermon, then hit back. They open an event, then hit back. They check the kids page, then hit back. The back button is one of the most-used buttons on your site, and you didn't build it.

On a well-built site, every one of those back taps is instant. The previous page simply reappears, scrolled exactly where they left it. On a lot of church sites we audit, it reloads from scratch instead: blank screen, spinner, images popping in, the list jumping back to the top. Nothing is technically broken. It just feels slow, many times per visit.

The fix usually has nothing to do with redesigning anything. It lives in a browser feature called the back/forward cache, or bfcache.

What bfcache Actually Does

When someone leaves a page, modern browsers can keep a complete snapshot of it in memory: the layout, the scroll position, even the half-filled form. If the visitor comes back with the back or forward button, the browser restores that snapshot rather than rebuilding the page. No network request, no rendering, no waiting.

This happens a lot. Chrome's own data shows that roughly one in ten desktop navigations, and about one in five on mobile, are back or forward navigations. For a church site, where people bounce between a sermon archive, an events list, and a "Plan a Visit" page, the share is often higher.

The catch is that browsers only use the cache when a page is eligible. A few common choices quietly make a page ineligible, and then every back tap becomes a full reload.

Why Church Sites Often Miss Out

In our experience, ministry sites usually lose bfcache for one of a handful of reasons. Most of them are leftovers from plugins or embeds nobody remembers adding.

Old "unload" scripts. Some analytics tools, chat widgets, and older WordPress plugins run code when a page unloads. Browsers treat that as a signal the page can't be safely frozen, and Chrome has been phasing out the unload event entirely. If something on your site still relies on it, it is both blocking bfcache and living on borrowed time.

Pages sent with "no-store" headers. Some hosting setups and security plugins tell the browser never to store a page, even public ones like your homepage or sermon list. That instruction makes sense for a member portal or a giving receipt. It doesn't make sense for the page with your service times.

Open live connections. Livestream chat, real-time prayer walls, and some giving widgets keep a connection open to a server. If that connection is still open when the visitor leaves, the browser may refuse to cache the page.

Embedded third-party frames. Calendar embeds, map widgets, and video players each bring their own code. If one of them misbehaves, the whole page can lose eligibility, even though your own code is fine.

None of this is anyone's fault. It is what happens when a site grows one helpful plugin at a time over several years.

How to Check Your Own Site

You don't need to be a developer to see whether this is a problem. You need Chrome and about five minutes.

  1. Open a page you care about, like your sermon archive or events page, in Chrome on a computer.
  2. Open DevTools (right-click, then "Inspect") and go to the Application tab.
  3. In the left sidebar, find Back/forward cache and click Test back/forward cache.

Chrome will navigate away, come back, and tell you whether the page was restored from the cache. If it wasn't, it lists the reasons in plain language, such as "the page has an unload handler" or "the main resource has cache-control: no-store." That list is your to-do list.

Run it on your five busiest pages. For most churches that means the homepage, Plan a Visit, the sermon or media page, events, and giving. Google's Lighthouse report also includes a bfcache check now, so if you already run Lighthouse audits you may have seen this flagged without knowing what it meant.

What Fixing It Looks Like

The fixes are usually small. We'd tackle them in this order.

Remove or replace unload handlers. If a plugin or script uses the unload event, check for an update first; most well-maintained tools have already switched to the "pagehide" event, which works with bfcache. If a plugin hasn't been updated in years, that is a good reason to retire it anyway.

Loosen caching on public pages. Ask your host or developer to stop sending "no-store" on pages that hold no private information. Keep it on account pages, checkout, and anything with personal data. This is a settings change, not a rebuild.

Close live connections when people leave. If you run livestream chat or a live prayer wall, the code should close its connection when the visitor navigates away and reopen it if they come back. A developer can wire this up with the browser's "pagehide" and "pageshow" events in an afternoon.

Refresh what needs refreshing on return. Some content does need to update when someone comes back, like a "Live now" badge or a seats-remaining count on an event. Instead of blocking bfcache to force a reload, a small script can check for changes when the page is restored. The visitor gets an instant page plus fresh information.

If you're on a hosted platform like Squarespace or a church-specific builder, you have less control over the code, but the DevTools report still helps. Removing one stale embed or chat tool can be enough to make the difference.

Why This Is Worth Doing Now

The next ten weeks bring the heaviest traffic most church sites see all year. Families will compare Christmas Eve service times, scroll through Advent events, and check where to park. Many of them will be first-time visitors on a phone, standing in a kitchen or sitting in a car, tapping back and forth between pages.

Every one of those back taps is a small moment of hospitality. An instant page says we were ready for you. A slow reload, repeated five or six times, says something else, even if no one could put it into words.

We think of this the way we think of a well-kept entryway. No one comes to church because the doors open smoothly. But they notice when they stick, and they notice when someone thought ahead.

A Small Fix With an Outsized Return

Back/forward cache isn't glamorous. It won't show up in a redesign mockup, and no one will compliment you on it. But it is one of the rare performance improvements that costs almost nothing, touches almost every visit, and makes your site feel faster than a lot of expensive changes would.

If you'd like a second set of eyes before the Advent rush, we're glad to run the check on your busiest pages and tell you, plainly, what's blocking it and what it would take to fix. Reach out to us here and we'll take a look together.

← Back to all posts