TTFB i.e. time between request being made and the start of response received is slow, which suggests either the request takes a long time to get there or the server is slow generating the response.
If you look at request 22 for example 2757ms to receive a response but only 1ms to download it (it probably fits in a single TCP packet)
Most of the images are pretty small, have you thought about using datauris or a sprite image?
I looked at Full Optimization Checklist and there are 82% compresss img and from 18 to last img are checked. Thus I thought there were compressed…
Those img are repeated img and I excluded them from sprites. At least I tried included them and applied to website but I can see other imgs in the sprite.
I did informed my host regarding TTFB and webpagetest but they told me it mostly test scripts or something like that… I asked them to reduced it without increasing the resources.
Image compression looks at JPEG images and looks for an opportunity to save bytes by compressing them FURTHER (not that they aren’t compressed at all). It is super-conservative and tries re-compressing jpeg images at a quality level of 85 which should not have any perceivable visual difference.
It seems that when I applied subdomain like images1.domain.com/mod/ to those images will make them load longer. Now I removed it and just put /mod/xxx.png…
Any reason why this happen? I thought it could help to reduce loading time but not increase them…
A new sub-domain (sharding) has some start-up cost where the browser has to do the DNS lookup and establish new connections. It usually only pays off if you have a LOT of static content that you need to serve.