Previously, I optimized your file, which consists of 10 pages converted into images, reducing its size from 8.7MB to 2.8MB. In general, images require longer loading times compared to text.
I was able to replicate your issue only when I quickly navigated between pages, especially using Google Viewer rather than the built-in viewer. Unfortunately, the control menu of the viewer cannot be affected by CSS.
There’s not much I can do, aside from suggesting that you avoid rapidly switching pages. There are some guidelines you might want to ask GPT about how to create an optimized PDF.
To my knowledge, PDFs should be easier to open, but since they are embedded into a web-embed component, the file isn’t stored on the device ram compared to using an image component.
This is quite complex to explain when it comes to PDFs, as it could be related to the type of image file (BMP, TIFF, or JPEG, etc.), image resolution, the variety of fonts, the number of vector objects, and so on (feel free to ask GPT about this). Similarly, with the use of an image component (excessive resolution, etc.), everything should ideally be optimized beforehand before being uploaded.
