Title: Load CSS asynchronously
Last modified: February 27, 2023

---

# Load CSS asynchronously

 *  Resolved [Pixelwunder](https://wordpress.org/support/users/pixelwunder/)
 * (@pixelwunder)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/load-css-asynchronously/)
 * The CSS file should be loaded asynchronously to improve the FCP value. This can
   be set in the CSS settings and UCSS Inline is automatically activated.
 * We have 65,000 pages, crawling the site takes about 6 hours. If the CSS code 
   via quic.cloud would take weeks. And start from the beginning with every purchasing.
   In addition, this is also relatively costly.
 * What other options are there?

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

 *  [serpentdriver](https://wordpress.org/support/users/serpentdriver/)
 * (@serpentdriver)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/load-css-asynchronously/#post-16509862)
 * There are different opinions about the asynchronous loading of CSS. My take on
   this is that you shouldn’t use CSS asynchronous loading because it introduces
   content shifting, and content shifting doesn’t like PageSpeed at all. CSS loading
   must take precedence over everything else. This means that you are better off
   using special deferred javascript and using lazy load for the images. With this
   you achieve more than with the asynchronous (=delayed) loading of CSS.
 * And if crawling takes too long, there are alternatives for the built-in crawler
   that can crawl 200,000 URLs in 1 hour.
 *  Thread Starter [Pixelwunder](https://wordpress.org/support/users/pixelwunder/)
 * (@pixelwunder)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/load-css-asynchronously/#post-16509921)
 * “And if crawling takes too long, there are alternatives for the built-in crawler
   that can crawl 200,000 URLs in 1 hour.”
 * What alternatives are we talking about here? Or do you mean the settings? These
   look like this at the moment:
 * Delay: 1000
   Run Duration: 400Interval between Rund: 60Crawl Interval: 1800Threads:
   6Timeout: 40Server load Limit: 2
 *  [serpentdriver](https://wordpress.org/support/users/serpentdriver/)
 * (@serpentdriver)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/load-css-asynchronously/#post-16509926)
 * Check my profile…
 *  [serpentdriver](https://wordpress.org/support/users/serpentdriver/)
 * (@serpentdriver)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/load-css-asynchronously/#post-16509943)
 * btw. You have completely wrong crawler settings, but that depends on the kind
   of your hosting.
 *  Thread Starter [Pixelwunder](https://wordpress.org/support/users/pixelwunder/)
 * (@pixelwunder)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/load-css-asynchronously/#post-16510075)
 * And which settings would be correct?
 *  [serpentdriver](https://wordpress.org/support/users/serpentdriver/)
 * (@serpentdriver)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/load-css-asynchronously/#post-16510177)
 * The built-in crawler doesn’t allow “correct” settings, because settings depend
   on your hosting and the load, but the load detection is buggy.

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

The topic ‘Load CSS asynchronously’ is closed to new replies.

 * ![](https://ps.w.org/litespeed-cache/assets/icon-256x256.png?rev=2554181)
 * [LiteSpeed Cache](https://wordpress.org/plugins/litespeed-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/litespeed-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/litespeed-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/litespeed-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/litespeed-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/litespeed-cache/reviews/)

 * 6 replies
 * 2 participants
 * Last reply from: [serpentdriver](https://wordpress.org/support/users/serpentdriver/)
 * Last activity: [3 years, 3 months ago](https://wordpress.org/support/topic/load-css-asynchronously/#post-16510177)
 * Status: resolved