Image size and http requests

  • Hi,
    I am using a lot of svgs on my website but unfortunately the svgs with paths are quite large in size, even when run through a compressor tool.
    I wanted to combine 3 small images in order to reduce http requests but then I noticed that the combined image is much larger than the three small images together(300kb vs 200kb). So would it still make more sense to combine them so that I have less http requests or is the end size more important?

    Thank you for your help.

Viewing 2 replies - 1 through 2 (of 2 total)

  • It is definitely beneficial to minimize the number of http requests being sent. Many people put all of their site images on a single image file (using Photoshop or some other photo editing software). Then, there is only one http request for all images on the site (referred to as “CSS Sprites”).

    In this case; I would probably reduce the http requests and go with the single file. Even though it is slightly larger in size; I think reducing two http requests is better.

    You can always optimize the “combined” image, for the web. If you go to a site like GTMetrix; and read through the stats, you’ll see links where you can get an optimized image of all images on your site (with file sizes; and how much space can be saved).

    Thread Starter kustv

    (@kustv)

    Thank you for your reply. I knwo sprites are recommended, but I have no idea how to implement these as I am a beginner…also, some of my images are svg and some are png or jpg, so not sure how that would work.
    I am already compressing through Tinypng or compressor/kraken.io, are there better/additional options?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Image size and http requests’ is closed to new replies.