Quote:
Originally Posted by yabate
No, absolutely not. They have enough http reqs so two more is just a kick in the head 
@drmadcat, i will give you some quick tips what you can do..
Your website load pretty fast for a number of requests and huge payload.
But, you can make it load faster.
Lets make it in a few steps:
1. Your first bite time is about 750ms by loading it from San Francisco, where is your website located. Its too too much. First bite time from the same city can be at 20,30ms.
Imagine only how much people from EU need to wait.
2. grab your photo http://xxxaus.com/images/top_bg.png and convert it in a JPG.
Current size: 342KB
Expected size: 56KB
Savings: 286KB
But its PNG with alpha, so you need to think of it. |
Its this png thats loading slow compared to the rest of the site, but its a png because its not a full pic, he could use the background cut into it as a JPG but even then he would need to slice it, as you do... so in which case, splitting the png into 3, 1 with each girl on, would still remain the most simplest way to deal with the header.
Quote:
Originally Posted by drmadcat
wow cheers loads of stuff to do thank you
|
png is best if you want it to remain see through, but as said, if you use the background included in the header, then JPG would be much less load. Still splice it.
You do still need to improve your ram
