Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • cappu Friend
    #186381

    Hi,

    I’m new to T3v3 and quite fascinated about the Argo Template and finally managed it to setup. 😎

    Any strategy to performance boost Argo: tools, settings, etc. – What do you suggest?
    Google Pagespeed Insights gives me a 0.

    Thanks for any hint.

    Kind regards, Bernhard

    Saguaros Moderator
    #488802

    Hi Bernhard,

    Here is my suggestion:

    – Disable Development mode in backend settings so that your site will load css instead of less.

    – Enable cache in your site, it helps much

    – enable the css / js optimization feature of T3. That will reduce the number of css / js files. Now you have so many css file to load. Please manually check css file and remove any unused css

    – Using our Amazon S3 component allows using CDN (cloudfront) (or you can try other component like this) and also has option to update cache folder with cron job.. which can be set to lower limit to have regular update of cache on cloud. Running without cache on is bound to make the site slower. However, the main reason for slow site would still be the number of items it has to fetch (css , js, images, external scripts / social stuff).

    – Reconsider the usage of the “important” plugins and modules or unused article content, sometimes switching them off is better

    Regards.

    cappu Friend
    #489021

    Hi Saguaros,

    Exactly what I was looking for. Thanks for all this information.

    I have two issues, though:

    – With Joomla 3.0.1 and JA Argo: When I disable Development Mode I may set ‘Optimize CSS’ and it works – but nothing for JavaScript.
    – To avoid overwrites of my individual theme settings, I created my own theme by copying the orange less and renamed it. – In Development Mode the framework uses my theme, but not if its disabled. – What am I missing?

    Thanks for any hint.

    Kind regards,

    Bernhard

    Saguaros Moderator
    #489181

    Hi Bernhard,

    – Yes, currently, there is only one option for compressing css

    – When Development mode is disabled and after making change in LESS file, you need to compile LESS to CSS via backend of this template.

    Please give it a try.

    cappu Friend
    #489209

    Hi Saguaros,

    I gave it a try. Do get “Unexpected error. Please refresh page an try again” error message on compile LESS to CSS. I check the folder rights, everything seems to be correct. But no folder with theme name got created in under /css/themes. –

    Any ideas?

    Thanks again for you help, Bernhard

    Saguaros Moderator
    #489491

    Hi Bernhard,

    Did you try to update T3 to the latest version (backup your site first before upgrading)?

    I tried to create a new theme folder under directory: /templates/ja_argo/less/themes/awesome

    Then copy some less file from another theme.

    Go to backend > template manager > compile less to css

    But I can see it create a same folder in /templates/ja_argo/css/theme

    It should work 🙂

    cappu Friend
    #489522

    Hi Saguaros,

    I updated to the latest T3 1.2.2 – the error still occurs.

    Acutally, I do get a 500 error from the server – this is what I see in Firebug on the GET-Request to the t3action=lesscall.

    No error logs.

    Could this be a limit in server resources?

    Thanks again for any hint,

    Bernhard

    cappu Friend
    #489529

    Hi Saguaros,

    I contacted the hoster and we successfully compiled LESS to CSS : – It is the server limit which causes the 500 error and finally the “Unexpected error. Please refresh page an try again” error message during “Compile LESS to CSS”. The compile process needs quite a bit ressources…

    Thanks for your help and time,

    Kind regards,

    Bernhard

    Saguaros Moderator
    #489906

    Glad it works now, let me know if you need further helps.

    Best Regards

Viewing 9 posts - 1 through 9 (of 9 total)

This topic contains 9 replies, has 2 voices, and was last updated by  Saguaros 11 years, 7 months ago.

We moved to new unified forum. Please post all new support queries in our New Forum