Change​.​org: Stop Wasting 15% Bandwidth and Blurring Our Images

The Issue

🚩 The Problem
As the manager of the petition for violence victims (change.org/gewalthilfe-alle), I rely on powerful visuals to rally support. However, I discovered that Change.org’s automated image processing degrades quality while wasting bandwidth.

My technical analysis of the HTTP headers and image files reveals an inefficient "double-compression" workflow:

  1. The Upload: I uploaded a high-quality, sharp JPEG (100% quality, ~591 KB) exactly to their specifications (1200 by 675 pixels).
  2. The Flaw: Instead of efficiently converting this high-quality source, the system appears to compress it down to a low-quality intermediate file (~90 KB) before processing it again.
  3. The Result: The final image served to visitors is ~72 KB and visibly blurry.

The Waste: I tested the optimal compression manually. If I take the original image and scale it to the exact same display size (800 by 450 pixels) using standard WebP settings, I get a sharper image that is only ~62 KB.

The Scale: Change.org’s current approach is ~15% larger than the higher-quality optimized solution. Across millions of petitions and views, this "bloat" represents a massive, unnecessary waste of server bandwidth and electricity.

🔑 The Solution
The fix is technically simple: Change.org needs to update its "Cloudflare Polish" configuration or image ingestion pipeline to compress only once.

I have already provided the Support Team with the technical evidence (HAR file) and solution (with comparison images). However, they refused to escalate the issue further, stating that image optimization settings are "applied globally and can't be modified".

We are calling on Change.org’s engineering leadership to: Update the global image compression settings.

🌏 Why is this relevant?

  • Campaign Impact: Blurry images reduce trust. Petition starters work hard to create professional content; the platform shouldn't ruin it.
  • Environmental Responsibility: Transferring data consumes energy. Wasting ~15% bandwidth on unnecessary file bloat contradicts the sustainability goals of a modern tech platform.
  • Platform Integrity: Change.org exists to empower people to fix broken systems. It is ironic that they are currently refusing to fix their own broken system when presented with a clear solution.

📚 Sources & Evidence

  • Case Study: See the blurry header image at change.org/gewalthilfe-alle and many more petitions on this platform.
  • Technical Proof: Analysis of HTTP response headers (cf-polished) confirms the double-compression workflow.
  • Support Response: Change.org Support Team wrote on Dec 20, 2025, that settings are global and will not be changed despite the quality loss.

📢 Sign now and share the petition so that action must be taken!

avatar of the starter
Christoph KöpernickPetition StarterDigital Management MSc., International Media and Computing BSc.

3

The Issue

🚩 The Problem
As the manager of the petition for violence victims (change.org/gewalthilfe-alle), I rely on powerful visuals to rally support. However, I discovered that Change.org’s automated image processing degrades quality while wasting bandwidth.

My technical analysis of the HTTP headers and image files reveals an inefficient "double-compression" workflow:

  1. The Upload: I uploaded a high-quality, sharp JPEG (100% quality, ~591 KB) exactly to their specifications (1200 by 675 pixels).
  2. The Flaw: Instead of efficiently converting this high-quality source, the system appears to compress it down to a low-quality intermediate file (~90 KB) before processing it again.
  3. The Result: The final image served to visitors is ~72 KB and visibly blurry.

The Waste: I tested the optimal compression manually. If I take the original image and scale it to the exact same display size (800 by 450 pixels) using standard WebP settings, I get a sharper image that is only ~62 KB.

The Scale: Change.org’s current approach is ~15% larger than the higher-quality optimized solution. Across millions of petitions and views, this "bloat" represents a massive, unnecessary waste of server bandwidth and electricity.

🔑 The Solution
The fix is technically simple: Change.org needs to update its "Cloudflare Polish" configuration or image ingestion pipeline to compress only once.

I have already provided the Support Team with the technical evidence (HAR file) and solution (with comparison images). However, they refused to escalate the issue further, stating that image optimization settings are "applied globally and can't be modified".

We are calling on Change.org’s engineering leadership to: Update the global image compression settings.

🌏 Why is this relevant?

  • Campaign Impact: Blurry images reduce trust. Petition starters work hard to create professional content; the platform shouldn't ruin it.
  • Environmental Responsibility: Transferring data consumes energy. Wasting ~15% bandwidth on unnecessary file bloat contradicts the sustainability goals of a modern tech platform.
  • Platform Integrity: Change.org exists to empower people to fix broken systems. It is ironic that they are currently refusing to fix their own broken system when presented with a clear solution.

📚 Sources & Evidence

  • Case Study: See the blurry header image at change.org/gewalthilfe-alle and many more petitions on this platform.
  • Technical Proof: Analysis of HTTP response headers (cf-polished) confirms the double-compression workflow.
  • Support Response: Change.org Support Team wrote on Dec 20, 2025, that settings are global and will not be changed despite the quality loss.

📢 Sign now and share the petition so that action must be taken!

avatar of the starter
Christoph KöpernickPetition StarterDigital Management MSc., International Media and Computing BSc.
Support now

3


The Decision Makers

Change.org
The world's platform for change
Petition updates