CNAME in DNS - is it a good option?

M

makecode2011-10-01 02:00:32

Domain Name System

makecode, 2011-10-01 02:00:32

Hello. There is a site. There are many pictures on the main page, more than 45. The size of the pictures is approximately 256x256.
Those. viewed as a preview in the photo gallery.

Because the browser can only pull a certain number of images (in HTTP 1.0 up to 4, 1.1 - up to 8), that is, the desire to speed up page loading.

There are no plans to buy a CDN.

Is it possible to solve the problem by writing
i1.domain.ru CNAME domain.ru

And requesting half of the images instead of
domain.ru/img.jpg
to
i1.domain.ru/img.jpg

Thus parallelize image pull.

Is this a good option? Perhaps there are any pitfalls?

Thanks a lot.

Reply

Answer the question

In order to leave comments, you need to log in

4 answer(s)

P

Puma Thailand, 2011-10-01
@opium

Throw a link to the site, I'll refactor the page load and then you can tell if it's worth posting the pictures.
It was just that there was a site whose php gave the page in about 10 seconds, and the pictures were loaded in less than one, well, they did cname, they smashed the pictures, the site still opens for 10 seconds.

K

Khurshed Nurmatov, 2011-10-01
@Hoorsh

In theory, this option should help, since browsers only look at the host, but not at the IP address. BUT! If you are really sure that the download delay is just due to the large number of pictures.
Have minimal optimization measures been carried out? Does nginx provide static?

R

RuJet, 2011-10-01
@RuJet

How will the search engines look at it?

A

Alex Babak, 2013-11-29
@Doctorrr

CSS Sprites