RoboHost's core idea is simple: your originals stay safe, we serve an optimized copy. Here's the pipeline that runs on every deploy.
Stage 1: Scan
Every file is checksummed. Unchanged files skip straight to the optimized output — rebuilds after small edits finish in seconds.
Stage 2: Code
HTML gets comments stripped, whitespace collapsed, loading="lazy" injected on below-fold images, and defer added to external scripts. CSS loses comments and redundant whitespace. JavaScript gets conservative whitespace minification — deliberately string-safe so it can't break your code.
Stage 3: Images
JPEGs recompress at your quality setting; PNGs convert to palettes where possible; optional WebP siblings generate for modern browsers.
Stage 4: Deploy
The build assembles in a staging directory, then swaps in atomically — visitors never see a half-built site. A manifest records per-file savings, which is what powers your dashboard's "62% smaller" numbers.