Image file size LARGER than original on server

I have a site that somehow is serving images at a way larger filesize than the original on the origin server.

For one example I have 758 x 503 px image that is 78.3 kb being served from cloudflare at 373.88 kb. The initiator is imageset, it’s served though HTTP2 and it’s a recent cache of the original file which I’ve verified as being on the server at the 78.3 size.

It’s called with an initiator of imageset, other times is lazy-imageset.

Really stumped here?

I use ezoic that uses cloudflare but specifically don’t get images resized/server through their servers as adblockers then block images.

Raw header data

HTTP/2 200 OK
date: Sat, 24 Apr 2021 21:08:47 GMT
content-type: image/jpeg
cache-control: max-age=2592000
display: staticcontent_sol, staticcontent_sol
etag: W/"60351bb6-5d26b-gzip"
last-modified: Sat, 24 Apr 2021 15:05:14 GMT
response: 200
strict-transport-security: max-age=15552000; includeSubDomains; preload
vary: Accept-Encoding
vary: Accept-Encoding,User-Agent,Origin
x-content-type-options: nosniff
x-ezoic-cdn: Hit ds;mm;4c954e4b1380b3760bf6afc070591d19;2-155440-3;325f9203-8430-452b-6237-1e3fdcc8707d
x-frame-options: SAMEORIGIN
x-middleton-display: staticcontent_sol, staticcontent_sol
x-middleton-response: 200
x-runcache-type: native
x-xss-protection: 1; mode=block
cf-cache-status: HIT
age: 3
cf-request-id: 09a74fbfd40000e658c60e4000000001
expect-ct: max-age=604800, report-uri=""
report-to: {"endpoints":[{"url":"https:\/\/\/report?s=%2F2PIMObVbD1HZP8yju3jXPekEpNDiwsZqH0b91zJXo89cnAEPrHNo7OWNI4%2Fj1A1fZhWBH8j32%2BBVITvc6gFgZY8AL%2Bher6yvM%2F%2BGZEjZ32ZrxUN"}],"group":"cf-nel","max_age":604800}
nel: {"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 64524f12ec74e658-LHR
alt-svc: h3-27=":443"; ma=86400, h3-28=":443"; ma=86400, h3-29=":443"; ma=86400
X-Firefox-Spdy: h2

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.