The scripts are actually needed if the quick registrations are enabled. Do you have quick registrations enabled on the site?

No. Quick registrations are not used.

Thanks for the info Marc. We will look into this further.

Hello Marc,

I have investigated further and the scripts are still necessary because:

1. The textbox that has the field are rendered using js and it uses js events to make the label appear within the input, https://take.ms/SlGxt

2. For sites that uses the single sign on (fb, apple, twitter or linkedin), it requires js too.

Thanks for the update.
is there any way we can defer the loading of the js script?

Hey Marc,

Unfortunately there is no way to defer EasySocial scripts because inline scripts will hit errors and cause the page to break.

the ES site-3.2.21.min.js script automatically included. This file is 1.1Mb in size and is a blocking script, being neither deferred or loaded async.

Really agree. Can this be developed differently or removed or..? this is a performance killer..not working with defer & async too

Hi ssnobben,

This has been investigated before and unfortunately, currently nothing can be done from our side.

Hi ssnobben,

This has been investigated before and unfortunately, currently nothing can be done from our side.

Ok thats a pity.

You can imagine you have a huge "untouchable" file of 1.1Mb in size ( no sync/defer working) and that effect your loading time massively! And the negative loading effect of your ES/Joomla site is huge with Google SERP penalties There is no other js file effect that come into comparision of this monster..

And thats why I also have to have no ES login box module on my front page.

Thanks for your input on this snobben. We have tried to use deferred more than a dozen times and it just wouldn't work in a large ecosystem like Joomla. We have absolutely no idea what other extensions or templates are doing and there is no way for us to bulldoze our way because somehow or rather, you either break something or break your own extension.

Unfortunately if our answer to our customer is to "check with your template / extension provider because their JS is breaking EasySocial", majority of the customer is going to back with us "But this problem only happens when EasySocial is installed" and believe it or not, 90% of the time, the template or extension developer will never even respond or do anything about it.

We end up going through this viscous cycle that does not benefit anyone.

I hope you understand where we are coming from and as much as we want to keep this file as small as possible, we are talking about a full suite of social network that has tons of functionality.