JPEG Website Image Audit Checklist: Fix Size, Quality, and Naming Problems Before Launch

Overview

A good JPEG website image audit is not simply a search for the smallest possible file. The goal is to balance visual clarity, loading efficiency, responsive presentation, and an organized publishing workflow. An image can be technically sharp but too large for its display area, or lightweight but damaged by visible compression artifacts. It can also look correct in an image editor and appear different in a browser because of color-profile handling, overlays, or responsive cropping.

Start by creating a review list containing the file name, intended page, image role, display dimensions, source location, and approval status. Separate images by use case: hero images, article or editorial images, product photos, thumbnails, logos, and decorative backgrounds. Each group may need different dimensions and quality settings.

Keep an original master outside the web-ready folder. Export a separate JPEG for the website, and avoid repeatedly opening and resaving that export. If the image includes transparency, a JPEG is usually not the appropriate format because JPEG does not preserve transparent areas. If sharp text, flat-color graphics, or transparency are central to the asset, compare another suitable format during your workflow rather than forcing every image into JPEG.

For a broader file-management system, see How to Organize a Reusable JPEG Asset Library for Brand and Client Projects.

Checklist by scenario

Before a new website launch

• Confirm display dimensions: Check the largest expected rendered size, including high-density displays where relevant. Do not upload a very large camera original when the page never displays it at that scale.
• Review responsive crops: Check the image on narrow and wide layouts. Confirm that faces, products, text within the image, and other important focal points remain visible.
• Export consistently: Use a repeatable quality setting and naming pattern for the project. Compare a representative sample at normal viewing size rather than judging only at extreme zoom.
• Check file weight: Flag unusually large files for closer review. A single oversized hero image can have a disproportionate effect on a page, especially on slower connections.
• Inspect the publishing destination: Confirm that the CMS, theme, or component will not create an unexpected crop, upscale a small image, or strip useful image information during upload.
• Prepare descriptive text: Write useful alt text for meaningful images and mark purely decorative images appropriately in the publishing system. Alt text should describe the image's purpose in context, not repeat its filename.

Before a campaign or seasonal upload

• Confirm that the image matches the current offer, date, product, or campaign message.
• Check every variant for consistent color, crop, logo placement, and visual hierarchy.
• Remove superseded exports from the upload batch so an editor does not select the wrong version.
• Use a temporary review folder, then move only approved files into the final web-ready folder.
• Verify that filenames distinguish sizes or placements, such as linen-shirt-sand-product-card.jpg and linen-shirt-sand-mobile-hero.jpg.

During a quarterly media-library audit

• Locate duplicate files, near-duplicates, obsolete campaign images, and files with unclear ownership or usage notes.
• Identify images that are repeatedly being resized or cropped by the CMS and create better source variants where needed.
• Check whether important pages still reference missing, blurry, or outdated images.
• Review filenames and folder structure so another contributor can find approved assets without opening every file.
• Record decisions in a simple audit log: keep, replace, archive, or delete.

What to double-check

Dimensions and quality

Measure an image against its actual role, not against a generic “large enough” rule. A full-width hero, a card thumbnail, and a detail-page product image have different requirements. Inspect the smallest important detail after the intended crop. If a product label or facial feature must remain readable, test the image in the component where it will appear.

Compression should be judged visually. Look for block patterns in smooth areas, smeared fine detail, halos around strong edges, and color banding in gradients. When an export looks poor, do not solve the problem by blindly increasing quality on an already damaged file. Re-export from the cleanest available source.

Filenames and metadata

A useful filename identifies the subject and, when necessary, the placement or variant. A practical template is subject-context-variant.jpg, for example ceramic-mug-blue-product-detail.jpg. Keep words lowercase, use hyphens, remove camera-generated strings, and avoid adding dates unless they help distinguish a genuinely time-specific asset. File names support handoff and library management, but they do not replace accurate alt text or a clear page context.

Before sharing files externally, inspect metadata for information that should not travel with the image. The JPEG Metadata and Privacy Checklist provides a separate review path for that task.

Common mistakes

• Optimizing only by file size: The smallest export is not automatically the best choice. Review clarity, crop, and purpose together.
• Uploading one image for every layout: A single image may be cropped badly or delivered at an inefficient size across different components.
• Repeatedly recompressing JPEGs: Keep a clean source and produce final exports from it whenever changes are needed.
• Trusting the filename alone: A descriptive name helps organization, but it does not provide accessible image information by itself.
• Ignoring duplicate variants: Files named “final,” “final2,” and “latest” create selection errors. Use a clear approval convention and archive superseded versions.
• Checking only on a desktop monitor: Review representative narrow and wide layouts, including the actual crop and surrounding text.
• Forgetting background behavior: A JPEG used as a background may be covered by overlays, positioned differently, or cropped more aggressively than an inline image.
• Changing tools without retesting: Export applications, CMS settings, and image-processing steps can alter dimensions, metadata, or color appearance. Compare a sample after workflow changes.

For hero-specific decisions, use the Website Hero Image Art Direction checklist. For compression choices, refer to the JPEG Compression Guide.

When to revisit

Run this website image preflight checklist before every major launch and campaign upload, not only when a page looks broken. Revisit it after changing a CMS, theme, image optimizer, hosting setup, responsive component, or export application. A workflow that worked for one template may produce poor crops or unnecessarily large files in a new layout.

Quarterly media-library reviews are useful for active sites with frequent publishing. Seasonal planning is another natural checkpoint: archive expired campaign assets, approve current variants, and confirm that shared folders contain only files contributors should use. Also audit after a brand refresh, product catalog change, or migration between systems.

Use this final action list before publishing:

1. Gather the exact JPEGs that will be uploaded.
2. Group them by page role and responsive placement.
3. Check dimensions, crop, sharpness, artifacts, and color in context.
4. Remove duplicates and confirm that each filename is descriptive and stable.
5. Review alt text and decorative-image treatment in the CMS.
6. Compare file weight with visual quality and replace inefficient outliers.
7. Preview the page at representative widths and record any corrections.
8. Archive the approved batch and retain the clean source files separately.

For image search and publishing details, continue with the JPEG Image SEO Checklist. Treat the audit as a repeatable asset workflow rather than a one-time technical task, and each launch should become easier to review.