Originally Posted by taming
IMO, the only way we would really know is to be using the same book, loaded onto the reader in the same format and timed with a fair amount of precision.
Sure, that might be interesting but it's not a fix. I've mentioned on several occassions that the correct way to fix this is to cache both the previous and next page. Why has no developer addressed this perfectly logical recommendation? The most feedback we've received on this specific issue is that chapters are cached. Of course, from a pragmatic perspective, caching chapters is pretty worthless because people are not scrolling through them. In fact, chapter caching is only going to slow down the overall end user experience simply because it's a bigger job that takes more system resources.
So the fix is simple. Cache both previous and next page as a background task when the current page has been loaded for a few seconds (this means the page's contents are being read).