Pre-Launch Self-Check: Image & Static Asset Optimization

The key to image optimization isn't how small you compress — it's whether you're delivering the right file for the actual use case. Six check groups below, take…

Insights:Pre-Launch Self-Check: Image & Static Asset Optimization

I. Size Check

  • What is the actual display width of each image.
  • Whether the pixel width of images is close to the display width (including 2x images).
  • Whether list thumbnails reuse large images.
  • Whether there are any non-essential images exceeding 2000px in width.

Judgment: Single images over 300KB that are not above-the-fold hero visuals can typically be optimized.

II. Format Check

Content Expected Format
Photos WebP (or JPEG as fallback)
Icons / Logo SVG
Transparent images PNG or WebP
Screenshot WebP/PNG

Check for obvious mismatches such as “save photo as PNG.”

III. Quality Check

  • Is the photo quality within the 75–85 range.
  • Are there obvious color banding or blur after compression.
  • Were images compared one by one (instead of uniformly compressed to the lowest setting).

IV. Loading Strategy

  • Whether above-the-fold images are not lazy-loaded.
  • Whether below-the-fold images have lazy loading enabled.
  • Whether all images declare width/height.
  • Whether the hero image on the first screen has a higher priority.

V. Cache & Versioning

  • Whether static assets are set with long-term caching.
  • Whether image filenames include a hash or version number.
  • Whether CDN rules are synchronized.
  • Whether updated images use new filenames.

VI. Availability

  • All images are accessible with no 404 errors.
  • Alt text is provided — descriptive of the content, not generic labels like "image1".
  • No blurriness or distortion on mobile displays.
  • No visual anomalies in dark mode or across different screens.

Verification Methods

  • Open the page and inspect total transfer volume via browser DevTools.
  • Compare first-screen load time before and after optimization.
  • Sample-check clarity of 10 images at various resolutions.

Common Oversights

  • Only the homepage was optimized; inner pages still serve original files.
  • Originals were deleted after compression, making it impossible to generate 2x-retina variants later.
  • Format conversion done without renaming files, so visitors still load the old images.
  • No explicit width/height set on images, causing layout shift during loading.

Boundary

This checklist ensures images don't become the bottleneck, but image optimization cannot fix a slow server. If the first screen is still sluggish, start by examining TTFB and cache-hit rate.

Related Reading: