Title: Css not deferred
Last modified: November 20, 2021

---

# Css not deferred

 *  Resolved [kikko088](https://wordpress.org/support/users/kikko088/)
 * (@kikko088)
 * [4 years, 6 months ago](https://wordpress.org/support/topic/css-not-deferred/)
 * Hello,
 * I’ve some issue deferring the css, maybe it is already correct but I’m not sure,
   I have my own way to extract critical css and I’m pushing them in the code manually,
   in the plugin I’ve enabled:
 *     ```
       Inline "above the fold CSS" while loading the main autoptimized CSS only after page load. Check the FAQ for more info. This can be fully automated for different types of pages on the CriticalCSS tab.
       ```
   
 * added a simple `.body{}` in ti, I can see the body class inline but the normal
   file is loaded in this way:
 *     ```
       <noscript id="aonoscrcss"><link media="all" href="http://192.168.1.78/wordpress/wp-content/cache/autoptimize/css/autoptimize_59e62629fb3add6f1286e32b678c4466.css" rel="stylesheet" /></noscript>
       ```
   
 * and:
 *     ```
       <link rel="stylesheet" media="print" href="http://192.168.1.78/wordpress/wp-content/cache/autoptimize/css/autoptimize_59e62629fb3add6f1286e32b678c4466.css" onload="this.onload=null;this.media='all';" />
       ```
   
 * I suppose they should have the `rel="preload"` but I don’t see it…maybe this 
   is a new way to preload css (I’m not super updated)…am I doing something wrong?
 * everything is still in dev, I don’t have anything online
 * many thanks
    -  This topic was modified 4 years, 6 months ago by [kikko088](https://wordpress.org/support/users/kikko088/).
    -  This topic was modified 4 years, 6 months ago by [kikko088](https://wordpress.org/support/users/kikko088/).

Viewing 1 replies (of 1 total)

 *  Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [4 years, 6 months ago](https://wordpress.org/support/topic/css-not-deferred/#post-15088525)
 * the noscript is fallback for if JS is not available so can be (and is) ignored.
 * the last line is where deferring is done, albeit not using “preload” but instead
   the “load CSS simpler” method described at [https://www.filamentgroup.com/lab/load-css-simpler/](https://www.filamentgroup.com/lab/load-css-simpler/)
   which does make the CSS not-render-blocking 🙂
 * hope this clarifies,
    frank

Viewing 1 replies (of 1 total)

The topic ‘Css not deferred’ is closed to new replies.

 * ![](https://ps.w.org/autoptimize/assets/icon-256X256.png?rev=2211608)
 * [Autoptimize](https://wordpress.org/plugins/autoptimize/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/autoptimize/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/autoptimize/)
 * [Active Topics](https://wordpress.org/support/plugin/autoptimize/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/autoptimize/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/autoptimize/reviews/)

## Tags

 * [css](https://wordpress.org/support/topic-tag/css/)
 * [defer](https://wordpress.org/support/topic-tag/defer/)

 * 1 reply
 * 2 participants
 * Last reply from: [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * Last activity: [4 years, 6 months ago](https://wordpress.org/support/topic/css-not-deferred/#post-15088525)
 * Status: resolved