Is it better to have a lot of Frames or Animations or Images?

I started writing a backstory for my game and wrote a graphic novel ... for mobile ... and I'm using C3 to create the mobile graphic novel.

ANYWAY, thus far the graphic novel is about 150 pages and one image contains all the pages as frames.

The images aren't animated, but I've started to notice that when I open the C3 preview, it's taking longer and longer to load. Which doesn't surprise me since there are 150 frames in 1 image.

Would it be better to break the image into animations? I'd still have 1 image, but have an animation for each chapter. Example: chapter1 with 25 frames and chapter2 has 25 frames and so on. Still all one image, but with several animations, with each animation having a bunch of frames.

Or would it be better to have an image named chapter1 and a different image for chapter2, and so on and each chapter contains all the frames for that chapter?

Thoughts?

If it helps, this is what it looks like: tiktok.com/t/ZTR7w8oGX

ps The game has yet to be made, but the novel is moving along splendidly.

See memory usage in the manual. A better option is separate object for each image, or at least a small number of pages per object. Then Construct will be able to load only some images at a time and leave the others out of memory, and you can also use the system actions to load/unload object images if needed. If you have all pages in the same object, then Construct will load everything in to memory, and it will be slow and have an extremely high memory usage.

Loading dynamically from URLs is another option - you could import all your pages as image files in the project 'Files' folder, and load them one at a time from there, which will also avoid having them all in memory at the same time (as loading an image from a URL to a Sprite will replace the current image).