The back button reloads instead of going back instantly

On most websites, pressing Back restores the previous page instantly from a snapshot the browser kept in memory. In this app it does a full reload instead. That is on purpose.

Why

App pages carry your data — your chart, your birth data, your client records. The browser's back-forward cache keeps a live snapshot of a page in memory after you navigate away from it, which means:

• On a shared or borrowed computer, someone pressing Back after you sign out could see a page of your data restored from memory.
• A page restored from the snapshot shows stale state — the plan you had before upgrading, a chart you have since edited.

So the app marks its own pages as not storable, and the browser reloads them instead. It costs a second. It is the right trade for pages that hold a birth time.

What this means for you

• Back always fetches fresh, so what you see is current.
• If your session expired while you were away, pressing Back will land you on sign-in rather than on a stale copy of your data. That is working correctly.
• It is slower than an instant restore. On a slow connection you will feel it.

Public pages are different

The marketing pages, the glossary and shared chart links are ordinary cacheable pages and behave normally. It is only the signed-in app that does this.

If Back sends you to sign-in every time

That is a different problem — a session that is not persisting rather than the cache behaviour. See signed out unexpectedly.