Is there a way to implement caching functionality in the web viewer to improve page load times when navigating back?

When navigating back in the web viewer, the previous page reloads, causing slow load times. Is there a way to implement caching functionality similar to browsers, so that the cached page is displayed instead of reloading the entire page?

To speed up back navigation in your web viewer, implement caching. Client-side caching, using service workers (for PWAs), HTTP cache headers, or in-memory/local storage, is usually the best approach. Server-side caching, via reverse proxies or web server modules, is effective if you control the server. Be sure to handle cache invalidation and memory usage appropriately. The optimal strategy depends on your web viewer’s implementation and server access.

Hello,

Do you have access to configure your server Illinois Pass to implement reverse proxy caching, or is it hosted on a platform that handles it for you?

Best Regard,
Nipo

Yes, you can improve back-navigation speed by caching pages. The exact method depends on your platform:

  • In-memory caching: Store pages when first loaded and reuse them on back navigation.
  • WebView settings (Android/iOS): Enable caching via setAppCacheEnabled(true) or configure WKWebView caching.
  • Service Workers (for web apps): Great for offline caching and fast reloads.
  • Local/session storage: Save page content and restore it manually.

Let me know your platform for a more specific solution! CT PARTS

This topic was automatically closed after 166 days. New replies are no longer allowed.