I was troubleshooting why my public pages were slow to display content, even with post-loaded scripts and css and critical css inlined and found out that my css loading script was the problem.
The new css (below) flags an error that I think could be changed.
<link rel=preload href="/css/public/responsive_postloaded.css" as="style" onload="this.rel='stylesheet'">
Please try downloading CSE HTML Validator Pro again. You should get v16.0302 which should support rel="preload" and the "as" attribute. Please let me know how it works.
The as attribute tells the browser what it will be downloading. Possible as values include:
"script",
"style",
"image",
"media",
and "document".
(See the fetch spec for the full list.)
Omitting the as attribute, or having an invalid value is equivalent to an XHR request, where the browser doesn’t know what it is fetching, and fetches it with a fairly low priority.
Thanks Rick, that's a really good page. I'll add a link to it on our "link" element help page and add some warnings to CSE HTML Validator when the "as" attribute is not used and when the "crossorigin" attribute is not used but should be (for fonts when as="font").
I liked the page since it was in plain english and found it interesting. Also did a nice job explaining the difference between preload and prefetch and the previous options.
Can you do a test? Like create some crazy style sheet that if it is loaded then you would easily know? But even if it works with Chrome then you still have all the other browsers to consider.