So I didn't see the "nglayout.initialpaint.delay" option in about:config. I figured I'd try making it anyway and giving it a low value.
No change.
I guess it's time to go back to v31 and hope that works out.
They mentioned some kind of new HTTP caching thing in v32. Maybe that's the source of my slowdowns - it'll wait until it finishes downloading the entire page,
then it will show content. Until then, the Firefox process sits at max CPU and is entirely unresponsive. Kind of makes it difficult to switch between tabs quickly and queue up slow-loading pages while doing other things.
Though allegedly...
"The new HTTP cache back end has many improvements like request prioritization optimized for first-paint time, ahead of read data preloading to speed up large content load...and zero main thread hangs or jank."
Edit: And I had no idea until now just how frequently I would right-click and press R to refresh a page. Can't do that anymore.
(One hand's on the mouse and one's on the keyboard, and my pinkie finger joints are wearing out from using Ctrl.
5.3% of all my workplace keystrokes of the last 6 months were Ctrl.)
I've got the Classic Theme Restorer addon, which does put the Back, Forward, and Reload text options back on the right-click menu, but it doesn't have the hotkey enabled, so R doesn't do anything.
I guess it makes sense. I've seen some regular users at a computer, and I think they could get along for quite awhile without a keyboard at all.
Meanwhile, I can navigate quite a bit without touching the
mouse at all. (Though the mouse does have 6 programmable buttons, all of which are regularly used.

)