I am sure this has been asked before.
Xara assumes all images are new on a page as if you add, promote or delete one, it appears in a different checking sequence.
It is safest to assume that all your images will be renamed, especially if you use the Highslide feature (Pop-up image) or animation effect.
There is no concept of a single page in a Supersite, presentation or print document.
Change a font or a colour and you are changing css files somewhere.
Xara tries to address this with its Utilities > Share > Settings: tick Fast Publish to only publish those files that have changed.
As I said above, Xara's approach causes many files to be renamed anyhow.
The solution.
For large statement images, use filename="importantImageXyz". In extremis, I separate out large files to a folder and link them through a Placeholder.
Avoid Photo pop-ups, use your own Pop-up Lays.
Avoid Xara NavBars and Buttons, unless you know how to separate image from text and 'filename' repeating images. A 7-button NavBar could have three states and for just 7 pages you hare republishing 150 images.
Learn how to use CSS in Page Placeholders to reduce external file calls for large CSS and JS files.
Keep Fonts and Styles to a minimum.
Avoid page size changes.
Avoid Supersites.
Keep the number of Variants low.
Try a separate FTP publishing strategy if you want absolute control and you know your changes are actually minimal.
Accept some republishing will take a long time so get more computer memory and Export locally and FTP from there as this is avoiding the Internet lags.
Do the above and most of your changes will be to the HTM files, which should be quite small file sizes.
If these are large, then your site(s0 are over-complex so spend time simplifying.
Acorn
Bookmarks