How do I check the size of images on a website?

Paste the page URL into the MiniFiles website image analyzer: it lists every image in the page's HTML with its file size and estimates how much compression would save. Manually, you can use Chrome DevTools → Network → Img and sort by size.

Is there a free image optimization checker?

Yes. The MiniFiles website image analyzer is free: 2 websites a day without an account and 5 with a free account. It also runs Google PageSpeed Insights and can produce a PDF report.

What is a good total image size for a web page?

There's no fixed rule, but on most pages keeping all images under 1–2 MB, and each photo under about 200–300 KB at its displayed size, gives fast mobile loading.

Will compressing images improve my PageSpeed score?

Usually, especially when the LCP element is an image. How much the score moves depends on everything else on the page, such as scripts and fonts, so the analyzer shows your current PageSpeed result alongside the image savings.

Can I analyse a whole website?

With Pro, yes: the analyzer scans up to 200 pages from the sitemap, compresses each image once and ranks pages by potential savings, with a ZIP of all optimised images.

Why does the checker find no images on my site?

Your site probably loads its images with JavaScript or as CSS backgrounds, which aren't in the initial HTML. Use Chrome DevTools → Network → Img to see them.

Website Image Checker: Find Oversized Images on Any Site

Why oversized images matter

Images are usually the heaviest part of a web page. A single unoptimised hero photo straight from a camera or stock site can weigh 2–5 MB, more than all the page's HTML, CSS and JavaScript combined. On a mobile connection that means seconds of loading, and the largest image on screen is very often the page's LCP element, one of Google's Core Web Vitals. PageSpeed Insights flags it as "Improve image delivery". Lighter images load faster, improve LCP and use less of your visitors' data.

How to check a website's images in one step

Open the website image analyzer. 2. Paste the page URL (your homepage, a product page or a blog post) and start the analysis. 3. While Google PageSpeed Insights tests the page on mobile, MiniFiles lists every image in the HTML and reads its size. 4. A sample of the images is compressed in your browser with the same engines as MiniFiles' image tools, and the savings for the rest are estimated from that sample and labelled as estimates. 5. Review the heaviest images, the LCP result and the total image weight now versus after optimisation. 6. Download a one-page PDF report to share with your developer or client. Without an account you can analyse 2 websites a day; a free account raises it to 5.

How to read the results

Total image weight: the sum of all images in the page. On most pages, anything above 1–2 MB of images is worth fixing.
Heaviest images: sorted by size. One or two large photos often account for most of the weight; start there.
Estimated savings: how much smaller each image gets after compression, and the page total.
PageSpeed score and LCP: Google's mobile test and which element is the LCP. If the LCP is an image, compressing it has the most direct effect on that metric. If it's text or a video, image compression won't fix it, and the analyzer says so.
Format: PNG photos and uncompressed JPEGs are the usual culprits; WebP is typically the smallest for photos.

Checking a whole site, not just one page

Problems rarely live on one page: blogs and shops repeat the same oversized thumbnails and banners everywhere. With Pro, the analyzer reads the site's sitemap (or the page's links), scans up to 200 pages, compresses each image once and ranks pages by what they would save, so you know which templates or posts to fix first. You can then download every optimised image at full size, one by one or as a single ZIP, keeping the original format so you can swap files without touching your code, or converting to WebP when it's smaller.

Free manual alternatives

PageSpeed Insights / Lighthouse: run the test and open "Improve image delivery" to see images with estimated savings. Good for one page; it doesn't give you the optimised files.
Chrome DevTools: open DevTools → Network, filter by Img, reload and sort by size. Accurate and free, but manual and per page.
Right-click → Open image in new tab: quick check of a single image's dimensions; the size appears in DevTools or when you save it.

The analyzer combines these: it lists and sizes every image, runs PageSpeed, and produces the compressed versions in one place.

What the image checker can't see

The analyzer reads the images present in the page's HTML. Images injected later by JavaScript (common in single-page apps built with React or Vue), CSS background images and SVGs aren't included, and images larger than 4 MB are skipped. If a site builds all its content with JavaScript, the analyzer may find few or no images; in that case use the DevTools method above.

How to fix the oversized images you find

Resize images to the largest size they're actually displayed at: a 4000 px photo shown at 1200 px wastes most of its bytes. 2. Compress them: for photos, JPEG or WebP at around 75–85% quality is visually identical on screen. 3. Use WebP where your site supports it; see how to convert JPG and PNG to WebP. 4. Lazy-load images below the fold, but not the LCP image. 5. Compress new images before you upload them, for example with Compress image, which runs in your browser. For the full workflow, read how to compress images for website speed.

Is my site's data stored?

The page and its images are fetched only to run the analysis and aren't stored. MiniFiles keeps just the domain name to count how many websites have been analysed. The URL is sent to Google PageSpeed Insights for the performance test. Images you compress yourself with MiniFiles' tools never leave your browser.