We control browser caching based on the publish cycle from within Digioh. Specifically, it is the “boostrapper” (e.g. the Low Impact Tag) that does this. This is a very small amount of JS, and we set the browser cache refresh frequency very high so that the boostrapper can see your Publishes quickly and download the newly published account settings. These will then be cached, effectively until the next publish. In practice, this means that +99% of Digioh code is cached. The boostrapper decides which version of your Digioh account to retrieve.
All Digioh source is gzip compressed for transit.
User Experience Impact
Minification, caching, and compression applies to all Digioh code. However, the practical impact of running Digioh JS on your site also depends on which version of the Digioh JS you use. There are tradeoffs between activation time and network load. More details here: Installing Digioh: choosing the right JS Snippet.