I have the latest AkkebaBackupPro and we are currently working on optimizing the site - we're using JBETOLO, which is a great component.
The site is www.innerwise.eu
We have resolved many issues and an now at the point of tidying up the final bits and pieces.
We have noticed that there are 2 JS files (akeebajq.js and akjqmigrate.js) that are injected into the frontend - even though I have frontend backups disabled.
The issues are ....
- why are these files there in the first place and if, how can they be disabled?
- why are they coming in in such a "exclusive" position, that compression tools cannot include them into the combined & minified JS.
- As you know, CSS should be loaded BEFORE JS, so CSS and JS can be loaded in parallel. your files come in so early, that the css & further pageload is delayed (check with webspeedtest.org). Can this be changed?
Gobezu, the JBETOLO dev wrote:
... the files akeebajq.js and akjqmigrate.js comes from akeeba and although the jbetolo plugin is placed as system plugin and as the last one being processed, the page doesn't contain those files at the time of parsing the body. This makes it extremely difficult to do anything about with jbetolo. I am not sure why the developer chose to circumvent everybody including the site owner out from the choice of doing what they want with it, including merging....
Thanks for your response & good work.
Gernot