Put your address in. We fetch the page, measure every image a visitor actually downloads, and show exactly what changes — on wifi, a good mobile signal, and a bad one.
Free, about five seconds, no sign-up. We don’t store the address.
One library, start to finish
A plant hire firm with fifteen years of photographs behind it — machinery shots straight off a phone, nothing ever resized. The kind of media library every agency inherits and nobody wants to open.
8,584 conversions — AVIF and a WebP fallback for every image — at an average of 205 ms each. The entire library finished in under half an hour, in the background, while the site stayed up. Figures read straight from the conversion log, not a marketing spreadsheet.
Every image on that site comes from images.brecklandplanthire.co.uk. Nothing in
the page source mentions us, and nothing in their media library was altered — the
originals sit exactly where they were.
Measured, not claimed
108 images from six unrelated client libraries, none previously optimised. Our quality was tuned down per image until it matched or beat the competitor’s fidelity — only then did we compare bytes.
Quality scored with SSIM against the original, using a harness that refuses to compare mismatched dimensions and self-tests to 1.0 before every run. Mean fidelity 0.892 against 0.862 — ours is the higher of the two.
How
Not a magic codec. Two decisions most optimisers don’t make, and one check nobody else does.
AVIF is roughly half the size of WebP at the same quality. We ship it by default, with WebP as automatic fallback for older browsers. Nobody sees a broken image.
Libraries are full of 5,000-pixel camera originals displayed at 1,200. Re-encoding those is pointless — we resize first. One 16 MB photo came out at 368 KB.
We found a competitor on a client’s site with 4,283 converted files and five being served. Peregrine only serves a format it has confirmed is retrievable from the edge.
Converted files sit alongside the originals. Turn Peregrine off and your site serves exactly what it did before. There is no destructive path.
Where we sit
An optimiser plugin shrinks files and stops there. A full-stack accelerator takes over your whole front end and charges like it. We do the delivery part properly without taking the site off you.
Categories, not a scoreboard against any one product — feature lists change and we would rather not be caught quoting an old one. The 39.5% figure above is a direct, quality-matched measurement against the market-leading optimiser, and the raw data behind it is published. If you think a column here is unfair to a tool you use, tell us and we will change it.
Getting started
Three steps, in this order. Nothing in it is hard to reverse, which is rather the point — you should not need courage to try a CDN.
A single CNAME for images.yourdomain.com on Glide. On Dive you delegate the
domain to our nameservers instead, which is what lets us cache the whole page rather than
just the assets.
It works through the library in the background while the site stays up. Breckland’s 4,542 images took under half an hour. Nothing is replaced — converted files sit alongside the originals.
A format is only served once we have confirmed that exact file comes back from the edge. We found a competitor on a client’s site with 4,283 converted files and five of them actually being served.
Reversing it is deleting the plugin. Your site goes straight back to serving what it served before, because that is still what is sitting in the library.
Pricing
No metered bandwidth and no surprise overages. Annual saves 20% and includes setup and migration.
billed annually at £84
billed annually at £228
billed annually at £144
The discount applies automatically across every site on the account — one invoice, one renewal date, add sites whenever you like.
Reseller pricing and your own whitelabelled nameservers are included from 20 sites.
For agencies
Assets serve from their domain, and on Dive your nameservers sit in front of the whole thing.
Images at images.theirdomain.co.uk. Nameservers under your brand. Block pages
with your name on them. Nothing in the page source points back at us.
ns1.youragency.com ns2.youragency.com
Per-site keys, portfolio-wide reporting, and a single annual commitment covering the lot. Adding a site provisions its storage, CDN hostname, certificate and caching rules in one step — not an afternoon of configuration.
“Everyone compresses images. We make sure they actually reach the browser.
Before you ask
Mostly variations on one thing: what happens when it goes wrong. Fair question to ask of anything sitting in front of a client’s site.
Your originals never left. They are in your media library exactly where WordPress put them, untouched, and the plugin falls back to serving them. The worst case is the site you had before us, which is a very different worst case from a service that has taken over your front end and holds the only copy of anything.
No, and we are careful about the specific way that usually happens. Cart, checkout and account pages bypass the cache entirely, and we never match on the mere presence of a cookie — that is the mistake that serves one logged-in customer’s basket to everybody. Personalised responses are never cached.
Yes. Page builders render outside the normal content filters, which is why plugins that hook
the_content quietly miss most of a builder-made page — they report
success and change nothing. We rewrite the finished output instead, so a builder page is
handled the same as any other.
Never. There is no destructive path in the product. Converted files sit alongside the originals and the plugin chooses between them at render time.
Then we keep yours. If our output is not actually smaller we say so and serve the original. An optimiser that ships a bigger file and calls it a saving is worse than doing nothing.
Only on Dive, and that is what buys you edge-cached HTML. Glide is one CNAME on a subdomain and leaves your DNS exactly where it is — you can stay with Cloudflare, your registrar or your host.
Usually not. Most site CDNs pass images through unchanged — they move the same bytes faster. The saving here comes from sending far fewer bytes in the first place. Glide sits beside an existing CDN happily; Dive replaces it.
One domain, whatever its size. A 40-page brochure site and a 12,000-product store are the same price, because our cost is compute at conversion time, not bandwidth.
Annual saves 20% and includes the migration done for you. Glide and Shield are also available monthly if you would rather not commit. Dive is annual only — delegating nameservers is a real migration and a one-month experiment does nobody any good.
Converted images sit in EU edge storage, in Germany, and are delivered from the nearest point of presence to each visitor. Original images stay on your own server throughout.
Start here
Tell us what you look after and we will come back with what it would cost and what it would save — measured on your actual pages, not an average.
Prefer email? tgf@xpose.online.