Sorry if you bought it for 2GB of RAM thinking it was going to fix everything and make it a MacBook Pro. I've been a proponent of more RAM for the sake of a temporary fix and pushing the platform forward, but I didn't expect it to magically fix Safari which is quite buggy. My MacBook Pro with 16GB of RAM often has issues crashing in Chrome or Firefox when I get up past 80-90 tabs (I do web dev and design, so don't ask). However, I notice a huge difference between my iPhone 6 Plus and my iPad Air 2 when it comes to tabs, and even compared to my old Mini 2. I tested up to 16 websites (ones that I typically have open, pulled from my bookmarks and history) before it reset in the 17th at the 12th tab switch, and on my iPhone 6 Plus I usually cap out at 3 at most. But in typical use of 8-10 tabs during a browsing/research/whatever session, I don't have reloads. Now sometimes I'll have reloads if I switch thorough several tabs after I've resonded to an email, snapped a photo to send in a text, checked the weather and made a sketch in Adobe Draw and came back to Safari, but I don't mind that as much, and often the tab I was in doesn't refresh which is usually good enough, especially compared to the crap we had to deal with before. Depending on the game they can max out the RAM, but considering most games haven't been upgraded for new devices it shouldn't happen unless you're switching around a few times through higher end games. Lastly the caching seen on websites is often implemented by the site itself. They dynamically load content based on scroll position so that it lessens load in their server. Other pages that implement infinite scrolling (a terrible design pattern btw) do this by nature. So unless the website is insanely media heavy it's probably the way they designed it so unavoidable.