Today when I looked in the logs I could see that it's not only the usual Safari events that gets discarded because it's out of order T197954, it seems there are some that happens for Chrome too.
Dec 19 11:54:35 webperf1003 navtiming[546953]: 2022-12-19 11:54:35,350 [INFO] (is_compliant:561) Discarding event because requestStart is out of order [('Chrome', '108')]
Dec 19 11:54:57 webperf1003 navtiming[546953]: 2022-12-19 11:54:57,393 [INFO] (is_compliant:561) Discarding event because requestStart is out of order [('Chrome', '104')]Lets look into this and check if there's something we should report to Chrome.