Autoptimise + WPFC

  • Resolved andrewf1997

    (@andrewf1997)


    2 years, 9 months ago

    I am using Autoptimise with WPFC pro and I just want to make sure there will be no clash in the settings. I have read that you suggested to disable any minification settings in WPFC and I first wanted to check if this is still true as I need to action this if so (currently have them all enabled in WPFC). The main thing I was wondering around is whether it’s safe to use the “combine” settings in WPFC, that being combine JS and combine CSS – or whether it’s best to totally avoid any JS / CSS settings in WPFC

    • This topic was modified 2 years, 9 months ago by andrewf1997.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    2 years, 9 months ago

    as AO has it’s own function to combine CSS/ JS, you should indeed leave those settings off in WPFC Andrew.

    hope this helps,
    frank

    Thread Starter andrewf1997

    (@andrewf1997)

    2 years, 9 months ago

    Thanks, I will action that this week as to ensure the chance of issues in the future is minimised

    Quick follow up question – I use a site with under 50 pages and some of those pages do have different custom CSS on a per page basis (however not all of them, most of the styling is pulled from a global styling headers and footers plugin) – In this case would you suggest that I can use “aggregate inline CSS” or it will not be as beneficial for me / could make the cache fill up fast

    The custom CSS will not change on a per page load basis so does that mean that once a user has visited all 50 of my pages once then the files will essentially start to have been cached effectively ? Or is it not that simple ?

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    2 years, 9 months ago

    there usually is very little performance advantage to be expected from “also aggregate inline CSS”, and when aggregating it the full autoptimized CSS will be different for each page (because the inline CSS was different) so the same autoptimized CSS cannot be used from cache. based on these, I would advice against “also aggregate inline CSS” really :-/

    Thread Starter andrewf1997

    (@andrewf1997)

    2 years, 9 months ago

    awesome thanks for letting me know – if it will avoid the cache filling up fast I’d rather leave it off anyway

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    2 years, 8 months ago

    you’re welcome, feel free to leave a review of the plugin and support here! 🙂

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Autoptimise + WPFC’ is closed to new replies.