All image assets need to be loaded for home page (not the case where each image is for a different page).

If I understand correctly, if each image gets stored in a different bucket Object, then we are opening a new HTTP connection for each download.

Will it be faster if I store all SVGs within the same object?

Is it worth considering gzip compression? (or any other kind of compression?)

  • 2
    S3 buckets can each store tons of files. Why would you consider creating a new bucket for each file? Aug 31, 2021 at 21:22
  • 3
    Any chance you could use CloudFront? It automatically handles connection multiplexing and compression, via http/2 and on-the-fly gzip respectively. So all your SVG files would be served over the same TCP connection. You can use S3 as a source for CloudFront. Aug 31, 2021 at 21:25
  • 1
    I said bucket object, not bucket. I have never considered creating one bucket per image. Aug 31, 2021 at 21:34
  • 3
    It looks like "object" is Amazon's terminology for "file". >:( Sep 1, 2021 at 11:31

1 Answer 1


I ended up creating a composite SVG Sprite which plays well with CSS and other style post-processors. Size is very small and eliminates the overhead for more than one single HTTP request per page.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.