Make WordPress Core

Changes between Version 2 and Version 3 of Ticket #57687, comment 4


Ignore:
Timestamp:
02/21/2023 06:32:42 PM (16 months ago)
Author:
oandregal
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #57687, comment 4

    v2 v3  
    11Another thought about meaningful things to track. In addition to: "server time" (TTFB) and "user time" (LCP), **there is value for us to understand the time it takes the client to render the data it receives**.
    22
    3 In https://github.com/WordPress/gutenberg/pull/48288 I'm proposing to add a new metric to Gutenberg's front-end performance suite: LCP-TTFB. I'm unaware of any industry metric that tracks the same thing, I'll be happy to adapt if there's any. The rationale is that TTFB takes so much of the LCP (50% for classic themes and 80% for block themes) that it may hide any meaningful difference in the client-side rendering. For example, changes that add blocking scripts/styles that impact LCP negatively may be hidden if we improve TTFB in big ways when comparing WordPress releases.
     3In https://github.com/WordPress/gutenberg/pull/48288 I'm proposing to add a new metric to Gutenberg's front-end performance suite: LCP-TTFB. I'm unaware of any industry metric that tracks the same thing, I'll be happy to adapt if there's any. The rationale is that TTFB takes so much of the LCP that it may hide any meaningful difference in the client-side rendering. For example, changes that add blocking scripts/styles that impact LCP negatively may be hidden if we improve TTFB in big ways when comparing WordPress releases.
    44
    55As a matter of fact, take a look at the [https://docs.google.com/spreadsheets/d/1LroIJoYz-O9CpfJzaiKYYMWJ7GbE5RZoW1rf1R4FqyA/edit#gid=996638482 latest numbers by Felix] that include LCP: