Google’s Lighthouse has long been the reference lab engine behind PageSpeed Insights and countless CI pipelines. Most teams know its headline categories (Performance, Accessibility, Best Practices, SEO) and the familiar 0–100 style scores on several of them. Chrome’s documentation now adds an experimental Agentic Browsing lane: how a page behaves when agents programmatically discover and use the interface. That is a different question from whether the same page feels fast and smooth when a human scrolls and taps. This post summarises what that category measures, how scoring works (and why it is not another weighted 0–100 average), and what it means for teams who already run Lighthouse on a schedule. Official detail lives in Chrome’s guide: Lighthouse agentic browsing scoring . What is Lighthouse Agentic Browsing? Agentic here means software agents (assistants, automation, or test harnesses) that need to discover, understand, and interact with your UI programmatically.…