In the case of Chrome and Firefox, they're competitive enough that you really need to say both what you're measuring and how you measured it. People tend to say one is faster than the other when they most commonly mean “the set of extensions I installed in A slowed it down more than B”.
In Chrome when you load a JS-intensive website (ex. Facebook) you can switch to a different tab while the website finishes doing that JS-intensive task (ex. loading), but in Firefox the opposite happens, the entire browser freezes so you are forced to wait until the browser becomes responsive again.
We are talking in the order of magnitude of milliseconds, but unfortunately it is enough to be perceptible (and annoying).
Fortunately for FF, e10s[1] is almost baked, it still doesn't feel as responsive as Chrome BUT it feels significantly better so you can easily neglect the difference until it matures or something better (Servo[2]) gets baked.
My point was simply that without providing more detail, those comments are so vague to be useless.
Other times, FF is lightning quick - near instantaneous loads - only other thing I can think of is that I'm running FF on Fedora?
I had higher hopes for FF android, as it allows plugins (adblock), but the browser is so horrible on the platform, I wound up switching back... I also tried dolphin for a while. Neither was satisfactory.
I just like chrome better...
Unfortunately outside America the mobile web is a malvertising minefield, and the malvertisers target the carriers directly, so there is no way to expect ad networks (ex. AdSense) to proactively hunt for them.
A browser with integrated AdBlock is the most sensible option you can have in a non-rooted device, and the easiest one you can recommend to friends and colleagues.
I know that is a separate issue... would really like my password manager & adblock & the app window/tabs where each "tab" is a separate window instead of integrated tab-bar, which isn't very nice at all on a phone.