[wp-trac] [WordPress Trac] #57687: Add automated performance testing CI workflow MVP

WordPress Trac noreply at wordpress.org
Fri Feb 10 12:06:57 UTC 2023


#57687: Add automated performance testing CI workflow MVP
------------------------------+------------------------------
 Reporter:  adamsilverstein   |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Build/Test Tools  |     Version:  trunk
 Severity:  normal            |  Resolution:
 Keywords:  needs-patch       |     Focuses:  performance
------------------------------+------------------------------

Comment (by oandregal):

 It's great to see progress on this.

 For visibility and create as much alignment as possible: I'd like to share
 that Gutenberg (and codehealth) is now tracking both Time To First Byte
 and Largest Contentful Paint. I consider this the v1 for tracking front-
 end metrics.

 While tracking the time spent in the server is useful, it doesn’t directly
 correlate to user-perceived performance. We need to track client metrics
 as well. For example, WordPress processes the post to render, so it can
 identify the blocks in use. With that information, it enqueues only the
 CSS of those blocks instead of the CSS of the whole block library. This
 certainly takes more time in the server, though we expect it to improve
 the perceived performance by the user. If we only tracked server metrics,
 they’d report this behavior as a regression, and we’d lack tools to
 understand how it impacted the actual user-perceived performance.

 So, I wonder if you'd consider those two metrics part of the MVP for core
 as well?

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


More information about the wp-trac mailing list