LCP request discovery" audit incorrectly reports "fetchpriority=high" should be applied. #16779
Description
FAQ
- Yes, my issue is not about variability or throttling.
- Yes, my issue is not about a specific accessibility audit (file with axe-core instead).
- Yes, my issue is not answered by other FAQs.
URL
https:/example.com/anyweb
What happened?
Hello Lighthouse Team,
I'm running a Lighthouse audit and encountering an incorrect result in the "LCP request discovery" section.
Actual Behavior: The audit fails the check "fetchpriority=high should be applied", as shown in the attached screenshot.
Expected Behavior: This check should pass, as the LCP element identified by Lighthouse already has the fetchpriority="high" attribute.
Evidence: Here is the HTML snippet for the LCP element, taken directly from the Lighthouse report:
HTML
<img alt="" fetchpriority="high" height="540" loading="eager" src="[...]" width="960">
As you can see, the fetchpriority="high" attribute is clearly present on the tag.
I suspect the audit might be incorrectly parsing the attribute, perhaps because the value is quoted ("high"). This is valid HTML, so the audit should be able to recognize it.
Thank you for looking into this.
What did you expect?
I expect the "fetchpriority=high" should be applied check to pass.
The Lighthouse report itself shows that the LCP element already has the fetchpriority="high" attribute, so this audit should show a green checkmark, not a red error.
What have you tried?
No response
How were you running Lighthouse?
Chrome DevTools, PageSpeed Insights
Lighthouse Version
13.0.1
Chrome Version
No response
Node Version
No response
OS
No response