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

WordPress Trac noreply at wordpress.org
Fri Jul 15 13:08:24 UTC 2016

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

Comment (by superpoincare):

 Replying to [comment:52 swissspidy]:

 That code gives a 500 error.

 I also have to add that preconnect is also costly to the server. How much
 is Wordpress' share? 25%? If all preconnect to s.w.org, it is costly to
 the servers.

 Ilya Grigorik says https://www.igvita.com/2015/08/17/eliminating-

 ''Preconnect is an important tool in your optimization toolbox. As above
 examples illustrate, it can eliminate many costly roundtrips from your
 request path — in some cases reducing the request latency by hundreds and
 even thousands of milliseconds. That said, use it wisely: each open socket
 incurs costs both on the client and server, and you want to avoid opening
 sockets that might go unused.''

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

More information about the wp-trac mailing list