However, the two second rule seems to kick in here when WPT measures the Fully Loaded time. Unless we specifically wait a little over 2 seconds (2200 ms seems to do the trick), any way we load assets seems to count towards the initial page load time, since it’s detected as network activity. Even via script tag marked as
My question: Under our scenario, is there any way we can structure our code to avoid this page load time inflation in the WPT figure?
I can see how WPT can’t really tell that what is being loaded has no dependencies to the initial interactions of the game (page), so it has to do what it can to assume this counts towards the initial page load metric.
Delaying further asset loading for over 2 seconds is mostly fine, if we do this for content used by the later game levels. We would get some extra flexibility in how we structure things though if we could avoid that extra delay.