Skip to main content

Bandwidth savings only.

Savings calculator

Faster load times and better Core Web Vitals are upside this calculator doesn't count.

AWS CloudFront, GCP, Azure typically $0.05–$0.12/GB

The software is free on every site and every server — the count only sizes the bandwidth math.

Your estimated savings

Annual savings

—

ROI

—

Illustrative estimate, not measured product output. We measure 48–69% page-weight reduction across our demo pages; this calculator uses a conservative 60%. Actual savings depend on your content mix, original image formats, and quality settings.

Show methodology — monthly breakdown

Current monthly bandwidth

—

Optimized bandwidth

—

Bandwidth saved

—

Monthly bandwidth savings

—

Monthly software cost (open source)

—

Net monthly savings

—

Illustrative LCP improvement: ~40% faster — an estimate derived from the assumed 60% page-weight reduction, not a measured product output. Industry studies (Google, Deloitte) report that a 100ms improvement in load time can lift conversions by roughly 1–2%.

Bandwidth comparison

Before optimization —
After optimization —

The software is free — the savings above are all net.

Beyond bandwidth savings

This calculator counts bandwidth cost alone. The rest of the return on image and CSS/JS optimization is harder to price, and larger:

  • • Better Core Web Vitals — Smaller pages load faster, improving LCP and reducing CLS. Google uses CWV as a ranking signal. That means this impacts your revenue, not just your metrics.
  • • Higher conversions — Industry data shows every 100ms of load time improvement can increase conversions by 1–2%.
  • • No engineering time — No build pipeline, no manual srcset, no image optimization workflow. Automatic and continuous.
  • • Free software vs. CDN usage fees — mod_pagespeed costs nothing regardless of traffic or server count. CDN and image-CDN optimization (Cloudflare Business $200/mo per site, Cloudinary usage-based) scales with your bill.

The estimate above counts image and CSS/JS savings from the variant-aware cache in mod_pagespeed. The optimizer worker does that work off the request path; the in-process module inside Apache and nginx minifies CSS/JS and transcodes images to WebP on the same pagespeed directives your configuration already uses. The IIS package ships as a signed installer on the mod_pagespeed GitHub release. See the optimizations side by side on the filter examples, or read the case for self-hosted image optimization.

Search