Page Image Audit

Enter a page address and we check up to forty of its images for file size, format, real dimensions, missing alt text, missing width and height and lazy loading, then estimate how much you could save.

Este conteúdo está em inglês.

Exemplos resolvidos

Oversized images on a homepage

https://example.com typed into the address box

(Illustrative) 12 images found, 3 of them much larger than the space they fill on screen, with an estimated saving listed for each.

Image sizes come from the files, but savings are rough estimates.

Single large photo

https://example.com/gallery typed into the address box

(Illustrative) One image of 4000 by 3000 pixels shown at 400 pixels wide, flagged as oversized with its file name.

Images added later by scripts, or set in separate stylesheet files, are not found by the audit.

Sobre Page Image Audit

A page image audit checks the pictures on a web page and tells you which ones are slowing it down or missing basic details. Enter a page address and Valtrinity finds up to forty images, including those in image tags, responsive image sets, picture elements, sharing tags and inline backgrounds. It then fetches each one and reports its format, file size and, where the file allows, its real width and height. Because the real file sizes and dimensions are read, you can see exactly which images are worth fixing first instead of guessing from how the page looks.

The report flags images with no alt text, no width and height, no lazy loading, older formats, very large files and files much bigger than the size the page declares. It estimates how much you could save by resizing and moving to WebP or AVIF, and gives an overall score with a table you can download. Savings are estimates, and images added later by scripts or set in separate stylesheet files are not found. The table can be downloaded as a spreadsheet file, which makes it easy to pass a clear list of files and fixes to a designer, developer or content editor.

Como usar Page Image Audit

  1. Enter the page address.
  2. Select Audit images and wait for the files to be checked.
  3. Read the score and the list of what to do.
  4. Sort out the largest files first using the biggest savings table.
  5. Download the CSV to share with a designer or developer.

Usos comuns

  • Finding the few large images that make up most of a page's weight
  • Checking product pages for missing alt text before a launch
  • Making sure images have set sizes so the page does not jump while loading
  • Deciding which files are worth converting to a modern format
  • Checking the sharing image that appears when a link is posted

Perguntas frequentes

How are the real image dimensions found?

The first bytes of each file contain its width and height, so the audit reads them directly. This works for PNG, JPEG, GIF, WebP, AVIF and SVG files. If a file cannot be read, the size is shown as unknown and the other checks still run.

What counts as missing alt text?

An image tag with no alt attribute at all. An empty alt attribute is treated as correct for purely decorative images, because it tells screen readers to skip them. Meaningful images such as products and diagrams should have a short description of what they show.

Why does it matter to set width and height?

When a page knows an image's size before it loads, it can reserve the space. Without that, text jumps down as each picture arrives, which is annoying and can hurt search performance. Adding width and height attributes is a quick fix.

How accurate are the savings estimates?

They are rough. They assume typical results from resizing an image to the size shown and converting older formats to WebP. Real savings depend on the picture and the quality settings you choose, so treat the figure as a guide for deciding where to start.

Why were some images not listed?

The audit looks at up to forty images in the order they appear, and only those present in the page's HTML. Images added by scripts after the page loads, or set in separate stylesheet files, are not seen. Tiny images embedded directly in the page are counted but not listed.

Should every image be lazy-loaded?

No. Images below the visible area benefit from loading=lazy, but the main image at the top should load straight away. Lazy-loading it can delay the part of the page visitors care about most, so the audit flags that case too.