Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteThe latest Lighthouse release listed by Google is v13.5.0, dated September 18, 2026. The most significant change for many developers arrived with Lighthouse 13: it replaced several older performance audits with consolidated insights while leaving the performance score unchanged. Lighthouse is also expanding into experimental checks for how reliably AI agents can discover and interact with websites.
What is the latest Lighthouse version?
Google’s Lighthouse releases page lists v13.5.0, published September 18, 2026. Its notes identify Agent Resource Discovery (ARD) as a notable new audit, alongside core changes including response-header capture support, user-flow navigation-abort handling, and updates to the llms.txt and WebMCP audits.
As an Amazon Associate I earn from qualifying purchases.
The release notes said Lighthouse 13.5.0 was expected to ship in Chrome DevTools with Chrome 156 and reach PageSpeed Insights within two weeks. That is the maintainers’ stated expectation, not confirmation that both rollouts have completed everywhere. Lighthouse’s version can differ across npm, the Chrome version embedding it, and the version served by PageSpeed Insights.
Recommended Free Tools
What changed in Lighthouse 13?
Lighthouse 13 moved toward shared performance insights with Chrome DevTools’ Performance panel. Several older audits were combined into insights, while others were removed. Google says these changes affected diagnostics and report structure, not the performance score: that score is based on metrics, and the replaced audits were non-scored.
#1 Best Overall
| Change | Previous audits or feature | What to know |
|---|---|---|
| Consolidated into an insight | layout-shifts, non-composited-animations, unsized-images |
Combined as cls-culprits-insight. |
| Consolidated into an insight | redirects, server-response-time, uses-text-compression |
Combined as document-latency-insight. |
| Replaced by an insight | dom-size |
Use dom-size-insight in place of the old audit. |
| Replaced by an insight | duplicated-javascript |
Use duplicated-javascript-insight. |
| Removed without a replacement | first-meaningful-paint, font-size, no-document-write, offscreen-images, preload-fonts, third-party-facades, uses-passive-event-listeners, uses-rel-preload |
These audits no longer appear in the report or its JSON output. |
Google’s reasons for removing audits varied: some checks were no longer recommended, some were rarely actionable, and some could encourage changes that might hurt performance. The official explanation is in What’s new in Lighthouse 13.
What this means for Lighthouse JSON users
If a script, dashboard, or test suite reads Lighthouse JSON, update it to handle the new insight IDs and the absence of removed audit data. Custom configurations that refer to the old IDs may also need revision. This is a compatibility change for diagnostics, not evidence that Lighthouse’s performance scoring formula changed.
Rank #2
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
What is Agentic Browsing?
Agentic Browsing is an experimental Lighthouse category for deterministic checks of signals that can help software agents interact with a website. Google describes it as addressing the interaction stage: agents first need to discover websites, then understand and use them. The category is not a conventional page-speed test.
Documented checks include whether page elements have useful accessibility-tree properties such as names and roles, whether layout remains stable, whether an llms.txt file is present at the domain root, and whether WebMCP tools are registered. The category was added to Lighthouse’s default configuration in v13.3.0; it is distinct from the ARD audit added in v13.5.0.
Rank #3
How to interpret its results
Agentic Browsing does not produce a weighted score out of 100. Its guide reports a fraction of readiness checks passed, individual audit pass/fail results, and informational counts. Treat it as a set of experimental diagnostics rather than a settled ranking or a guarantee that an agent will succeed on a site.
Results can vary if JavaScript registers tools dynamically or if the accessibility tree or layout changes during capture. Testing the documented category requires Chrome 150 or later. WebMCP audits have an additional condition: registration for the WebMCP origin trial. See Google’s Agentic Browsing scoring guide and its developer toolkit announcement for details.
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
How to get Lighthouse and check which version you are using
Lighthouse is available through Chrome DevTools, npm as a module or command-line interface, and browser extensions for Chrome and Firefox. It also powers services such as PageSpeed Insights. The route you choose affects which Lighthouse version you are using.
- npm or automated CLI workflows: Check the installed package version in your project or environment; the version can be upgraded independently of Chrome’s embedded version.
- Chrome DevTools: The embedded Lighthouse version is tied to the Chrome release and rollout. A release note’s expected Chrome version is not proof that every user has received it.
- PageSpeed Insights: Google may roll out a Lighthouse release on a different schedule from DevTools. Do not assume its version matches your local installation.
Lighthouse 13 requires Node.js 22.19 or later, an important prerequisite for npm, CLI, and automation users. Google’s Lighthouse 13 announcement covers supported access routes and the version requirement.
What Lighthouse’s recent changes mean for developers
- For performance investigations, focus on the consolidated insight recommendations and the underlying performance metrics, rather than expecting the version 13 audit changes to alter the score.
- For JSON consumers and CI checks, review audit-ID dependencies and update tests for renamed insights and removed audits.
- For teams exploring agent compatibility, consider Agentic Browsing a separate, experimental diagnostic area, with Chrome and WebMCP requirements in mind.
- For release-sensitive comparisons, record both the Lighthouse version and where it ran—npm, DevTools/Chrome, or PageSpeed Insights—so differences between results are interpretable.
For teams running audits automatically, the Lighthouse CI release history is a relevant place to track compatibility with Lighthouse releases.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
