W3C home > Mailing lists > Public > public-bpwg@w3.org > July 2009

Re: MWABP: general / Yahoo guidelines

From: Adam Connors <adamconnors@google.com>
Date: Wed, 1 Jul 2009 12:07:31 +0100
Message-ID: <393b77970907010407g67edcb54s7ab8187b9903f771@mail.gmail.com>
To: Eduardo Casais <casays@yahoo.com>
Cc: public-bpwg@w3.org
I did take a look at these a while ago though I will check again now that
our scope has become more focussed. For the most part, things in yahoo that
have been omitted are either very device specific (e.g. iPhone 25K limit, is
iPhone specific not even webkit and was true for first release but it's not
clear to me that it still applies to the later releases) or more technical /
low-level than feels appropriate for MWABP.

On Wed, Jul 1, 2009 at 10:35 AM, Eduardo Casais <casays@yahoo.com> wrote:

>
> The developers' site of Yahoo provides an interesting list
> of "Best Practices for Speeding Up Your Web Site":
>
> http://developer.yahoo.com/performance/rules.html
>
> Unsurprisingly, there is considerable overlap with what
> can be found in comparable guidelines from other firms,
> and with the MWABP as well. However, it is still
> instructive to look at their detailed justifications and at
> the rules that do not appear in the MWABP.
>
> There are two interesting guidelines that are specifically
> for mobile devices only:
>
> Keep Components under 25K (because, among other
> issues, the iPhone does not cache larger resources -- an
> issue I had already seen mentioned here and there; these
> 25K are as well quite compatible with usual BP for mobile
> devices).
>
> Pack Components into a Multipart Document (with the
> caveat that one must check whether the device supports
> multiparts).
>
> A quick cross-check might be in order, if it has not been
> done before.
>
>
> E.Casais
>
>
>
>
>
Received on Wednesday, 1 July 2009 11:08:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:01 UTC