Enter a page address. The checker fetches the page as served, finds the images it references and weighs each one from the server's own headers. You receive the total image payload, the heaviest files, the format mix and a grade out of 100, with fixes ranked by impact. Built for portfolio sites, where photographs decide the load time.
A note
Results remain on screen. Copying or downloading the report asks for an email once per browser. Four checks per network per day.
Why image weight decides a portfolio's speed
On a portfolio site nearly all the weight is photography. The HTML of a well-built page runs 100 to 300 KB; a single hero image exported carelessly from Lightroom is easily 4 MB, more than ten pages' worth of everything else. Visitors on a phone feel this directly: at the 1.6 Mbps of a modest mobile connection, 6 MB of images is roughly thirty seconds of blank screen.
Two repairs move most of the number. Modern formats (AVIF and WebP) carry the same visual quality as JPEG at roughly half the bytes, often less. And responsive delivery through the srcset attribute lets a phone download an 800 pixel version while a large display receives the full frame, so no device pays for pixels it cannot show.
The grade weighs total payload at 40 points, formats at 20, delivery at 20, and care (alt text and reserved dimensions) at 20.
What the checker reads, and what it cannot
The checker reads the page exactly as your server sends it: img tags (choosing the srcset candidate a phone-sized screen would load, about 800 pixels wide), inline background-image styles and preloaded images. It weighs the first 24 it finds using HEAD and range requests, so nothing is downloaded in full and your bandwidth is undisturbed.
It cannot see images that scripts inject after load, galleries rendered by JavaScript, or backgrounds set in external stylesheets. If it reports far fewer images than the page displays, your gallery is script-rendered; the images it does find are still the ones a search crawler and the first paint see. Sizes come from each server's own headers, and a handful of hosts decline to state them.
Frequently Asked Questions
How heavy is too heavy?
Useful budgets: keep a page's total image payload under 2 MB and any single image under 300 KB, with the hero allowed up to 500 KB when it earns its place. The grade's top band sits at 1 MB total, which a portfolio page in AVIF at sensible dimensions reaches comfortably.
Which version of a responsive image is measured?
For images with srcset, the candidate closest to 800 pixels wide, roughly what a phone downloads. Fixed src images are measured as served. The desktop variant of a well-built responsive image can be larger without harm, because only large screens receive it.
Why does it find fewer images than I can see?
Galleries injected by JavaScript are invisible to a plain fetch of the HTML, and so are backgrounds defined in external stylesheets. The checker sees what a search crawler and the first paint see. A count near zero on an image-rich page is itself a finding: your photography is invisible until scripts run.
What are AVIF and WebP?
Newer image formats that every current browser displays. At like-for-like visual quality they are commonly 30 to 60 percent smaller than JPEG. Export tools and CDNs can produce them automatically, and the picture element with srcset lets you keep JPEG as a fallback.
Is the checker complimentary?
Yes, within daily limits: four checks per network per day. Results stay on screen; copying or downloading the report asks for an email once per browser.
Most image problems are pipeline problems: exports at print resolution, formats chosen a decade ago, a theme that never learned srcset. They are fixed once, in the build, and every page benefits. If the grade reads C or worse and the site matters commercially, inquire and attach the report. To see how the whole site measures beyond its images, run the Luxury Web Index Grader next.
In the garden of time, we'll soon meet Your aspiration, like a seed, has taken root Our response, like a bloom, shall shortly greet.
A fleeting error has crossed our path, please, try once more
Correspondence
Discover the marketing and client acquisition strategies behind top architects. Monthly emails, unsubscribe anytime.
Thank you, we look forward to sharing our insights with you.
