Two things you can’t control in postprocessing:
-
form detection. We can disable this for you as long as you have optimization totally disabled (I see you do), AND you don’t want to use our forms service. If this is true, let me know your site’s API ID and I can turn off forms processing for you.
-
mixed content warnings. We look for
http://links in your pages and tell you about those so you’ll be aware that a browser is likely to act ugly when displaying the pages. No way to disable this.
However, we wouldn’t have to process at all if you used best practices in creating your site. I don’t think you just edited 839 pages in one commit, yet you have 839 new assets to upload. This is likely due to some antipattern you use in building, as described in this article:
If you don’t change most files, we don’t have to upload and scan most files (no processing of files that didn’t change will occur), so that’s the “best way” to speed up your deploys 