generated: '2026-08-13'
method: searched
source: https://developers.google.com/speed/docs/insights/v5/reference/pagespeedapi/runpagespeed
note: >-
  The PageSpeed Insights API has NO test/live key separation, no test mode, no fixture
  values and no simulated data — it analyses whatever public URL you point it at, so
  every call is a live call. What Google does publish is an interactive execution
  surface: an embedded "Try it!" APIs Explorer panel on the reference page, a standalone
  APIs Explorer entry for pagespeedonline v5, and the pagespeed.web.dev web UI which runs
  the same analysis without a key. Recorded here so the console surface is not confused
  with a sandbox.
test_mode:
  exists: false
  key_prefixes: null
  test_values: null
  time_simulation: null
  fixtures: null
consoles:
  - name: APIs Explorer — pagespeedonline v5
    url: https://developers.google.com/apis-explorer#p/pagespeedonline/v5/
    type: api-explorer
    auth: google-account (OAuth) or anonymous
    note: Executes real requests against the production API.
  - name: Try it! panel on the runPagespeed reference page
    url: https://developers.google.com/speed/docs/insights/v5/reference/pagespeedapi/runpagespeed
    type: embedded-explorer
    note: Same explorer embedded inline in the method reference.
  - name: PageSpeed Insights web UI
    url: https://pagespeed.web.dev/
    type: hosted-ui
    auth: none
    note: >-
      Keyless human-facing surface running the same Lighthouse analysis. Useful for
      eyeballing an expected result before wiring the API, but it is not an API sandbox.
safe_test_targets:
  note: >-
    Google's own documentation example uses https://web.dev/ as the analysed URL. No
    "magic" test URL exists; there is nothing to fabricate here.
  documented_example: https://web.dev/
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com