Several months ago, we decided to move Meeting In The Media from WordPress to Squarespace - and we made the switch! Our new look and branding is just what we'd pictured, and this easy-to-use platform makes creating content fun again.
However, two weeks into the move, we noticed that our Firefox browser would freeze when trying to load the blog. We started to see a small pop-up window labeled 'Unresponsive Script Warning,' which noted some information about 'debugging' the problem, along with an option to 'continue.' We would click 'continue,' but this warning message would appear each time we returned to the blog page - this meant any time we were working on draft posts, editing posts, and visiting the live site.
We tried to solve the problem ourselves, first removing custom CSS, then removing custom Header and Footer code injection. We removed our Pinterest and Twitter sidebar apps, tested the site on a Mac and PC, across Firefox, Safari, Google Chrome and Opera - but, still, the problem persisted.
We wrote to Squarespace support staff and, with the in-depth information we provided in our initial message, our problem was immediately elevated to a supervisor. We were told that Squarespace has trouble loading too much information on one page, such as too many images or multiple blog posts. This means that Squarespace has a problem loading its own assets - image blocks and blog posts, summary blocks, and other assets created and hosted by Squarespace.com for its essential function as a website builder. Read more about Squarespace's problem loading its own assets, and how this could affect your website, internet browser - and possible workarounds while the problem remains at large.
We contacted Squarespace support once again, and were told that Squarespace has trouble loading its own assets, and therefore takes too long to load, freezing your browser. When an internet browser takes too long to load a webpage's content, the browser will pause and tell you that the scripts on the page are 'unresponsive'. The website will either cut-out altogether, such as with Google Chrome, or will give you the option to 'continue' to the page when it finally loads.
The Squarespace help supervisor wrote:
"I've been testing this and I can definitely replicate it periodically in Firefox. Normally this message [appears] when the script takes longer than expected to complete loading the content. Most browsers have a threshold for when to throw a warning message if a script takes a long time to complete, and it seems that the threshold for Firefox et al is right around the time it takes for this script to finish, which is why sometimes it finishes in time and sometimes it takes just a little too long, so the warning appears intermittently.
Typically, you can just click ‘Continue’ on the warning dialogue and the script will continue to load and you’ll be able to use the site normally. When I get this message while testing your site, clicking continue allows me to proceed and use the interface normally. However, you mentioned that after this message appears the site becomes unusable. Before troubleshooting further, I want to confirm that you have clicked continue and then the message either comes back, or the interface is unusable in some other way. And, if it is unusable can you describe the symptoms that occur so that we can look into this more.
If clicking continue does allow you to continue editing without trouble, then this is all that’s necessary. For more information about this warning message and how to increase the threshold slightly if you would like, see Mozilla's documentation here: https://support.mozilla.org/en-US/kb/warning-unresponsive-script..."
We were told that increasing the time limit threshold set for Firefox to load a page will help the website load without the 'Unresponsive Script' warning - but this only affects our individual browser, and not that of our users.
While you can change your Firefox browser settings so your personal browser doesn't see the 'Unresponsive Script Warning,' this problem lies with Squarespace. This Firefox fix can be a great workaround to the current, ongoing issue you are experiencing, and will help you push out your content without the 'Unresponsive Script' warning.
However, you should consider a few other workaround methods to prevent your viewers from seeing an Unresponsive Script warning, as well. One solution is to make a separate archive page - one that is not the landing page to your website, which could deter visitors. Another solution is to cut-down the number of blog posts that appear per page - we cut down from 10 to 3, and our blog post page no longer displayed this error message.