Is that your qualified opinion? Browsing on my old A1200 with 040/16MB fast (when the 040 card works, but that's a different story) on AGA is not a lot of fun, either. It starts off fine but sooner or later (depending on how many image intensive pages I've visited), I'm down to my last MB of memory and my 040 feels more like an 020 until I either flush the images or turn them off. That's with a minimal installation of OS3.5 and the usual 040 speedup patches installed (RemApollo, 040 ieee math libraries etc).
When? In the Win 3.1 days or today?
It's not just a case of misremembering either. This behaviour was observed recently, during the development of the old browser proxy for iBrowse/Aweb.
Aah so its today. You want to view the bloated mess thats the web today on a 40 mhz cpu with 32 Mb ram. Sheesh.
FYI I used the same spec A1200 in 64 colors dblscan(fblit and Ftext) till about 2002 with Aweb/Ibrowse. Sure over the years, it got slower as web pages became bloated with more and more useless banners and images. Being on dial up didn't help matters so i switched off images. I also ran netscape 4 communicator under shapeshifter with Mac SO 7.5.5 and the savage driver in 640x480 256 colors (the screen was in fast ram mapped with the MMU). The Aweb/Ibrowse set up was faster. The speed advantage of YAM over communicator was even more stark.
Eventually i went to the A4000/68060/CV64 running Ibrowse 2, on dial up till 2007 or so, and never experienced this BULLSHIT about worrying if the next web page would crash the system!
With some of posts some "Amigans" here make, you'd think their machines did nothing but crashed at the first single mouse pointer movement after booting. All the software on aminet must have been created with amiga's in an alternate reality, as according to Leander, the Amiga was one useless, perpetually crashing mess. For him NOTHING worked.