From my experience, it's the "Access-Control-Allow-Origin: *" response header that causes the problem. So, it's in the way Chrome uses/enforces cross-origin HTTP request/response headers.
That's assuming the metrics they measure actually means anything. It's been proven many times that all the "science" behind these metrics and the resulting numbers are meaningless.
This is a long-standing issue and many solutions have been devised. Regardless of most solutions, it will probably always fail because people don't want to be bothered with remembering colors, images, configuring PGP, etc. Case in point, ask anyone how much they are annoyed by reCAPTCHA.
How is this any different from the what wait/serving staff experience. Most jobs are a flat wage (possibly minimum) and tips. It's always like that and still is. Maybe, the next time you leave a dollar tip for your server, you'll think again.
#omnibox-ui-hide-steady-state-url-scheme / #omnibox-ui-hide-steady-state-url-trivial-subdomains / #omnibox-ui-hide-steady-state-url-path-query-and-ref / #omnibox-ui-one-click-unelide