images.tooling.report

Offers content via HTTP2

Can we access content via HTTP2+?

    a child looking into a telescope, pointed upwards

    Introduction

    As images take up a majority of the bytes transferred online, the optimizations offered by HTTP2 are often clearly highlighted. Features like multiplexing header compression, and server push all mean that images can be rendered that much faster. Any network based image optimization service should be able to respond over H2 to make sure site’s can be as fast as possible.

    The Test

    Examine the protocol used to respond to the image request

    Conclusion

    akamai
    bigCartel
    cloudflare
    cloudinary
    ecwid
    fastly
    goDaddy
    imageEngine
    imaginary
    imgix
    imgproxy

    Since imgproxy is self hosted, it is up to you to serve it via HTTP2+. Therefore, this is not applicable.

    optimole
    shopify
    shortPixel

    ShortPixel Image Optimizer (the plugin being tested) serves images from your own WordPress server, it is up to you to serve it via HTTP2+. Therefore, this is not applicable. ShortPixel does have an API, that is available via HTTP2+.

    smush

    Since Smush serves images from your own WordPress server, it is up to you to serve it via HTTP2+. Therefore, this is not applicable.

    squarespace
    thumbor

    Since thumbor is self hosted, it is up to you to serve it via HTTP2+. Therefore, this is not applicable.

    webflow
    weebly
    wix
    Effective-Connection-Type
    Does it respond to the ECT (Effective Connection Type) header?
    Long-lived cache headers
    Is content produces served with long-lived cache headers?