Force path-based rules? Full-Page Cache?

  • dichiarativo

    (@dichiarativo)


    7 years ago

    Q 1)
    I understand “Force path-based rules to be generated for pages?” will create a CCSS for each page.
    If I do NOT force path-based rules, one single CCSS will be created for all pages.
    Will this CCSS be created after having analysed ALL of the pages? and so I can be comfortable that, for example, pages without and pages with a GravityForm will both display well?
    Presumably, having fewer CCSS would be preferable as the autoptimise.css that goes with it can be cached in the user’s browser for subsequent pages visited?

    Q 2) I use W3 full page cache. Does this play well with CCSS? Will the full-page cache automatically purge if a new CCSS and accompanying autoptimise.css are generated?

    Thanks!
    Mel

Viewing 1 replies (of 1 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    7 years ago

    Will this CCSS be created after having analysed ALL of the pages? and so I can be comfortable that, for example, pages without and pages with a GravityForm will both display well?

    no, in that case one random page will be used to extract critical CSS and that will be used accross all pages, so the CCSS might have gravityforms CSS but might not.

    Presumably, having fewer CCSS would be preferable as the autoptimise.css that goes with it can be cached in the user’s browser for subsequent pages visited?

    the critical CSS is not served as a file, but is inlined, hence having few or many does not really matter 🙂

    I use W3 full page cache. Does this play well with CCSS? Will the full-page cache automatically purge if a new CCSS and accompanying autoptimise.css are generated?

    No, CCSS does not have any logic to clear page caches cache (W3TC or other).

    hope this clarifies,
    frank

Viewing 1 replies (of 1 total)

The topic ‘Force path-based rules? Full-Page Cache?’ is closed to new replies.