Action follows the audit
The workflow ends with usable replacement files, not only a score or a list of generic recommendations.
Optimize Images from Any Webpage
Scan one public webpage, select heavy image candidates, optimize them locally and download a replacement bundle.
Single-page scanPublic targets onlyLocal optimization
Move from webpage evidence to replacement files.
Scan one public page, review verified supported images and their measured size, deselect anything you do not need, then compress and package the rest in the same local engine used for uploads.
- Scan scope
- One public webpage per scan
- Selection
- Supported images selected by default
- Output
- Optimized files plus replacement map
Scope stays visible
The page states what static HTML discovery misses and never claims full-site, rendered-page or script-executed coverage.
How it works
The webpage URL and selected public asset URLs must be fetched over the network. Compression, previews, settings and ZIP creation run locally after import.
Scan one page safely
Enter one public HTTP or HTTPS webpage. The server validates the destination and fetches a bounded HTML response without credentials.
Choose real opportunities
Review thumbnails, measured sizes, dimensions, formats and heuristic issue labels. Supported images start selected so you only need to remove assets you do not want.
Build the replacement bundle
Use the already verified assets, optimize them in browser workers and download individual replacements or a mapped ZIP.
Useful for
- Prepare optimized replacements for heavy images on a landing page.
- Resize oversized assets to better match their declared layout dimensions.
- Keep source-to-output filenames traceable with a replacement map.
Questions about optimize images from any webpage
Does the optimizer crawl my whole website?
No. It fetches one public HTML document and does not follow internal links. Run another scan for another page.
Which webpage images can it find?
It discovers image URLs present in fetched HTML, including image, lazy-image, srcset, picture, social metadata and image-preload sources. It does not execute JavaScript, render the page or discover CSS background images.
How are replacement files created?
Supported files are verified and loaded three at a time, selected by default and then passed to browser workers. The ZIP can include replacement-map.json so source URLs can be matched to output filenames.