2 people found this helpful
Unfortunately I fear, it is not TypeKit.
Since Muse 2015.2 Muse uses a better loading script – asynchronously loading –, which accelerates the loading times of your site.
Unfortunately there are some older widgets, which do not honour this modification.
Unfortunately, the custom widget that is being used in this web page is relying solely on $(window).load(...) to initialize the widget. Since the $(window).load(...) is now being fired before the rest of the libraries were loaded and initialized (including the library that relocates the HTML code for the widget from the infinity breakpoint to the current visible one), that init code ends up running on the infinity breakpoint. The problem "fixes" itself if a refresh is being triggered (by a page resize); in this case, the code that updates the appearance of the widget runs after the responsive library was loaded/executed, and correctly updates the HTML from the visible breakpoint."
You may try the following:
Delete your 3rd party widgets one by one and always upload your site to control page load. So, you may find the "bad behaving" widget and ask the vendor for an update.
By the way: I find your linked website very nice and clean! Congratulations!
Thank you for your detailed reply Günter. I think it was a third party widget that was causing the problem - I bought a different audio player widget and it seems to be working fine.
Thanks for your help!