Summary Card Image Proxy bloats image size from 11kB to 72kB


#1

I’m experimenting with “summary cards with large images”, and I noticed the twimg.com proxied image is about 7 times larger than the original image. Is it possible to avoid this overhead? Here’s some background information:

web page in question: http://creditcardjs.com
original image url: http://creditcardjs.com/s/twitter-summary-card.min.png
original image file size: 11kB
proxied image url: https://o.twimg.com/2/proxy.jpg?t=HBg2aHR0cDovL2NyZWRpdGNhcmRqcy5jb20vcy90d2l0dGVyLXN1bW1hcnktY2FyZC5taW4ucG5nFOQGFIIFABYAEgA&s=sr4XO2zSm7vsSNTw0RXgMT_LeJvyJwJtIKuFlbuLFIw
proxied image file size: 72kB

Thanks


#2

First things first: the image URL in the card metadata is incorrect: it’s not http://creditcardjs.com/s/twitter-summary-card.min.png but http://creditcardjs.com/s/twitter-summary-card-min.png (not “.min.png” but “-min.png”).


#3

Hi Vincent,

The url variation is an earlier typo that should no longer be affecting the twimg proxying. The current card metadata on my home page points at the correct “.min.png” url, and twimg.com successfully proxies the image.

When I still had this typo in the card metadata, I could not even reach the Card Validator step that displayed the proxied image (because the typo url returned 404).


#4

Any updates? Regardless of the details of my specific metacard setup, it’s clear that the proxied image is significantly larger than the original image. I know this is easier said than done, but ideally the twimg proxy could just proxy the original image verbatim if image postprocessing increases file size.


#5

Sorry for the delay. Unfortunately, our image proxy does some processing on our side that appears to be increasing the size. We can raise to the team here, but unlikely for a quick fix soon.


#6

Hi Ryan, I would appreciate if you forwarded this to the dev team. Thanks for your help.