I want to attempt to replicate a situation of what an "average" user would be willing to do in order to use their system.
Even for the average user, there is a difference between wanting to "use" their system, and get the most out of their system. And the difference between the two realistically takes very little effort, all in a span of less than five additional minutes total. If they are not willing to get the most out of their old system and just use it how Apple would have wanted you, then Web-wise, it's frankly a waste of time and they will almost always be disappointed.
Often, the user only needs to simply be aware of a certain Firefox patch and be supportive of the idea of making browsing faster, and they will have no trouble spending an additional five minutes to achieve faster Web speeds, because said patch strives to make the entire installation experience as absolutely user friendly as possible. Simple as that.
My guess is it's down to the javascript that OSX Tiger/Leopard gets bogged down with rather than GPU assisted acceleration, hence my observation about older user agents speeding things up by presumably not loading new script driven features.
Even for very basic sites on my G5 (in TFF), I've seen evidence that the GPU is always inactive, regardless of what the user has done. For instance, scrolling isn't as smooth as it could be. CPU activity briefly shoots up every time you make an action. On heavy sites, the CPU fans are prone to spinning up because the load-bearer is the CPU, NOT the graphics processing unit.
Contrastingly, I have not been able to replicate these results on a Linux distro using something like Arctic Fox. Maybe that doesn't go for every platform due to GPU support, but that's the case I've consistently seen.
So yes, the Web's addiction to JavaScript makes a bad situation much worse, but it's quite evident that it's not the sole root of all said browsing problems.
And when I've done benchmarks to establish any merit to config file acceleration tweaks I found none.
I just tried running the linked benchmark on stock TFF vs on foxPEP 1.8.1. Keep in mind TFF can only get a portion of foxPEP's effect as so many integral technologies to help alleviate Web 3.0 are disabled or outright missing, severely hampering the Web experience right out the gate. So, it's likely the results below are not in fact the full picture, especially as I have not run this tool on any other OS or browser.
Stock:
foxPEP 1.8.1:
Strangely, the demos for foxPEP 1.8.1 ran slightly smoother than on stock, and yet it still got a lower score.
This will be (attempted to be) remedied once and for all for version 1.8.2. But whether another noticeable browsing difference springs from that remains to be seen, as it's entirely possible that could simply amount to higher numbers, but lower real performance.