LinkElements gatherer encountered an error: Expected attribute delimiter at offset 94

[mattzeunert]

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).

URL

https://calendly.com/matt-665/debugbear-demo?month=2023-03

What happened?

Run lighthouse --view https://calendly.com/matt-665/debugbear-demo\?month\=2023-03

There's no SEO score:

What did you expect?

An SEO score should be reported, it worked with Lighthouse 10.0.1.

Started seeing this error on bunch of pages when trying to upgrade to 10.1.0.

What have you tried?

No response

How were you running Lighthouse?

CLI

Lighthouse Version

10.1.0

Chrome Version

114

Node Version

No response

OS

No response

Relevant log output

No response

[brendankenny]

Thanks @mattzeunert! Looks like this is due to updating http-link-header in 10.1.0.

From the example page, it's attempting to parse the header <https://assets.calendly.com/assets/booking/css/booking-5e8a798d.css>; rel=preload; as=style; nopush and throwing when it doesn't find a '=' after nopush.

I haven't looked into why it got stricter on this. The error condition looks like it was in the old version as well, so something else must have gotten stricter/changed requirements and led back to that code path.

[adamraine]

jhermsmeier/node-http-link-header#29

[noon92]

I can confirm this is still happening:
https://pagespeed.web.dev/analysis/https-www-rustil-co-il/3jaf8imvmb?form_factor=mobile

[adamraine]

@nagumii Lighthouse 10.1.1 isn't in pagespeed yet, that will probably be updated this week.

[noon92]

Thanks, appreciate the response!