
I assume this happens when
- The initial HTML page cannot be obtained on time over the network and it's obtained from the cache instead, and
- The other resources it loads have a content hash in their URL and their content has changed since the HTML page has last cached
A possible solution would be to fallback to the cache in case of a network error.