Image Optimization Audit Checklist for Small Websites

Small websites often carry image problems for years because no single file looks urgent. A homepage hero is a little too large. A team photo was uploaded straight from a phone. A blog thumbnail is served at 2400 pixels wide even though the card is 420 pixels wide. None of these mistakes feel dramatic on their own, but together they make the site slower than it needs to be.

An image audit is the cleanest way to fix that without guessing. The goal is not to convert every file to WebP on day one. The goal is to understand what is on the site, which images matter most, and what can be improved without hurting quality or breaking templates.

An audit checklist that only says "compress your images" gives no evidence trail. A small-site audit should leave behind a page inventory, a sample conversion report, visual review notes, and a short list of exceptions that should stay PNG, SVG, JPEG, or untouched.

Start With an Inventory#

List the images that actually appear on your important pages. For a small business site, that usually means the homepage, pricing or services page, top landing pages, contact page, and a handful of recent blog posts. Do not start with the media folder alone; folders contain old exports, unused images, and duplicates that may not affect users.

For each visible image, record:

• page URL
• image URL
• displayed size
• natural dimensions
• file format
• file size
• image role: hero, thumbnail, logo, screenshot, product photo, background, or icon

The image role matters. A logo, a screenshot, and a hero photograph should not be reviewed with the same quality threshold.

Keep the inventory concrete:

page,image_url,role,displayed_size,natural_size,current_bytes,above_fold,action
/,/images/hero.jpg,hero,1280x720,3200x1800,824120,true,resize+convert
/pricing,/images/logo.png,logo,160x48,320x96,18422,true,keep SVG/PNG
/blog/example,/images/screenshot.png,screenshot,860x520,1720x1040,392441,false,test high quality

Find Oversized Images Before Changing Formats#

Many image problems are dimension problems before they are format problems. If a 4000-pixel image is displayed at 800 pixels wide, converting it to WebP helps, but it still leaves waste on the table. Resize first, then compress.

Look for images where the natural width is more than about twice the largest displayed width. That is not a legal rule, just a practical review signal. High-density displays need extra pixels, but they do not need a full camera original for a small card.

This is where small websites get quick wins. Replacing a few oversized hero and gallery images can improve the real page faster than optimizing dozens of tiny decorative assets.

Decide Which Files Should Become WebP#

WebP is a strong default for web photos and many graphics because it supports lossy compression, lossless compression, transparency, and broad modern browser support. Google’s WebP overview notes that WebP can produce smaller images than JPEG and PNG at comparable visual quality, while MDN’s image format guide describes WebP as a good choice for both still and animated web images.

That does not mean every image should change. Keep SVG for vector logos and icons. Be careful with screenshots that contain small text. Review transparent PNGs against the actual backgrounds where they appear. If a platform outside your website needs the file, such as an email tool or marketplace upload form, check that platform separately.

Run a Small Conversion Pass#

Pick ten representative files before changing the whole site:

• one hero photo
• one staff or location photo
• one blog thumbnail
• one screenshot
• one transparent graphic
• one product or portfolio image
• a few typical content images

Convert those files to WebP and review them on the actual pages. If you use GetWebP locally, keep the original files untouched and write converted files as separate outputs:

mkdir -p ./audit-reports

getwebp ./audit-sample \
  --recursive \
  --output ./audit-output \
  --dry-run

getwebp ./audit-sample \
  --recursive \
  --output ./audit-output \
  --quality 82 \
  --json > ./audit-reports/sample-q82.ndjson

The exact quality value is less important than the review process. A good setting for product photos may be too aggressive for screenshots with text.

Summarize the conversion evidence:

jq -r '
  select(.type == "convert.completed")
  | .data.results[]
  | [.status, .file, .outputPath, .originalSize, .newSize, .savedRatio, .quality, .qualityMode, (.error // "")]
  | @tsv
' ./audit-reports/sample-q82.ndjson

The GetWebP CLI command reference documents --dry-run, --recursive, --output, --quality, and --json; the JSON output guide explains the report fields. Keep this report with the page inventory so later reviewers can tell which savings came from conversion, which came from resizing, and which files failed or need exceptions.

Review Quality Like a Publisher#

Do not approve images by file size alone. Open the page and compare the converted version with the original at normal reading size. Then inspect high-risk areas at 100 percent: faces, text, gradients, shadows, transparent edges, and product texture.

Reject output when the damage is visible in the real context. A 70 percent file-size reduction is not a win if the homepage hero looks muddy or a product detail loses texture.

Final Checklist#

Before publishing the optimized images, confirm:

• original files are backed up or still available
• resized dimensions match the layout
• WebP output is visually acceptable
• logos and icons were not rasterized unnecessarily
• fallbacks are in place where your template needs them
• cache or CDN behavior has been checked
• the site still renders correctly on mobile

For a small site, this audit can often be completed in an afternoon. The important part is discipline: inventory first, resize obvious waste, convert a representative sample, review quality, then roll out the rest. That is slower than a one-click promise, but it produces better results and fewer surprises.

Further Reading#

• Google WebP overview
• MDN image format guide