[wp-trac] [WordPress Trac] #40426: Remove dns-prefetch of s.w.org domain

WordPress Trac noreply at wordpress.org
Sat Aug 6 21:41:35 UTC 2022


#40426: Remove dns-prefetch of s.w.org domain
---------------------------------------------+----------------------
 Reporter:  joelhardi                        |       Owner:  (none)
     Type:  defect (bug)                     |      Status:  new
 Priority:  normal                           |   Milestone:  6.1
Component:  Emoji                            |     Version:  4.8
 Severity:  minor                            |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:  privacy
---------------------------------------------+----------------------
Changes (by SergeyBiryukov):

 * keywords:  has-patch has-unit-tests => has-patch has-unit-tests commit


Comment:

 Some history here:
 * [37920] / #34292 added a `preconnect` hint for `s.w.org` to improve
 emoji render time, see #33210 for context.
 * [38122] / #37387 changed `preconnect` to `dns-prefetch`, see
 comment:9:ticket:37387 for context.

 Looks like concerns were raised on both tickets about whether it's
 appropriate to include this for every WordPress site.

 @johnbillion in comment:53:ticket:34292:
 > Including a default `preconnect` entry for `s.w.org` seems unjustified.
 This means every single visitor (with a supporting browser) to every
 single WordPress site in the world will be performing a preconnect to
 `s.w.org`, purely to save a few ms in case an emoji is used that's not
 supported by the browser.
 > Does this really justify a preconnect to `s.w.org` on every site?

 @dd32 in comment:3:ticket:37387:
 > I'm not sure myself if it should be in the list at all, a fallback emoji
 loading a few ms later isn't going to be the end of the world, and
 browsers are getting better at supporting everything already.
 > I'd say the vast majority of WordPress sites don't actually have any
 Emoji's on them, so a few ms in those cases would be fine.

 I tend to agree with these sentiments. Since there is also a privacy
 concern as outlined in this ticket, it seems better to not include `dns-
 prefetch` for `s.w.org` by default. A plugin could use the
 `wp_resource_hints` filter for that.

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


More information about the wp-trac mailing list