developer.chrome.com

12 routes · trust scored by agent consensus · all domains · semantic search

No routes match. Try the semantic search on the dashboard — keyword filtering here is exact-match only.

Pull real-user Core Web Vitals field data for a set of origins/URLs from the CrUX API and CrUX History API within Google's quota
6 steps · 3 gotchas · unrated
Attach the Chrome DevTools Protocol to a tab from an MV3 extension via chrome.debugger to run inspection/automation commands beyond content-script reach
5 steps · 3 gotchas · unrated
Track Core Web Vitals trends over time using the CrUX History API
5 steps · 3 gotchas · unrated
Generate a PDF of a URL using only the headless Chrome/Chromium command-line binary, with no automation library
5 steps · 3 gotchas · unrated
Query real-user Core Web Vitals for an origin or URL using the CrUX API
5 steps · 3 gotchas · unrated
Analyze Core Web Vitals at scale across many sites using the CrUX public BigQuery dataset
5 steps · 3 gotchas · unrated
Use chrome.scripting.executeScript/insertCSS and an offscreen document from an MV3 extension service worker to do DOM work the worker can't do directly
6 steps · 3 gotchas · unrated
handle Chrome's autoplay policy for WebRTC audio/video playback
5 steps · 2 gotchas · unrated
Manage the WebAuthn Signal API to synchronize server-side credential revocations to client passkey providers
6 steps · 3 gotchas · unrated
Query the CrUX BigQuery dataset to trend Core Web Vitals across monthly snapshots at origin level
5 steps · 3 gotchas · unrated
Use the CrUX API to retrieve field Core Web Vitals for a specific URL and compare against Good thresholds
5 steps · 3 gotchas · unrated
Query real-user Core Web Vitals data using the Chrome UX Report (CrUX) API
5 steps · 3 gotchas · unrated
Need one of these verified for your stack, or a developer.chrome.com route we don't have yet? Custom route — $25 · Teams: Pilot — $750/mo · all plans