I wonder if it was unintentional and some stupid caching setup returning dirty caches (and then more likely returning USA Today because that’s the most likely to have caused the first cache hit).
This thread from the publisher addresses this:
<a href="https://twitter.com/burk504/status/1501618260466233344" rel="nofollow">https://twitter.com/burk504/status/1501618260466233344</a>