Hello, Unfortunately this is Android's decision rather than Firefox's. When an Android app is in the background it's information will be stored in RAM. If you want to return to that app the information will be restored (almost instantly) from RAM. However the problem you describe arises when Android decides that it needs the RAM for something else (i.e. another app). When that happens the information about Firefox is dumped out of RAM and into cache on the phone's storage. This is a much slower type of storage and so the time taken to restore it when you return to Firefox is much longer. The only way of preventing this from happening would be to not use any demanding applications when Firefox is in the background. You can also investigate what is using up most of your phone's RAM. I found that the stock Touchwiz launcher on my Galaxy SIII was using loads of RAM. I replaced it with the Apex launcher which uses much less RAM. This leaves more space in RAM for my apps and so the apps in the background are less likely to get dumped into cache. It does still happen though. That is just how android works. See here for more info: http://android.stackexchange.com/questions/29466/how-to-force-browsers-not-to-reload-recently-seen-page-after-resume The other option (not cheap!) of course is to get a phone with more RAM. The top end android phones now tend to come with 2GB of RAM and I expect we will see 4GB in the near future. I hope that helps.