[wp-trac] [WordPress Trac] #62687: Performance improvement proposal (core and support level changes)

[WordPress Trac]

#62687: Performance improvement proposal (core and support level changes)
-----------------------------+--------------------------
 Reporter:  tunyk            |       Owner:  (none)
     Type:  feature request  |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  General          |     Version:
 Severity:  normal           |  Resolution:  duplicate
 Keywords:                   |     Focuses:  performance
-----------------------------+--------------------------
Changes (by swissspidy):

 * status:  new => closed
 * focuses:  accessibility, css, administration, performance => performance
 * resolution:   => duplicate
 * milestone:  Awaiting Review =>


Comment:

 Hi there,

 You might be interested in learning about the
 [https://make.wordpress.org/performance/ WordPress core performance team],
 which is dedicated to monitoring, enhancing, and promoting performance in
 WordPress core and its surrounding ecosystem. That includes working with
 some of the technologies you are listing here.

 Typically we create separate tickets either here on Trac or on
 https://github.com/WordPress/performance for each individual feature the
 team is working on, rather than having one catch-all ticket.

 > Intersection Observer API
 > Mutation Observer API

 Here, you are just listing some technologies that by itself don't do much.
 They're just a means to an end. So this is not really actionable.

 > Speculative Loading (integrate the functionality of this plugin into the
 basic system – https://wordpress.org/plugins/speculation-rules/)

 Integrating the functionality of that plugin into core is actually the
 whole point of its existence. It's a so-called feature plugin that allows
 us to test and refine features before merging into WordPress itself.

 Speculative loading integration is already being worked on in #62503,
 targeting 6.8.


 > PWA – (integrate the functionality of this plugin into the basic system
 – https://wordpress.org/plugins/pwa/)

 Same for this plugin :-) While it works great on its own, it was also
 originally built to be integrated into core itself. It's even in the
 readme.

 > Use CSS content-visibility in standard WordPress themes
 https://web.dev/blog/css-content-visibility-baseline


 Again, a means to an end. It's not something you just add everywhere to
 make performance better.

 content-visibility is being looked at in
 https://github.com/WordPress/performance/issues/1308.

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