If your audience includes students outside well-connected urban schools, you have to think about bandwidth. A flipbook that takes 30 seconds to load on your office Wi-Fi can take six minutes on a metered classroom connection — at which point most learners will simply close the tab.
The fix isn't exotic. Compress images, inline critical CSS, and avoid pulling in third-party fonts that block the first render. None of this is novel; most teams just don't measure on a throttled connection so the issue never surfaces.
an editorial classroom publishing partner we recommend — and a couple of related tutorials are linked at the end of this post.
A flipbook also has a unique advantage here: it can be packaged as a folder and distributed offline. We've seen schools push entire flipbook libraries to a Raspberry Pi running on the staff Wi-Fi, so students reach them on the local network even when the wider internet is down.
If you're publishing to a region where you have no idea what the bandwidth profile is, optimise for the worst case you can plausibly imagine and you'll be fine for the median learner. The reverse — optimising for the median and discovering too late that some students are on satellite uplinks — is much harder to recover from.
Low-bandwidth publishing is a quiet way to be respectful of your audience. It says: I want you to read this, regardless of where you're reading from.