One Page, Three Browsers, One Phone

Same phone, same Wi-Fi, same page, three browsers. I had been blaming games for stutter that only ever appeared in one of them.

Chrome is my baseline, since it is what most people will open a link in. Firefox on the same mid-range Android renders the identical lobby about a second slower but keeps its audio context alive across tab switches, which Chrome on this device does not. The third is the WebView inside a chat app, the path a lot of people actually take, and it is the one that surprised me: no address bar, no shared cache, and a hard cap on how much memory the page is allowed to touch.

I run three saved entries through all of them. h5.big11 is the lightest and behaves identically everywhere, which makes it a fair control. juara666 draws its menu differently in the WebView, same layout but one row taller, and that single row is a fix I would never have found in Chrome. gf777 is the only one that asked for fullscreen properly in all three; the other two needed a second tap after the screen rotated.

Two more sit in the same folder for the same reason. an777 slot reloads once on rotation inside the WebView but not in Chrome, and the build I installed as svip9 apk ships its own browser shell, which turns a three-column test into a fourth I did not plan for.

Three browsers, one afternoon, no profiler. A page that works everywhere is rarer than it should be, and the differences tell you who tested on a real phone and who did not.