omry at yadan.net
Tue Sep 18 20:34:56 GMT 2007
This is not true because of browser cache.
besides, you need to look at the bigger picture:
how much you are effecting the entire size of data a user gets when
for example, if your entire front page is 200k including images and
save 50%, you saved 5%.
provided by library authors.
Computer Guru wrote:
> Just my two cents:
> I think it is pretty illogical to not do something just because it "might
> not be as effective" as other things that aren't mutually exclusive.
> Hell, if it's just a 1% difference w/ minification + gz compression +
> bundling vs just gz compression... That's 1% TIMES xx MILLIONS of requests
> to your blog === LOTS of bandwdith saved!
> And in this case, it's more than that, seemingly a lot more. But even if it
> isn't, I don't think that's a good excuse.
> On 9/18/07, Charles <lists07 at wiltgen.net> wrote:
>>>> server-side text compression and (3) file-combining is the norm,
>>>> more serious than roll-overs.
>>> 1 and 3 are useless in most (not all, mind you) cases.
>> I'm not sure how you arrived at that conclusion.
>> Check out this chart to understand how server-side text compression and
>> Combining files when possible is almost always a good idea for deployed
>> apps, since (1) HTTP requests are relatively expensive and (2) browsers
>> typically limit themselves to two parallel downloads per hostname.
>> -- Charles
>> introducing new bugs during the minification process "compressors". Not
>> everyone makes the distinction.
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
More information about the wp-hackers