5 articles
Blog
Image weight, formats and delivery, with the measurement method and its limits beside each result.
Blog
Image weight by platform: 41 stores measured
We measured image bytes on 41 real storefronts across 14 platforms. WooCommerce sent 2.7 times more bytes per pixel than Shopify.
Read
Blog
WooCommerce slow? Images fix the storefront, not checkout
A slow WooCommerce storefront may be carrying heavy images. A slow checkout is usually code or the database. We measured one, not the other.
Read
Blog
Why is my WordPress site so slow? The images, measured
Slow WordPress? Plugins get checked first. Images rarely do. Weigh yours, see if they are the problem, and learn what the fix changes.
Read
Blog
“Serve images in next-gen formats”: what it means now
Lighthouse renamed this image audit. Here is what it measures, what it estimates, and how to check the image bytes on your own page.
Read
Blog
Hit Optimole's visit limit? What happens next
On Optimole's free plan, optimized delivery can stop. Paid plans upgrade automatically. Here is what their docs say and how to recover images.
Read
This is the NimboCDN blog: everything we have measured about how images get delivered on the web. An image CDN sounds like one thing — your images, smaller, in the right format for every visitor — and the interesting part is everything that statement hides. What exactly gets resized, who pays for the bandwidth, what happens when a plan runs out: each piece here takes one of those questions and answers it with numbers you can check.
Every claim carries its measurement. When a piece says a format weighs less, it is because the same image was encoded both ways and the bytes are in the article. When it describes a competitor's limit, the quote comes from their own documentation, dated and linked. Nothing is «up to»: if we could not measure it, we did not write it.
Articles go newest first. If you are deciding between tools, the comparison pieces live under Alternatives; everything here is about the delivery itself — how it works, what it costs, and how to tell whether it is working.
New pieces appear when there is something to measure, not on a calendar: a question from a customer, a change in a competitor's plans, a format the network starts serving to more browsers. The RSS feed of this blog carries every piece the day it goes out: /feed.xml in English, /es/feed.xml and /pt/feed.xml in the other two languages.
Everything is signed: the byline links to the author's page, with what they work on. When a number turns out to be wrong, the correction goes into the article with its date and its reason — the same standard we ask of the competitors we quote.
How to read a piece here: every claim carries its source at the bottom — the pricing page, the plugin directory, the API response, each with the date we read it and how. If a number matters to your decision, click its source: we would rather you verify us than trust us. And when something could not be verified first hand, the piece says so instead of rounding it into a claim.
Nothing here is evergreen by accident: each piece is re-checked on a review date printed next to the byline, and the sources are re-read then. A number that no longer matches its source gets corrected with the date and the reason — not quietly replaced. A blog about measurement owes you the measurements.