The debate on which is the best browser in the world is unlikely to conclude anytime sooner. While Google Chrome is arguably the most popular browser, it does get fair amount of criticism for being slow and hogging performance. Mozilla s Firefox is no stranger to similar criticism. However, the next version of Firefox could be major improvement in terms of overall performance. The new versions 55 and 56 of Firefox which are under development stage are claimed to support an insane number of tabs and still function. In one such example cited by a Firefox developer, there were a total of 1,691 tabs open on his browser which still functioned without any problems. Also Read - Chrome Beta 89 released: Revamped Discover feed, web sharing on the desktop, and moreAlso Read - Google confirms a fix for Chrome crashing issue on Apple Macs with M1 chip
Dietrich Ayala, a Mozilla Firefox developer, recently shared how he had a Firefox browser with multiple tabs open. He took up the task to see how fast and how smooth the experience was. His report mentions how initially, the same profile would take minutes to start up and also there were be long time wait to open up external tabs. However, the new version of Firefox eliminated all that. He compared the older Firefox version 51 to the more advanced Firefox version 55 and the results were very different. ALSO READ: Mozilla Firefox Focus private web browser finally comes to Android Also Read - Microsoft Edge and Internet Explorer will not support Flash by end of this year
The older Firefox 51 took as much as 8 minutes to complete the tasks and fire up whereas the newer version did it in under a minute – 15 seconds to be precise. The project called Quantum Flow is working on improving on making Mozilla more responsive and quicker. In order to be sure of his tests, he shut all other applications on his MacBook and carried out the test only on Mozilla. Wi-Fi was also turned off. Firefox has also restricted memory usage, freeing up more memory to open additional tabs while browsing. ALSO READ: How to disable pesky Google Chrome notifications on your desktop
Ayala does mention that he measured approximately, not setting any timer but simply checking and confirming once the page loaded to see how long it took. Since his Wi-Fi was turned off, the way he tracked time was how long it took for the “Server Not Available” page to fully load into the system.
With regards to how he measured memory, he says, “For memory, I waited for one minute after the startup measurement point and then grabbed the total value from the bottom of about:memory. I waited one minute, because I observed a consistent spike in memory after startup which went away within the first minute and then stabilized for a long period after. It’s all kinds of initialization that doesn’t need to block the app from starting, but needs to happen once you get to browsing.”
He tested multiple Firefox versions starting 20, 30, 40, and 50 through 56 and interestingly discovered that till version 51, the speed and the response kept dipping consistently. Once rolled out, the new feature will try to attract tab hoarders and try and get closer to Google Chrome in the browser race.