I'm seeing a lot of IO on ref hw inside
mozilla::AuthenticodeImpl::GetBinaryOrgName, called through
mozilla::UntrustedModulesProcessor::ProcessModuleLoadQueue. This usually runs after first paint but before we finish painting
about:home or whatever the first page to display is. On IO-bound systems we are still overloaded with IO at this point, so this is likely impacting the time until the first content is settled.
It seems like there's no reason we can't defer this a bit later? It already tries to defer itself until CPU idle, but that only gets you so far. Aaron, am I correct in thinking this?