[wp-trac] [WordPress Trac] #34292: Support for DNS Prefetching & Prerender

[WordPress Trac]

#34292: Support for DNS Prefetching & Prerender
--------------------------------------+--------------------------
 Reporter:  bhubbard                  |       Owner:
     Type:  feature request           |      Status:  new
 Priority:  normal                    |   Milestone:  4.6
Component:  Script Loader             |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+--------------------------

Comment (by peterwilsoncc):

 Couple of thoughts around adding support for the pre* specs:

 * Pre-fetching or -rendering posts on the front-end increases the
 potential for a site to be brought down if it gets linked by a high-
 profile site or twitter user. If this path is followed, I’m slightly
 keener on prefetching than rendering but this is gut rather than science.

 * For resources enqueued prior to output, adding the pre* instructions as
 HTTP headers would start to get WordPress ready for HTTP/2 with server
 push. Actual push support can be a separate ticket.

 * It would be handy to include the preload spec, while the spec itself is
 in draft support is starting to appear in browser nightlies. Preload is a
 direction to the browser, prefetch is a suggestion.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/34292#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform