If you’ve got a VPS at your disposal, many of the homepage softwares I’ve tried over the years have some amount of caching to make them quite fast or even operate offline(“Homer” for one required me to deeply purge my cache as it would still appear when my site was offline…despite having replaced it long ago! 😂). Or, if you wanted to roll your own static HTML page, you can absolutely add a Service Worker for your own offline caching.
That’s where I’m at now. I use a custom ServiceWorker static HTML for my homepage and tab page on all my devices. This page is a bouncer, checks if I’m at home or not(or if my local dashboard is offline) and either redirects me to the local homepage which has all my HomeLab services on it, or if it fails just tells me I might be abroad or offline and lists a few public websites.
And yes, this works offline or over a shitty connection. Essentially the service worker quickly provides the cached page from the browser storage, then tries to take the time to check the live version. If it gets one, it updates the cache, if not, enjoy the offline version.
It’s not really because it fell over. It’s because it wasn’t supposed to fall over. Consumable launch materials don’t contend with this because failure to return is a success. This is a failure. This must be learned from and fought against/prevented going forward.