Google PageSpeed score is being negatively affected by HubSpot network requests
Mar 4, 2019 3:47 PM
Our Google PageSpeed score is being negatively affected by hubspot network requests.
Though these scripts are being loaded defered and async, they still are calculated into the overall page load times for Google's metric.
1.) Can anything be done to lighten these, or at least follow the guidelines Google is asking for for a better user experience?
2.) Can you put a cache policy onto the below static assets? Google suggests "Cache-Control: max-age=31536000". If you need to update these resources, why not use a url revision query?
3.) If your chatbot needs to download 6 fonts, at least use the font-display css value of "swap" so that it can use a system font until the fonts are fully loaded.
5.) Can you remove the default styling in the forms embed that is injected into the head of the document? If I am selecting "Unstyled Form", that's what I should actually get so I can style the forms in my own stylesheet. This small change would allow me not to have to go to the troulble of rebuilding all my forms using the Forms API.
6.) Because of the chatbot specifically, our site's Mobile pagespeed score is "Slow". There isn't a way to disable it for mobile, only a hack of using css to hide it which doesn't solve anything - still requests all the above offending resources.
Making these changes or suggesting solutions that work would be a step to helping out those of us concerned with site optimization as it pertains to SEO and overall performance for our users/customers.
Supporting backward compatibility for old browsers and/or hubspot users' legacy code is understandable but those of us utilizing current web standards shouldn't have to suffer. HubSpot is an expensive product to not be at the top of it's game when it comes to these concerns.