Looking at the graphs for WebPageTest emulated mobile we can see that we have an increase for that metric:
If I just look at one URL I can see that it correlates to when Chrome 100 was released:
Peter | |
Mar 31 2022, 7:45 AM |
F35043325: Screenshot 2022-04-08 at 08.42.42.png | |
Apr 8 2022, 6:47 AM |
F35043318: Screenshot 2022-04-07 at 16.23.11.png | |
Apr 8 2022, 6:47 AM |
F35043330: Screenshot 2022-04-08 at 08.44.58.png | |
Apr 8 2022, 6:47 AM |
F35042536: Screenshot 2022-04-07 at 16.19.57.png | |
Apr 7 2022, 2:20 PM |
F35031483: Screenshot 2022-03-31 at 09.36.43.png | |
Mar 31 2022, 7:45 AM |
F35031487: chrome99vs100.jpg | |
Mar 31 2022, 7:45 AM |
Looking at the graphs for WebPageTest emulated mobile we can see that we have an increase for that metric:
If I just look at one URL I can see that it correlates to when Chrome 100 was released:
Looking into the WebPageReplay tests and the other test we run directly against Wikipedia and there there's no visible change. Let me look into if I get something useful out of WebPageTest.
As reported in T305572 I could see that Chrome makes multiple requests to optimizationguide-pa,googleapis.com. In Browsertime/sitespeed.io those requests are blocked but since we haven't done any update to WebPageTest in a year or more, WebPageTest missed the Chrome flag to turn it off. I can also see that people reported that the requests happen even with the flag enabled so I just added that domain to blocking.
That fixed the late request in T305572 and more interesting it also fixes the response end:
It isn't super easy to see (since we had WPT go down for some time but also LCP is affected for Sweden and Facebook (hard to say about Obama):
Its interesting that this only happens on emulated mobile, so in best case this is not something that would affect real users. I'm gonna create a Chrome task and ask.
There's an upstream bug (that I do not have access to) https://bugs.chromium.org/p/chromium/issues/detail?id=1293151 and then there's some info in this thread: https://twitter.com/_tbansal/status/1493335460331933696
If I understand correctly there was bug that was introduced (that hidden for us) and then they are working on trying to distribute the calls to the optimisation guide better.