Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter craigmilam

    (@craigmilam)

    Hi Marko, just wanted to thank you again for trying to help me out here.

    I went ahead and just disabled CSS minification in w3tc as it was creating minified CSS files that Avada was continuing to serve anyway and adding bloat.

    I tried manually combining the CSS files but it did not stop Avada from serving their theme files.

    Manually combining js files did help me reduce server requests and helped my Google page speed go up by 15 points on desktop, so that is a positive.

    In the future I’d love to know if there is a way to stop Avada from serving their CSS files and only use w3tc for CSS file minification/combination. Thanks again for you help!

    Thread Starter craigmilam

    (@craigmilam)

    Hi Marko, i an aware that this is valid Mark up. The issue is, the css being printed by Avada is the exact same css as that which is in the minify file… meaning I’m downloading the css rules twice. This is a problem bc there’s 100+kb of css in both the minify file and the Avada css (since they are the exact same).

    I want to only use the css file from w3tc and not the css from Avada. With the js files w3tc replaces the Avada js files. In my case w3tc is creating the css minify file and not replacing the Avada file (or inline css as it is now).

    • This reply was modified 4 years, 2 months ago by craigmilam.
    Thread Starter craigmilam

    (@craigmilam)

    Ok I’ve disabled line break removal for css. If you check the page now, you will see the avada css printed inline (it was printed inline but was difficult to see). Let me know if you can see it now. So now w3tc is serving the minified css file and avada is printing that css inline in the body of the HTML.

    Thread Starter craigmilam

    (@craigmilam)

    Hi Marko, thank you for the prompt support. The core issue is still not resolved. It is now including the minified css file from w3tc plus other files from avada and printing the main Avada css styles inline.

    • This reply was modified 4 years, 2 months ago by craigmilam.
    Thread Starter craigmilam

    (@craigmilam)

    Hi Marko, yes sorry I incorrectly stated that I had linebreaks enabled. I checked and that was not the case so I enabled them in the plugin.

    I’ve disabled CSS compiler in the Avada performance section, purged the Avada Cache, saved and purged cache in w3tc, and purged cloudflare cache.

    Now the css is being printed inline in the html.

    Thread Starter craigmilam

    (@craigmilam)

    Hi Marko,

    I just checked again. When I posted this question it was doubling all CSS files. I do have linebreaks enabled in the HTML section of the plugin but that doesn’t seem to be working. Currently I have CSS minification active and minification set to Auto. These two files are the same code – 3b850c6a355b311778146b0c11ad294c.min.css (Avada) & fbd14.css (w3tc) – I’ve turned off js compiling in Avada – CSS compiling is set to ‘file’.

    • This reply was modified 4 years, 2 months ago by craigmilam.
    • This reply was modified 4 years, 2 months ago by craigmilam.
Viewing 6 replies - 1 through 6 (of 6 total)