Conversation
OrKoN
force-pushed
the
orkon/lighthouse
branch
3 times, most recently
from
4ad8fa2 to
2f158cb
Compare
OrKoN
force-pushed
the
orkon/lighthouse
branch
6 times, most recently
from
55a3355 to
092a16a
Compare
OrKoN
commented
Feb 11, 2026
OrKoN
force-pushed
the
orkon/lighthouse
branch
2 times, most recently
from
eb3d938 to
df770c7
Compare
OrKoN
force-pushed
the
orkon/lighthouse
branch
3 times, most recently
from
289bc0d to
f492e90
Compare
OrKoN
force-pushed
the
orkon/lighthouse
branch
4 times, most recently
from
661364c to
30ae425
Compare
OrKoN
force-pushed
the
orkon/lighthouse
branch
from
30ae425 to
c2a6db4
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Collaborator
Author
|
@zyzyzyryxy could you please review the bundling setup and perhaps you could run an import CL to see if there will be any complaints from linters? |
Collaborator
Author
|
@paulirish could you please review for the lighthouse integration? |
OrKoN
commented
Feb 16, 2026
OrKoN
force-pushed
the
orkon/lighthouse
branch
from
f34cffe to
e4ced16
Compare
Collaborator
Author
|
@zyzyzyryxy PT(another)L, the notices are now combined into the one file (source is copied to our source). |
OrKoN
force-pushed
the
orkon/lighthouse
branch
from
e4ced16 to
b3cd5ee
Compare
github-merge-queue bot
pushed a commit
that referenced
this pull request
Feb 23, 2026
This is a draft for new skill to debug and optimize LCP scores, going hand in hand with #831. Base for this skill is key authoritative learning material from web.dev, about debugging and optimizing LCP, mainly: - http://web.dev/articles/lcp - http://web.dev/articles/optimize-lcp - https://web.dev/articles/top-cwv I gave the content of those articles together with the [tool reference](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/tool-reference.md), the README and the chrome-devtools core skill to both Claude Opus 4.6 and Gemini 3 Pro and their respective skill creator skills. The final skill in this PR is a merge of multiple runs with both models. The snippets to run with `evaluate_script` is something only Opus came up with, but I think it's quite nice, though our own `performance_*` tools might give the same insight but likely with more overhead (meaning tokens).
OrKoN
force-pushed
the
orkon/lighthouse
branch
from
cd1897f to
d5a603c
Compare
OrKoN
commented
Feb 23, 2026
OrKoN
force-pushed
the
orkon/lighthouse
branch
from
99f9f5d to
88a2f44
Compare
OrKoN
force-pushed
the
orkon/lighthouse
branch
from
88a2f44 to
195e6e3
Compare
OrKoN
force-pushed
the
orkon/lighthouse
branch
from
24b0807 to
a061909
Compare
zyzyzyryxy
approved these changes
Feb 24, 2026
natorion
approved these changes
Feb 26, 2026
OrKoN
pushed a commit
that referenced
this pull request
Mar 5, 2026
🤖 I have created a release *beep* *boop* --- ## [0.19.0](chrome-devtools-mcp-v0.18.1...chrome-devtools-mcp-v0.19.0) (2026-03-05) ### 🎉 Features * add pageId routing for parallel multi-agent workflows ([#1022](#1022)) ([caf601a](caf601a)), closes [#1019](#1019) * Add skill which helps with onboarding of the mcp server ([#1083](#1083)) ([7273f16](7273f16)) * integrate Lighthouse audits ([#831](#831)) ([dfdac26](dfdac26)) ### 🛠️ Fixes * improve error messages around --auto-connect ([#1075](#1075)) ([bcb852d](bcb852d)) * improve tool descriptions ([#965](#965)) ([bdbbc84](bdbbc84)) * repair broken markdown and extract snippets in a11y-debugging skill ([#1096](#1096)) ([adac7c5](adac7c5)) * simplify emulation and script tools ([#1073](#1073)) ([e51ba47](e51ba47)) * simplify focus state management ([#1063](#1063)) ([f763da2](f763da2)) * tweak lighthouse description ([#1112](#1112)) ([5538180](5538180)) ### 📄 Documentation * Adapt a11y skill to utilize Lighthouse ([#1054](#1054)) ([21634e6](21634e6)) * add feature release checklist to CONTRIBUTING.md ([#1118](#1118)) ([0378457](0378457)) * fix typo in README regarding slim mode ([#1093](#1093)) ([92f2c7b](92f2c7b)) ### 🏗️ Refactor * clean up more of the context getters ([#1062](#1062)) ([9628dab](9628dab)) * consistently use McpPage in tools ([#1057](#1057)) ([302e5a0](302e5a0)) * improve type safety for page scoped tools ([#1051](#1051)) ([5f694c6](5f694c6)) * make cdp resolvers use McpPage ([#1060](#1060)) ([d6c06c5](d6c06c5)) * move dialog handling to McpPage ([#1059](#1059)) ([40c241b](40c241b)) * move server to a separate file ([#1043](#1043)) ([a8bf3e5](a8bf3e5)) * remove page passing via context ([#1061](#1061)) ([4cb5a17](4cb5a17)) * set defaults to performance trace tool ([#1090](#1090)) ([dfa9b79](dfa9b79)) * simplify the response texts ([#1095](#1095)) ([cb0079e](cb0079e)) * type-cast as internal CdpPage interface ([#1064](#1064)) ([2d5e4fa](2d5e4fa)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
wolfib
pushed a commit
to wolfib/chrome-devtools-mcp
that referenced
this pull request
Mar 10, 2026
This is a draft for new skill to debug and optimize LCP scores, going hand in hand with ChromeDevTools#831. Base for this skill is key authoritative learning material from web.dev, about debugging and optimizing LCP, mainly: - http://web.dev/articles/lcp - http://web.dev/articles/optimize-lcp - https://web.dev/articles/top-cwv I gave the content of those articles together with the [tool reference](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/tool-reference.md), the README and the chrome-devtools core skill to both Claude Opus 4.6 and Gemini 3 Pro and their respective skill creator skills. The final skill in this PR is a merge of multiple runs with both models. The snippets to run with `evaluate_script` is something only Opus came up with, but I think it's quite nice, though our own `performance_*` tools might give the same insight but likely with more overhead (meaning tokens).
wolfib
pushed a commit
to wolfib/chrome-devtools-mcp
that referenced
this pull request
Mar 10, 2026
This PR adds tool to perform navigation and snapshot audits using Lighthouse for Accessibility, SEO and Best practices. For performance audits existing tools can be used. Closes ChromeDevTools#473
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds tool to perform navigation and snapshot audits using Lighthouse for Accessibility, SEO and Best practices. For performance audits existing tools can be used.
Closes #473