Nice, thanks for sharing this Jannik

You are very welcome oh and don't let the title of this thread mislead anyone. You can use Too Many Files and JCH Optimize at the same time, it is just that there are some overlapping features. So it is wise to test it independently first, and then you fine tune by adjusting which features you use from each.

do you have a link to this "Too Many Files" tool?

http://extensions.joomla.org/extensions/core-enhancements/performance/site-performance/26612 here you go.

Thanks for sharing Jannik

You are very welcome. Also let me point out that it also achieves the same thing a JQuery Easy, but instead of slowing down your site in the process, it speeds it up

Jannik Laursen wrote:
You are very welcome. Also let me point out that it also achieves the same thing a JQuery Easy, but instead of slowing down your site in the process, it speeds it up

what did you set in the config from this plugin, on my first tests i could not see any better results as JCH?

Well, I actually experienced instant results when I installed it. After adding CometChat I felt my site was too slow, so I added Too Many Files to ensure that I wasn't loading anything twice... and what do you know, the moment I installed it I dropped my sites size from 2.4mb to 1.1mb, so I was definitely loading some things multiple times. I also used it to remove MooTools.

But to answer your question, I actually use Too Many Files and JCH Optimize Pro at the same time. I just found that the merge JavaScript from Too Many Files is more flexible than that of JCH Optimize Pro (The one in JCH slowed down my site). Anyway, I have attached screenshots of my settings of both.

Sounds like a pretty decent solution

wow that speed my site up DRAMATICALLY! Thank you

You are very welcome Sam, I am glad it helped you. That was literally the experience I had. Additionally, let me point out, if you are using the Merge JavaScript from Too Many Files, there are several different options. I most recently changed my settings to the "Safe" one, as I was experiencing some inconsistencies with JavaScript on my site. So make sure to test the different versions to see what works best.

and Mark, it definitely is wonderful... and best of all it is free.

My point of view and approach of this is that we shouldn't just "patch" a leaking hole but fix the hole for good .
Keep it simple ! Keep it clean !

We get a bloated J! by installing all kinds of modules, bells and whistles , extensions that load their own stuff.
Then, because our sites becomes dinosaurs .. we load OTHER optimization extensions on top of it in our desperate need to make a "dinosaur" to not look like a dinosaur.

My approach is this

1. Analyze your site and figure out the "mission-critical" stuff !
2. Keep only the stuff you need.
3. Try to achieve as much as you can with as FEW extensions as you can.
4. Figure out what files are these FEW extensions load and need.
5. Try to merge the extensions dependencies in you template file that you already load.
For example, if one "mission critical" extension it's loading some css files, maybe it's a good idea to "merge" the extension css code into your template style.css file and figure out a way to disable/remove for good ... the loading of extension separate file.

Of course this may involve some kind of hacking at different levels. This may require that you keep a record of what "core" code you change from extensions, in order to re-apply it after extension upgrade. If you comment-out a line that loads unnecessary css files from extensions "core", make sure you keep a track of that change.

In my opinion this is the most "healthy" approach.

Let's bring "dinosaurs" sites down to "puppy" sites that works lightning fast. It requires pragmatism and focus.

Keep it simple !

Oh in an ideal world, I agree. However, in a world where your components, modules, templates and plugins are updated weekly for security, performance and feature set purposes... hacking makes the workflow very inefficient. This is a very efficient solution which has yielded noticeable improvements for a one time 2 min effort. This is a permanent solution. Your suggestion needs to be changed on a very regular basis.

I believe it all boils down to choices, aye? Being a non-techie, I'd prefer to keep it simple. Tech wiz such as Mark or Jannik would prefer to hack their way through the issue.

Looks interesting and notes it supports CDN. Based on your usage/testing/implementation, does this work alongside or in place of CDN for Joomla?

Hi Jannik,

I was going through your optimisation process, it definitely pointed me in the right direction.

Now i have JCC (Javascript+CSS Control) + Toomanyfiles, with both these i have optimum control over which scripts and css are loaded on which page and also move to bottom.

Now only one thing i need your expert guidance one, ES is loading three CSS files (base.min, style.min & more.min on each and every page wherever i have any module of ES enabled. These three css combined are about 718kb uncompressed, and moreover about 80-90% of this css are unused according to google audit.

Basically i plan to remove all three of these 3 css from all pages except the main ES pages with the help of JCC and then compiling only used css and including it in my template index.php.
These would have double benefits (3 http requests + reduced size) bith helping in reducing page load times. I'll only let these 3 styles load on the main ES pages.

Do you have any idea how i can remove these unused css, i tried dustmeselectors (Firefox extension) but for the above three files it says " files are too minified for operation"

Maybe Mark can advise on any headways he can give me on the above.

regards
Sunny

Hello Sunny,

I don't think you should remove them because they are the base of all the module styling (bootstrap is on it). Also, the reason that we split into 3 different files is simply because IE has a limitation on the total number of selectors that can be used in a single file

Hi Mark,

Thanks for your reply, I agree on a global basis.

But on specific optimisation needs, as the modules of ES are now more or less finalised, it does not make sense to load all unused selectors.

Right now i'm working on style.min.css, which was 310kb uncompressed, after removing unused selectors, i have currently managed to bring it down to approx 85kb uncompressed & unminified.

If i make any progress on base & more i'll update here.

Regarding bootstrap, fonts & icons, i would humbly like to submit that ES should have an option to exclude easy-social icons & bootstrap css & js, if the template is already loading bootstrap & fontawesome (Which nowadays most templates load by default). This would eliminate unnecessary duplications and make the component leaner.

regards

Sure, thanks for updating. There will be lots of css / js optimizations on EasySocial 2.0