While domInteractive  is a much better metric, it also suffers from not being a good proxy for the user experience in some (fairly common) situations. The problem is, domInteractive  does not necessarily reflect when that happens. Stylesheets and custom fonts make domInteractive  measurements too small suggesting that content was interactive sooner than it really was. Scripts: Loading the domInteractive JS – too conservative test page, we see that the critical content is visible almost immediately. Fonts: The results for the domInteractive Font – too optimistic have a domInteractive time of about half a second in all browsers, but the time at which the critical content is visible varies.