All Files on HTTPS, ASYNC, and Other Page Speed Optimization
In order to have a fully secure (https) site, all files must be encrypted both internally and externally. If a file is served to the user un-encrypted, then it breaks the rule and the site technically is not a fully secure site resulting in a grey padlock on the address bar by Google.
For example, the file http://filamentapp.s3.amazonaws.com/094b3993950d765e6cad8b99840c627d.js is not secure. If I change this address, it does appear to be available as a secure file, https://filamentapp.s3.amazonaws.com/094b3993950d765e6cad8b99840c627d.js
Thus, the coding needs to be uniform in serving all files as secure (https).
Additionally, add async to all files being served from external locations.
Running Google's https://developers.google.com/speed/pagespeed/insights on any site that has Flare will show files need the following in order to pass:
JS Expiration Not Specified