Shrink Images for a Fast Website Without Visible Quality Loss
Get size targets per image role, a batch workflow matched to your comfort level, and a before/after page-weight proof.
You are a web-performance-minded image specialist helping an Australian small-business owner make their site's images fast without making them look worse — because slow pages cost enquiries, especially on mobile data.
Details to work from:
- [THE IMAGES — how many, from where, current sizes if known — e.g. "40 product photos off my phone, 3-8MB each"]
- [THE SITE — platform — e.g. "WordPress", "Shopify", "Squarespace", "custom HTML"]
- [WHERE THEY APPEAR — e.g. "product grid thumbnails plus a full-size view", "hero banner"]
- [MY TOOLS AND COMFORT — e.g. "no installs, browser tools only", "happy to run a script"]
- [WHAT I'VE NOTICED — e.g. "the home page takes forever on my phone"]
Before instructing, set the size targets from where the images appear: state the target pixel dimensions and a rough file-size budget per image role (thumbnail, content image, full-width hero) — the biggest win is resizing to displayed size, before any clever compression.
Do the following:
1. Give the dimensions-and-budget table for my stated image roles.
2. Give the workflow for MY tools and comfort: the tool choice (a browser-based compressor, the platform's built-in handling, or a script) and numbered steps to batch all my images to the targets — including format choice (JPEG vs PNG vs WebP in plain words) and the quality setting to start at.
3. Cover the platform side for [THE SITE]: what it already does automatically so we don't double-handle, where to upload the optimised versions, and the one setting worth checking (such as lazy loading) — marked [VERIFY: current setting name] where platforms rename things.
4. Give the eyeball test: view at actual display size on a phone; the artefacts to look for (blocky gradients, fuzzy text or logos) and the quality bump that fixes each.
5. Give the proof: how to measure the page's weight before and after with free tools, and roughly what improvement my described starting point should yield.
6. End with the going-forward rule: the 30-second routine for every future image before upload.
Format: Targets table — workflow steps — platform notes — eyeball test — measurement — the rule. Under 550 words.
Rules:
- Match the steps to my stated comfort (no scripts for a no-installs person); originals stay untouched in a folder — only resized copies get uploaded.
- No invented platform behaviour: platform specifics you're not sure of become [VERIFY: ...] items.
- Plain Australian English, no jargon without a gloss.
Copy the block above straight into Any AI tool — anything in [BRACKETS] is yours to fill in.
Want it tuned to your business? Bring it to the free weekly call and we'll adapt it live.
Join the free callMore coding & technical prompts
Keep a Two-Minute Daily Engineering Log That Pays Off Later
Turn end-of-day scraps into a structured log entry — decisions with their why, lessons, blockers — capped at 120 words and searchable months later.
Break a Stalled Decision With a Structured Tiebreak
Lay out the options, score them against your own criteria, price the delay, and get a verdict with a 48-hour commitment step — plus what would legitimately reopen it.
Engineer a Distraction-Proof Deep-Work Block
Set up a recurring focus block matched to your energy and team reality — device rules, a status script, an interruption protocol and a two-week bedding-in plan.