Question Complaints about Mootools

Hi Karmany, I'm trying hard to speed up my site, I was curious what was your fix was this? What version of Joomla and Kunena setup do you recommend for speed and lower server resources?

Sunny33days,

If you read the post above you will see it is 6 months old. You will also notice, if you read, that Mootools is part of Joomla, not part of Kunena, so direct your Mootools questions to forum.joomla.org/

Thanks.

Jiminimonka wrote: Sunny33days,

You will also notice, if you read, that Mootools is part of Joomla, not part of Kunena, so direct your Mootools questions to forum.joomla.org/

Thanks.

that's is quite right...

if i disable mootools-more and mootools-core (i found a plugin for this that works very well) everything in joomla works fine except of kunena (boardcode crashes)

so, this is a problem related to kunena

and this is a BIG problem, cause that damned mootools in j2.5 takes 50% of my pages weight

Since Mootools is part of Joomla now, the correct way for extensions to work is to use Mootools, to stop conflicts later down the line.

If Mootools is using up too many resources on your server and that is an issue, you need to upgrade, seriously, as your server must be from the 1980s.

rexet wrote: so, this is a problem related to kunena

and this is a BIG problem, cause that damned mootools in j2.5 takes 50% of my pages weight

As I've stated before, many other extensions use the Mootools library, it's not just Kunena. This is a library that's provided by Joomla and is available to use by any extension. The Kunena installation package doesn't actually contain the Mootools library, it's already part of your Joomla installation.

Also as I mentioned before, the library is downloaded once by the browser and then cached locally. Subsequent requests for the library result in nothing being downloaded. So that initial burden only happens once. Once the library has been cached locally, ALL extensions that make use of it on your site no longer need to download it. Utilities like PageSpeed and YSlow do not take this into account when they evaluate a page, they only assume initial page load.

Furthermore, the library is usually compressed by the server before being sent to a user's browser, so its actual size and download burden is even smaller than reported. Using a CSS/JS gzipper is typically a bad idea, since it just ends up breaking the gzipped CSS/JS files. However the built-in Joomla gzip compression functionality (enabled in the Joomla Control Panel) works very well and doesn't break anything.

Finally, the Mootools javascript library is a defacto standard all over the web, used in many large and popular web sites that you probably visit daily. It allows web developers to include advanced, cross-browser compatible features using minimal coding. So in the end, using Mootools can actually LIGHTEN the overall burden of a site since the javascript code requirements for extensions are lessened in the process. Once that library is cached in your browser, it does everything without requiring any further downloads.

Jiminimonka wrote: If Mootools is using up too many resources on your server and that is an issue, you need to upgrade, seriously, as your server must be from the 1980s.

first: learn to read = work in progress

rexet wrote: that damned mootools in j2.5 takes 50% of my pages weight

my website is on a Intel Xeon E3-1270 3.40GHZ dedicated server, 4MB memory with mysql on a separete SSD disk

@Goreman: thanks for your depth answer