DevTools Adds Lighthouse Checks

Chrome DevTools’ Model Context Protocol server now lets coding agents run Lighthouse audits, inspect memory leaks, check accessibility, and troubleshoot Largest Contentful Paint from inside Chrome workflows. (developer.chrome.com) Google documented the additions in its Chrome 146 DevTools notes on March 10, 2026, saying the DevTools Model Context Protocol server gained integrated Lighthouse audits, new accessibility and Largest Contentful Paint skills, and a `take_memory_snapshot` tool. (developer.chrome.com) The server itself is a bridge between Chrome and artificial intelligence coding tools. Google launched the public preview on September 23, 2025, describing it as a Model Context Protocol server that lets assistants control Chrome, record traces, inspect pages, and analyze what code does in a live browser. (developer.chrome.com) Lighthouse is Chrome’s automated site-auditing system. Google says it can test performance, accessibility, search engine optimization, and other best practices on public or authenticated pages, then generate a report developers can use to fix failures. (developer.chrome.com) Largest Contentful Paint is a speed metric for the main thing a user sees first. Google defines it as the time from the start of page load until the largest image or text block in the viewport is rendered, which is why it is used as a key page-load signal in Chrome’s performance tooling. (web.dev) Accessibility checks cover a different class of bugs. Chrome’s Lighthouse documentation says those audits are scored as pass or fail and weighted by user-impact assessments, which makes them useful for catching missing labels, low-contrast elements, and other barriers before code ships. (developer.chrome.com) The memory-leak tooling arrived in the project’s release stream at the start of April. The GitHub release for version 0.21.0, published April 1, 2026, lists “a skill for detecting memory leaks using `take_memory_snapshot`,” alongside other updates to the server. (github.com) Google has also been tightening the link between Lighthouse and DevTools more broadly. In Lighthouse 13, Chrome said it was consolidating older performance audits with newer “insights” shared across Lighthouse and the DevTools Performance panel, reducing the gap between one-off reports and trace-based debugging. (developer.chrome.com) That leaves developers with fewer handoffs: the browser can now supply the page, the trace, the audit, and the debugging hooks in the same toolchain the agent already uses. (developer.chrome.com)