W3C home > Mailing lists > Public > public-web-perf@w3.org > November 2013

Re: [resource hints] preconnect, preload, prender

From: Ilya Grigorik <igrigorik@google.com>
Date: Thu, 21 Nov 2013 14:48:14 -0800
Message-ID: <CADXXVKrH3q6JNEbXCx5KUuVQ9sO650GjDJ0TOygyEyyD_RFx5g@mail.gmail.com>
To: Jonny Rein Eriksen <jonnyr@opera.com>
Cc: public-web-perf <public-web-perf@w3.org>
On Thu, Nov 21, 2013 at 1:53 AM, Jonny Rein Eriksen <jonnyr@opera.com>wrote:

> Does the order of tags indicate importance, or should there be other ways
> of indicating priority? Does that change if injecting hints through js?
>

I don't think the order should matter -- the type should determine
priority. Just because one <script> tag is above another in the doc doesn't
give it higher priority (short of just being parsed earlier), I think same
should apply for hints. When creating a hint via JS, setting the type
attribute should set its priority.


> Could the hints also be used on subsequent loads to improve performance?
>

You mean preloading assets for next navigation? If so, both <link
rel="preload" lazyload> and <link rel="prerender"> are exactly that...


> Would this be better than hints the browser could generate/store itself?
>

The browser should do as much as it can on its own. BUT, there are cases
where the app developer has specific app knowledge based on navigation
patterns, type of user, etc., and that's what these hints are for. In
short, we need both. It's not either/or.
Received on Thursday, 21 November 2013 22:49:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:37 UTC