The boot splash animation can artificially slow down the time from boot to sign-in screen visible if the sign-in screen is ready before the boot splash animation has complete because frecon does not send the dbus signal to Chrome to take over gfx until the animation has completed.

We should have a way to track the time delta between when the sign-in screen is able to be displayed, and when Chrome gets the dbus signal to take over gfx.

Currently there does not seem to be any headroom but there was in the past, and it's likely there will be in the future for some devices. If headroom becomes significant, we can consider shortening the boot sequence in some way.

See crbug/508600 for further background.