It's not really the web developers who are the issue; they just implement what the people above them in the org chart wants. You could argue that the web developers should push back on it more than they do, but I don't buy that they're not knowledgeable enough to fix it.
That's not to say that there aren't actual technical issues; the recent trend of throwing front-end frameworks on content-heavy pages, making the users' low-powered phones parse and run hundreds of megabytes of JS before the page can be interacted with, is an example.
There are a multitude of issues that can be tweaked to speed things up more so than javascript elimination. You can switch to HTTP/2, implement server push, image compression, header compression, compressing HTML/CSS/Javascript downloads, preloading, above-the-fold downloads, and much more. A jQuery plugin user might not know half those things and I only mentioned maybe half the things one should know.
The average JS dev (like average anything dev) may not write performant code, but the functional parts of the website are not where the main problem lies.
The worst culprit is not knowing how to use photoshop to optimise images properly.
1 A lot of the front end production staff wont be comfortable using a cli - its designers that should be providing the images not developers.
2 Photoshop in some ways produces better results and is already part of the work flow.
As such, sure, it's useful to know the details, but it's usually far from necessary.
One example would be lazy-loading of images. I've worked at multiple agencies that definitely knew how to do this, but didn't, causing in the tens of megabytes of unnecessary data. Even just a small change to the templates + a jQuery plugin could have solved this one issue.
Of course, there are lots of reasons why a lot of this low-hanging fruit is left to rot, but they're not primarily to do with the developer's ability to understand all those details that you describe as necessary.