A JSON fetch using { cache: ‘reload’ } was found on three pages — the Visual Troubleshoot flowchart, the Web Dictionary, and What’s New — each pulling their data file fresh on every single page view instead of letting the browser cache it normally.
⚡ Quick Fix (TL;DR)
The Culprit: { cache: 'reload' } was most likely copy-pasted between files during the original build as a workaround for an old caching bug, then never revisited once that underlying bug was fixed elsewhere.
The Fix: Removed { cache: 'reload' } from all three fetch calls, letting normal browser HTTP caching (respecting the server's own cache headers) take over. Treat any cache: 'reload' found elsewhere as a red flag worth double-checking — it almost always means a one-time workaround that outlived its reason for existing.
Rather not untangle this yourself? Our Done-For-You team handles exactly this kind of thing, start to finish.
See DFY options → Was this helpful? Thanks for the feedback!
Tagged in :