Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Frank Goossens

    (@futtta)

    (1) it detects changes
    (2) “above the fold optimization” automatically detects the critical CSS, whereas for AO you’ll have to find that yourself (using an external tool), so Google might not have “liked” the CSS you entered.

    frank

    Thread Starter Jim Zarkadas

    (@jimzar)

    Thanks for the reply!

    Concerning the second question, I manually add the CSS code to the “above the fold optimization” and it’s the same as autoptimize.

    Did anyone had the same issue ? I guess it has to do with the way css file is being loaded.

    Plugin Author Frank Goossens

    (@futtta)

    I’ll have a look at the code of “above the fold optimization” one of these days to see if they “inline & defer” differently.

    frank

    Thread Starter Jim Zarkadas

    (@jimzar)

    Ok cool ?? Also I made some research and I think that above the fold plugin, uses this tool for loading the CSS file https://github.com/filamentgroup/loadCSS

    Thanks,
    Jim

    Plugin Author Frank Goossens

    (@futtta)

    AO uses another approach indeed;
    * when the DOMContentLoaded event (with a fallback to onload) occurs it executes a JS function deferredCSS
    * deferredCSS will execute lCss for every stylesheet that has to be loaded
    * lCss appends the stylesheet to the start of the <head>
    * all stylesheets are also added to a <noscript>-block in the head of the HTML

    You can see the code here.

    hope this clarifies,
    frank

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Above the fold and caching questions’ is closed to new replies.