Originally Posted by murg
Why they aren't using the time when you are reading a page to pre-process the most likely next event (page forward) is a mystery to me.
I'm totally with you. Thit is the first thing i thought when I saw this slow page turn bug.
They should simply pre-render the next/previous page in a buffer, and show it when the user turn page (and then prerender the next page...)
This will make for near-instantaneous page turn, without any added cost.
I'm a software dev, so I know that prerender a page is not something you can implement in some hours of work... but the benefit for the user experience will be huge!