Combined CSS nightmare
Sep 3, 2019 9:59 AM
It's kind of nuts that this is still a problem. Our dev team took great efforts to split out the CSS that is common to all pages on our site into a common.css and then generated page-specific CSS files for those pages with a fair amount of custom CSS in order to not have one gigantic bloated common.css
And in comes HubSpot trying to do its magic with combining CSS. The result is that now NONE of our CSS is cached in the browser because every single visit to a page on our site now requires downloading a new unique gigantic combined CSS file generated by HubSpot's wizards who are implementing practices that made sense in 2008 before the advent of HTTP 2 which allows simultaneous multiple downloads.
Combining CSS no longer improves load times for modern browsers and in our case, it actually makes our site far slower because nothing is ever cached in the browser (unless a visitor managed to visit all 30 pages on our site and cache each one's unique combined CSS file).
We have submitted this to support and supposedly the "engineers can't see the combined CSS". ¯\_(ツ)_/¯
Here are screenshots of what the HTML SHOULD look like and what HubSpot is butchering it to actually be. I don't know why the devs can't see it but this will seriously be the thing that causes me to just leave HubSpot entirely, I don't need or want you to "fix" my optimized web site.
What do we have to do to fix this? It's just so unbelievable.