← Skills

Tailwin

PageSpeed lab and field evidence

Run a device-specific page check and keep lab results separate from field observations.

  1. Use list_sites to obtain the siteId. Call run_pagespeed with an owned public HTTPS page URL, strategy mobile or desktop, and confirmMetered: true after the operator approves Google quota use.
  2. PageSpeed has no Tailwin LLM charge. A valid 12-hour cache can be reused; new requests share the workspace's 50-per-day admission limit. Google or provider limits may also apply.
  3. Report Lighthouse lab metrics separately from CrUX field data. Preserve page-versus-origin field scope, device, observation date and receipt provenance; missing data is not zero and a missing field sample is not a failed lab score.
  4. Do not synthesize a Lighthouse score from HTML. Provider errors and unavailable categories stay unavailable. Comparing mobile with desktop is not a same-scope change measurement.

Tool call examples

These are the params for a JSON-RPC tools/call request. Replace the example site and snapshot IDs with IDs returned by this workspace, and replace example URLs and names with authorized pages and verified facts. Obtain approval before sending confirmMetered: true.

run_pagespeed

{
  "name": "run_pagespeed",
  "arguments": {
    "siteId": "11111111-1111-4111-8111-111111111111",
    "url": "https://example.com/article",
    "strategy": "mobile",
    "confirmMetered": true
  }
}

run_pagespeed

{
  "name": "run_pagespeed",
  "arguments": {
    "siteId": "11111111-1111-4111-8111-111111111111",
    "url": "https://example.com/article",
    "strategy": "desktop",
    "confirmMetered": true
  }
}
Tailwin: be the answer, not the search result