Render-blocking request waterfall not flagged
FAQ
- [X] Yes, my issue is not about variability or throttling.
- [X] Yes, my issue is not about a specific accessibility audit (file with axe-core instead).
URL
https://discreet-ginger-bench.glitch.me/
What happened?
Eliminate render-blocking requests passed.
Critical request chains correctly identified a render-blocking waterfall 4 layers deep.
What did you expect?
Eliminate render-blocking requests to identify every render-blocking request in the chain.
What have you tried?
How were you running Lighthouse?
Chrome DevTools
Lighthouse Version
9.2.0
Chrome Version
M99
Node Version
No response
OS
macOS
Relevant log output
The content at that location might change, so the waterfall specifically is
script.js
|- document.write style.css
|- @import other-style.css
|- @font-face font.woff2
And hey everyone 👋 :)
And hey everyone 👋 :)
Hey Patrick 👋 !
https://ludicrous-curved-capybara.glitch.me/index.html
Link isn't working for me, you got another?
Ah sorry I updated it already 🤦
this one is just for you, won't touch, promise :) https://discreet-ginger-bench.glitch.me/index.html
this one is just for you, won't touch, promise :)
nice, it still works. @patrickhulce delivers!
i see this today:
just the render blocking css is there, but not the loader.js file. I know in render-blocking requests audit we filter out if < 50ms, but in crc audit we don't use lantern to filter the critical requests. so that's the mismatch.