I wonder whether this could have anything to do with DNS lookups working different in Chrome. Assuming Chrome on mobile directly goes to google DNS too.
Or maybe FF also getting IPv6 records for your affected targets and there being some slow or bad connection there.
But personally I don't have much experience debugging such things on Android.
I wonder whether this could have anything to do with DNS lookups working different in Chrome. Assuming Chrome on mobile directly goes to google DNS too.
Or maybe FF also getting IPv6 records for your affected targets and there being some slow or bad connection there.
But personally I don't have much experience debugging such things on Android.