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

Re: [resource hints] preconnect, preload, prender

From: Tony Gentilcore <tonyg@google.com>
Date: Wed, 20 Nov 2013 17:01:03 -0800
Message-ID: <CANvLf_Gjidv1nwHxNOzZ=tm2GQahod82=XQAknM3261+y0SA0g@mail.gmail.com>
To: Ilya Grigorik <igrigorik@google.com>
Cc: public-web-perf <public-web-perf@w3.org>
I love this proposal and think we should consider it in the group.
Jatinder, any thoughts from your end?

Some questions/thoughts on the specifics:
* Does <link rel="preconnect"> need a new attribute to indicate how
many connections to open? Or would the author just include the tag
multiple times if they want multiple connections?
* Does <link rel="preload"> do anything different than the <link
rel="subresource">[1] that chrome already supports?
* The part about prerendering things other than HTML is brilliant.
Could it parse CSS and compile JS as well? If so, does it need a more
general name?


[1] http://www.chromium.org/spdy/link-headers-and-server-hint/link-rel-subresource

On Mon, Nov 11, 2013 at 9:06 AM, Ilya Grigorik <igrigorik@google.com> wrote:
> Unfortunately won't make it to TPAC in person but seeing "prerender" topic
> on the agenda would like to share some thoughts on where I'd love to see the
> effort go in the coming year...
> Specifically, I think the platform is missing some critical primitives that
> can allow the site/app developers help the browser perform speculative
> optimization: preconnects, preloads, prerenders. Yes, we do have <link
> rel={dns-prefetch,prefetch,subresource,prerender}>, but in practice the
> current implementations of these hints often makes them less than useful -
> missing support, scheduling/prioritization gotchas, bad interop with
> preloaders, inconsistent implementation between different UAs, and so on.
> I think we should revisit what we've learned from our current hints and
> produce a spec around the three core primitives: preconnect, preload,
> prerender. To that end, drafted a quick doc describing the use cases and
> motivation for each one:
> https://docs.google.com/document/d/1HeTVglnZHD_mGSaID1gUZPqLAa1lXWObV-Zkx6q_HF4/edit
> Would love to hear any thoughts and feedback!
> P.S. Resource Hints spec as a 2014 goal? :)
Received on Thursday, 21 November 2013 01:02:11 UTC

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