Title: Different method for lazy loading CSS
Last modified: April 2, 2018

---

# Different method for lazy loading CSS

 *  Resolved [Prayag Verma](https://wordpress.org/support/users/stylifyyourblog/)
 * (@stylifyyourblog)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/different-method-for-lazy-loading-css/)
 * Is it possible to use a method different than rel=preload for lazy loading CSS?
 * The main reason behind this is because the rel=preload attribute is no longer
   supported in Firefox (Refer to [https://developer.mozilla.org/en-US/docs/Web/HTML/Preloading_content#Browser_compatibility](https://developer.mozilla.org/en-US/docs/Web/HTML/Preloading_content#Browser_compatibility))

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

 *  Plugin Author [Raul P.](https://wordpress.org/support/users/alignak/)
 * (@alignak)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/different-method-for-lazy-loading-css/#post-10137578)
 * I don’t think changing it is a good idea.
 * Chrome supports it, Firefox support was poor and they had a bug with it, but 
   it also says an improved versio with cache support (finally catching up with 
   chrome) is coming the next version. This can be a couple or months or even less,
   since this feature is critical.
 * Its basically a browser change that its breaking things, not the plugin. People
   that use firefox they understand that browser updates may break things.
 *  Thread Starter [Prayag Verma](https://wordpress.org/support/users/stylifyyourblog/)
 * (@stylifyyourblog)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/different-method-for-lazy-loading-css/#post-10160609)
 * Hi Raul,
 * Thanks for the reply. I totally understand the sentiment behind your decision.
 * But the problem is that, as it currently stands, this feature is not supported
   in 3 major versions of Firefox (57,58,59). Firefox 60 is due to be released in
   May 2018 ( [https://wiki.mozilla.org/Release_Management/Calendar](https://wiki.mozilla.org/Release_Management/Calendar))
   so there is still around a month till this feature re-lands in Firefox. Also,
   if you check Bugzilla, there are currently lots of open issues related to preload
   which are still in works (Refer to [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=preload](https://bugzilla.mozilla.org/buglist.cgi?quicksearch=preload)
   and [https://i.imgur.com/jbrTG0o.png](https://i.imgur.com/jbrTG0o.png) )
 * If possible, is there a way to include a small warning near this option in the
   plugin informing the users about this feature not being supported in Firefox
 *  Thread Starter [Prayag Verma](https://wordpress.org/support/users/stylifyyourblog/)
 * (@stylifyyourblog)
 * [7 years, 9 months ago](https://wordpress.org/support/topic/different-method-for-lazy-loading-css/#post-10529966)
 * Hi Raul,
 * Sorry for posting in this old thread. Firefox seems to have delayed implementing
   this even further ( Refer to the thread [https://bugzilla.mozilla.org/show_bug.cgi?id=1394778](https://bugzilla.mozilla.org/show_bug.cgi?id=1394778)).
   Also, some of the other browsers also don’t support this feature (like old browsers
   like Internet Explorer and low data browsers like Opera Mini, UC Browser for 
   Android – Refer to [https://caniuse.com/#feat=link-rel-preload](https://caniuse.com/#feat=link-rel-preload))
 * After thinking, changing to a different method for asynchronously loading CSS
   wouldn’t be required to resolve this issue. If we can add polyfill for rel=preload
   when this feature is enabled, then that would also resolve this problem. loadCSS
   has created a polyfill for rel=preload – [https://github.com/filamentgroup/loadCSS/blob/master/src/cssrelpreload.js](https://github.com/filamentgroup/loadCSS/blob/master/src/cssrelpreload.js)(
   Compressed version – [https://cdnjs.cloudflare.com/ajax/libs/loadCSS/2.0.1/cssrelpreload.min.js](https://cdnjs.cloudflare.com/ajax/libs/loadCSS/2.0.1/cssrelpreload.min.js))
 *  Plugin Author [Raul P.](https://wordpress.org/support/users/alignak/)
 * (@alignak)
 * [7 years, 8 months ago](https://wordpress.org/support/topic/different-method-for-lazy-loading-css/#post-10612932)
 * Sorry for the late reply, but the plugin is already using LoadCSS polyfill.
 * It’s inlined once you enable async css, but async css loads css files randomly…
   you need to understand that css files won’t load in order, so you must only have
   one single css file.
 * You should probably disable css processing on FVM and then manually dequeue and
   merge your own css code.

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

The topic ‘Different method for lazy loading CSS’ is closed to new replies.

 * ![](https://ps.w.org/fast-velocity-minify/assets/icon-128x128.jpg?rev=1440946)
 * [Fast Velocity Minify](https://wordpress.org/plugins/fast-velocity-minify/)
 * [Support Threads](https://wordpress.org/support/plugin/fast-velocity-minify/)
 * [Active Topics](https://wordpress.org/support/plugin/fast-velocity-minify/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/fast-velocity-minify/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/fast-velocity-minify/reviews/)

## Tags

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

 * 4 replies
 * 2 participants
 * Last reply from: [Raul P.](https://wordpress.org/support/users/alignak/)
 * Last activity: [7 years, 8 months ago](https://wordpress.org/support/topic/different-method-for-lazy-loading-css/#post-10612932)
 * Status: resolved