Live Chat App slows page down

[merlinvicki]

Hi,

I have the Hubspot Chat installed here:

https://www.3mediaweb.com/great-b2b-software-company-websites/

There is a file:

https://static.hsappstatic.net/conversations-visitor-ui/static-1.383/bundles/visitor.js

which is almost a 1.39 mb file. Is there no way to compress the scripts so it loads faster?

[BB-King]

The fact that you had to write all this custom script for a Hubspot chat feature is completely ridiculous and should not be necessary.

How can a thread that has this many comments from unhappy users get away with having "it's probably some other problem with your website, bro" as the only response from a Hubspot rep? This is insane.

Hubspot - fix your chat scripts!

[Joy-EWM · Accepted solution]

Thanks for the codes, it saves my day.

Btw for those who confuse how to create the button, i found another workaround by adding delay. So it will load the chat widget after "X" milliseconds.

Here's the sample code with 15 seconds delay:

<script>
  window.hsConversationsSettings = { loadImmediately: false };
  setTimeout(function() {
    window.HubSpotConversations.widget.load();
  }, 15000);
</script>

[PamCotton]

Hi @Joy-EWM, thank you for posting another workaround!

Kindly,

Pam

[TBL]

Solution works, I mean delays loading for the widget.

But when checking with gtmetrix tool, I still see that HS files created problems.

Maybe someone can help to prevent delay these files too:

• https://js.hs-scripts.com/6974069.js 
• https://js.hs-analytics.net/analytics/1598021700000/6974069.js 
• https://js.hs-banner.com/6974069.js
• https://js.usemessages.com/conversations-embed.js

[berylindia]

Where to use these codes in WordPress website? I am not a technical person. 

[bsplosion]

@berylindia you've hit on why all of the proposed "workarounds" really indicate that HubSpot needs to fix their bundle.  Each workaround is both technical (requiring at least some modicum of Javascript familiarity) and intentionally breaks pieces of existing HubSpot chat functionality in order to "fix" the issue (which is not fixed, just delayed).

@PamCotton is there any ETA on this being fixed?  We're likely not going to use HubSpot for an upcoming platform if there isn't any commitment to bundle size changes.

[rawphael]

Same here, we won't roll out any new HubSpot projects for our clients nor will we consult them to use it in the future.

Speed is essential these days and the HubSpot Product Team is either not aware of this issue or they don't think it is a problem. Whatever - it is simply not acceptable for a tool in this price range to ignore something like this. 

[edsvcs]

We feel the same way. When you pay a premium price you expect at least a mediocre product. This is unacceptable and is the primary reason why we already migrated from HubSpot to a more fully integrated CRM.

[Joy-EWM]

@berylindia try to put it before closing of body tag

[aupperk24]

Still no resolution?

[PamCotton]

Hello @aupperk24 @edsvcs, @rawphael, 

I talked to our team and they are aware of how this and working on actions that improve this metric.

It is important to remember that performance recommendations surfaced in external tools are typically formulated by bots and automated measures to evaluate a site and assign a score or grade. With that in mind, these scores don’t always replicate the actual visitor’s experience of the page load. In the case of chat, the widget is designed to not load until the site is fully loaded.

That means it won’t impact the speed of the site loading, only the overall time of page load. From the visitor’s perspective, the website is loaded and interactable before the widget loads since these are asynchronous actions. Tests like Google PSI measure based on total time to load, instead, so they are tracking something different than what the visitor really experiences on the page.

All that said, we absolutely understand users tracking that number and hoping to see improvement. On our end, we need to balance whether we are solving for the page visitor or solving for the test since the two are not always aligned. We are always investigating ways to improve these numbers and it is on our radar to do further investigation here.

Thank you,

Pam

[tilly · Accepted solution]

Hi all! We recently updated the "Time on page in seconds" trigger. Delaying the chat widget load by at least 5 seconds should optimize for a faster initial page load.

[bsplosion]

Hi @tilly ,

Thanks for the update!  Oddly enough, there was an even bigger change on your end which no one has bothered to mention:  the visitor.js bundle has been greatly reduced in size as everyone has been requesting, all the way from ~1.39MB to 246kB!  This is the degree of minification which we'd been saying should've been possible since 2 1/2 years ago, so thank you to whichever unsung hero within HubSpot finally got this knocked out.

FYI @jennysowyrda , it turns out this was possible despite the stonewalling, as HubSpot finally took care of it (your comment didn't age well)...

The "Time on page in seconds" trigger actually wouldn't have resolved this issue, as visitor.js still gets loaded immediately and would've still had a pretty massive impact on both initial page loads and script compile times.  There doesn't appear to be any load deferred until after the time on page elapses, so our primary complaint wouldn't have been addressed without the optimization of the visitor.js dependency.

[tilly]

Hi there @bsplosion and thank you for the tag!

You are absolutely correct, there have been some much larger and more significant changes, happy to hear you've noticed the improvement!

More details on your recent changes below:

• The payload size of the widget has been reduced. In the past, this project simply has not been possible given the size of the undertaking. It took significant resources and time to see this through, I'm very glad you have seen the change.
• We also changed how the "Time on page seconds" trigger loads the widget. You are correct that in the past this would not have had an impact; however, with recent updates we now delay parts of the widget load and startup until after the time delay has completed.

Please let me know if you have any additional feedback or questions!