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.
“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: 400
Interval between Rund: 60
Crawl Interval: 1800
Threads: 6
Timeout: 40
Server load Limit: 2
btw. You have completely wrong crawler settings, but that depends on the kind of your hosting.
And which settings would be correct?
The built-in crawler doesn’t allow “correct” settings, because settings depend on your hosting and the load, but the load detection is buggy.
