Speed and performance should be a top priority, it is one factor that Google takes into consideration to make your website score higher in the search results. It is great that Plone offers so many tools out of the box to improve speed, bundle resources, defer javascripts, caching system etc. It is very impressive.
Currently I'm working on bringing a default Plone installation to score 100/100 in all Google metrics. I intent to write and share a small article with instructions that everybody can use to get there.
Problem:
While using Google's tools, PageSpeed and web.dev, to improve speed I've come across a problem with the jQuery version being used in the latest Plone 5.2 with Python 3.
Unfortunately I cannot help you with your question, but I am interessted in that topic. We have also worked on finding ways to improve the score of a default installation.
Perhaps we could get in contact and exchange information about the current status.
I have upgraded Patternslib for Quaive to jQuery 3.latest, so it can be done. The jQuery changes are the easy part. The hard part is the whole packaging mess. Also, Patternslib has pretty good test coverage so I was able to rely heavily on that. I'm not sure what the state of JS tests is in Plone.
For upgrading plone.staticresources see the README.rst in that package:
If there is anything unclear ask me. Would be good to have some feedback regarding this docs anyways. @fredvd do you remember our discussion @ alpine city sprint 20 about the state of docs of the Plone's JS workflow? Do you have some notes of that?