pagespeed_field_metrics
Pack: pagespeed-insights · Endpoint: https://gateway.pipeworx.io/pagespeed-insights/mcp
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/pagespeed_field_metrics for the schema, then POST the same URL with its arguments for the data.
Real-user Core Web Vitals for a page AND for its whole origin in one call, from Google’s Chrome UX Report as PageSpeed Insights serves it — 75th-percentile Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift and Time to First Byte, with the good/needs-improvement/poor split behind each and Google’s own pass/fail verdict. AUTHORITATIVE for whether a page passes Core Web Vitals, and it says plainly when a low-traffic page has no data of its own and Google substituted the origin’s — a substitution that otherwise reads as page data and misattributes the whole site’s performance to one URL.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
url | string | yes | Full page URL, including the scheme, e.g. https://www.example.com/pricing. |
strategy | string | no | Device class for the field data: mobile (the default) or desktop. |
Example call
Arguments
{
"url": "https://www.wikipedia.org"
}
curl
curl -X POST https://gateway.pipeworx.io/pagespeed-insights/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"pagespeed_field_metrics","arguments":{"url":"https://www.wikipedia.org"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('pagespeed_field_metrics', {
"url": "https://www.wikipedia.org"
});
More examples
{
"url": "https://www.shopify.com/pricing",
"strategy": "desktop"
}
Connect
Add this to your MCP client config, or use one-click install buttons:
{
"mcpServers": {
"pagespeed-insights": {
"url": "https://gateway.pipeworx.io/pagespeed-insights/mcp"
}
}
}
See Getting Started for client-specific install steps.