Jo, I understand your point, and do wonder if optimizing in this way is worthwhile, it is an idea, but I have noticed that small things make a real difference in speed.
Our single page has several parts including, availcalendar tab, a contactform (php) / recaptcha tab. The website when completed had 5 CSS + 7 JS files, which result in a slower load time.
CSS BEFORE
cdnjs ... bootstrap.min.css 142kb
cdnjs ...bootstrap.theme.min.css 23kb (we don't use it)
cdnjs...lightbox
plus a number of other files that availcalendar, contactform (php) and recaptcha require
styles.min.css 5kb
CSS NOW
cdnjs ... bootstrap.min.css 142kb
styles.min+.css 8kb (also contains lightbox, availcalendar, contactforms and bootstrap.validator)
JS BEFORE
cdnjs...bootstrap.min.js 37kb
script.min.js 3kb
lightbox
plus total of about 5 more js scripts for availcalendar, contactforms.
JS NOW
cdnjs ... bootstrap.min.js 37kb
script+.min.js 119kb (also contains lighbox, availcalendar, contactforms and bootstrap.validator etc)
recaptcha and availcalendar still download several files separately because I don't have access to do that.
Perhaps you are right that messing with Bootstrap files might be too much work and I've completed the optimization that is reasonably possible. I guess if I could successfully delay the photos that are not used in the first render, that might help more with page speed, but the javascript I've tried does not work well.
Now I am realizing that a website utilizing multiple or separate pages inherently reduces page load time because the first page is the first page (and contains nothing else behind it - as opposed to the the TAB structure). So this is a good reason to change the format to separate pages. The other advantage of separate pages is that bots will pick up each separate page and catalog it for some real SEO advantages.
Utilizing separate pages, would also reduce the number of CSS and JS files that have to be downloaded because they would only be what is needed for the first page, not all the TABS.