GoogleChrome / GoogleChrome/lighthouse

[image-elements] Protocol error (CSS.getMatchedStylesForNode): CSS agent was not enabled

Open
#13,928 1 comment 0 reactions 0 assignees View on GitHub
bug needs-investigation P1.5
Dominant language
JavaScript
Stars
30.8k
Forks
9.8k
Avg merge
1d 14h
Merged PRs (30d)
20

Description

### FAQ

- [X] Yes, my issue is not about [variability](https://github.com/GoogleChrome/lighthouse/blob/master/docs/variability.md) or [throttling](https://github.com/GoogleChrome/lighthouse/blob/master/docs/throttling.md).
- [X] Yes, my issue is not about a specific accessibility audit (file with [axe-core](https://github.com/dequelabs/axe-core) instead).

### URL

https://sidigital.es/servicios/coste-por-pagina/

### What happened?

In **report.artifacts.ImageElements**

Protocol error (CSS.getMatchedStylesForNode): CSS agent was not enabled {"protocolError":"CSS agent was not enabled","protocolMethod":"CSS.getMatchedStylesForNode"}

### What did you expect?

Getting correct image details

### What have you tried?

_No response_

### How were you running Lighthouse?

node

### Lighthouse Version

9.1.0

### Chrome Version

_No response_

### Node Version

_No response_

### OS

_No response_

### Relevant log output

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by tracing the report.artifacts.ImageElements path and its CSS.getMatchedStylesForNode protocol call, reproducing the failure against the reported URL with Lighthouse 9.1.0 under Node. Identify why the CSS agent is unavailable, then verify that image details are collected without the protocol error.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.