• Resolved Anonymous User 16110023

    (@anonymized-16110023)


    Hello, first of all, his is one of the best plugins around.

    I’ve checked:
    Defer CSS Loaded in the <BODY> (Footer)
    Yes, for all the stylesheet LINK tags that are moved or already loaded in the BODY

    But pagespeed still gives me that the combined css is not being deferred.

    Would you know how to fix it?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Gabe Livan

    (@gabelivan)

    @an0nimo If you’re sure those CSS files are moved to the BODY (from HEAD) via Asset CleanUp Pro or they are already in the BODY (note that this is not common), then Asset CleanUp Pro should make them non-render blocking. Please clear the cache and re-test.

    If you’re not comfortable posting your website’s URL here, you can send an email to support ( at ) assetcleanup [ dot ] com

    Thread Starter Anonymous User 16110023

    (@anonymized-16110023)

    Ive checked the path, its talking about a head css:

    <head>
    .
    .
    /wp-content/cache/asset-cleanup/css/head-847221043db634d241f989e3a189179717ffc403.css
    .
    .
    </head>

    Google is asking me to eliminate it because its render blocking, how can I achieve this using this plugin?

    The current setting for this is:

    Defer CSS Loaded in the <BODY> (Footer)
    Yes, for any stylesheet LINK tags moved from HEAD to BODY via Asset CleanUp Pro * default

    Plugin Author Gabe Livan

    (@gabelivan)

    @an0nimo my apologies for this late reply! If you have CSS loaded in the BODY or moved it to the BODY from HEAD, then it will be deferred. However, because you still have some CSS that is loaded in the HEAD and it’s render-blocking, Google PageSpeed will report that combined file which is in fact smaller than usual because otherwise (if you had not moved any CSS to there BODY), will be bigger in size since more combined render-blocking would have been merged into that large combined file.

    Even though it’s smaller in size, it’s still render-blocking. One way would be to implement critical CSS (https://assetcleanup.com/docs/critical-css-how-to-implement-it-to-completely-reduce-render-blocking-stylesheets/) if you’re comfortable editing PHP files (this is the best way to clear render-blocking CSS, but a bit technical, I have to admit that) or “Preload (async)” more of the CSS stylesheets that are loading in the HEAD section of the website, but you have to make sure you’re applying this only to files that are not styling the above the fold. Even so, you will still end up with one/two files that are render-blocking, but at least, the combined CSS would be even smaller and shouldn’t bother you that much.

    Let me know if this helps or need more clarification. Perhaps having extra documentation about render-blocking CSS/JS would be a good idea.

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

The topic ‘Defer CSS not completely working’ is closed to new replies.