Our Test Agents are now using Chrome 156 and Lighthouse 13.6.0 to test your Sites.

Chrome 156 fixes CVE-2026-118320, a high severity memory corruption vulnerability in V8.

LCP, FCP and Performance Score changes#

Lighthouse 13.6.0 fixes how simulated throttling calculates Largest Contentful Paint and First Contentful Paint:

• Text LCP: when the LCP element is text painted at the same time as FCP, LCP now equals FCP. Previously, preloaded and other non-blocking requests could push LCP later. This was reported in June 2025.
• Render-blocking requests: Lighthouse now uses Chrome's own render-blocking data instead of guessing from request priority, so requests that don't block rendering, including module scripts, no longer count against FCP and LCP (#16869, #17163).

Expect LCP and FCP to mostly improve on PageSpeed Desktop and PageSpeed Mobile Test Profiles, lifting Performance Scores. Test Profiles using runtime throttling aren't affected by these fixes.

New: Agentic Browsing audits#

Snapshots now include Lighthouse's Agentic Browsing audits, which check how well AI agents can navigate and use your pages:

• Accessibility tree: whether it's well-formed.
• WebMCP: registered tools, form coverage and schema validity.
• llms.txt: whether your file follows community recommendations.
• ARD manifest: whether your Agentic Resource Discovery manifest is valid.

Google marks this category as under development, so expect the audits to change. Read more in the Lighthouse Audits documentation.