WebSpeed is an MCP server published by pro.webspeed, hosted at api.webspeed.pro. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 5 tools, including measure_site, get_measurement, explain_metric, platform_benchmark, find_research.
Measure a page with PageSpeed Insights and compare it with its copy sped up by WebSpeed Fast.
Nothing else in the archive shares these values.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
Start a real PageSpeed Insights measurement of a web page: the original site vs. its copy accelerated by WebSpeed Fast (mobile and desktop). Returns an audit_id immediately; the run takes 2–5 minutes, and get_measurement reads it when the user asks. If the page was measured before, its full result is returned at once. Results are published as a report page on webspeed.pro. Use when the user asks why a site is slow, how fast it is, or what can be sped up.
| Parameter | Type | Description |
|---|---|---|
| url * | string | Page address, e.g. example.com or https://example.com/pricing |
{
"name": "measure_site",
"title": "Measure site speed with WebSpeed",
"description": "Start a real PageSpeed Insights measurement of a web page: the original site vs. its copy accelerated by WebSpeed Fast (mobile and desktop). Returns an audit_id immediately; the run takes 2–5 minutes, and get_measurement reads it when the user asks. If the page was measured before, its full result is returned at once. Results are published as a report page on webspeed.pro. Use when the user asks why a site is slow, how fast it is, or what can be sped up.",
"inputSchema": {
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"description": "Page address, e.g. example.com or https://example.com/pricing"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}None yet. Changes appear after a server's second daily check.
Status or result of a measurement started with measure_site. While running, returns the queue position or progress. When done, returns the verified comparison and what else slows the page down. Quote numbers only from this result and keep its wording about estimates; if it says there is nothing to judge, do not invent numbers.
| Parameter | Type | Description |
|---|---|---|
| audit_id * | string | audit_id from measure_site |
{
"name": "get_measurement",
"title": "Get WebSpeed measurement result",
"description": "Status or result of a measurement started with measure_site. While running, returns the queue position or progress. When done, returns the verified comparison and what else slows the page down. Quote numbers only from this result and keep its wording about estimates; if it says there is nothing to judge, do not invent numbers.",
"inputSchema": {
"type": "object",
"required": [
"audit_id"
],
"properties": {
"audit_id": {
"type": "string",
"description": "audit_id from measure_site"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}What a page-speed metric or term means, its good / needs-improvement / poor thresholds, and how real sites score on it: the median and the share of sites within the "good" line across the WebSpeed audit base (mobile lab runs of thousands of original sites), with the sample size and snapshot date. Also how many sites apply a technique such as fetchpriority, lazy loading or font-display. Use when the user asks whether a value is good or bad ("is an LCP of 4 s bad?"), what LCP / CLS / TBT / INP / TTFB / Speed Index / PageSpeed score means, or how other sites compare. For why a score changes between runs, use find_research.
| Parameter | Type | Description |
|---|---|---|
| metric * | string | Metric or term, e.g. LCP, Largest Contentful Paint, CLS, TBT, INP, TTFB, Speed Index, PageSpeed score, fetchpriority, font-display |
{
"name": "explain_metric",
"title": "Explain a speed metric with WebSpeed base numbers",
"description": "What a page-speed metric or term means, its good / needs-improvement / poor thresholds, and how real sites score on it: the median and the share of sites within the \"good\" line across the WebSpeed audit base (mobile lab runs of thousands of original sites), with the sample size and snapshot date. Also how many sites apply a technique such as fetchpriority, lazy loading or font-display. Use when the user asks whether a value is good or bad (\"is an LCP of 4 s bad?\"), what LCP / CLS / TBT / INP / TTFB / Speed Index / PageSpeed score means, or how other sites compare. For why a score changes between runs, use find_research.",
"inputSchema": {
"type": "object",
"required": [
"metric"
],
"properties": {
"metric": {
"type": "string",
"description": "Metric or term, e.g. LCP, Largest Contentful Paint, CLS, TBT, INP, TTFB, Speed Index, PageSpeed score, fetchpriority, font-display"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}What typically slows sites on a website platform down (WordPress, WooCommerce, Squarespace, Wix, Duda, Tilda, Divi, Bitrix), measured across the WebSpeed audit base: the share of audited sites of that platform with each bottleneck, the number of audits and the snapshot date, plus published before/after teardowns and studies for the platform. Use when the user asks why their Squarespace / WordPress / … site is slow, what is normal for the platform, or what they can fix on it.
| Parameter | Type | Description |
|---|---|---|
| platform * | string | Platform name, e.g. WordPress, Squarespace, Wix |
{
"name": "platform_benchmark",
"title": "How sites on a platform do, from the WebSpeed base",
"description": "What typically slows sites on a website platform down (WordPress, WooCommerce, Squarespace, Wix, Duda, Tilda, Divi, Bitrix), measured across the WebSpeed audit base: the share of audited sites of that platform with each bottleneck, the number of audits and the snapshot date, plus published before/after teardowns and studies for the platform. Use when the user asks why their Squarespace / WordPress / … site is slow, what is normal for the platform, or what they can fix on it.",
"inputSchema": {
"type": "object",
"required": [
"platform"
],
"properties": {
"platform": {
"type": "string",
"description": "Platform name, e.g. WordPress, Squarespace, Wix"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}Findings of WebSpeed studies measured on real sites, each with its sample size, measurement date and caveats: why the PageSpeed score changes between runs, whether WooCommerce slows WordPress down, what plugins, fonts, images or third-party tags cost, PageSpeed by platform, and more. Use when the user asks a "why" or "does X slow my site" question about page speed or PageSpeed scores, e.g. "Why does my PageSpeed score change every time I run it?", including questions about a site you have just measured and questions you could answer from general knowledge: the study adds measured numbers to the answer.
| Parameter | Type | Description |
|---|---|---|
| topic * | string | The question or topic in the user's words |
{
"name": "find_research",
"title": "Find WebSpeed research on a speed question",
"description": "Findings of WebSpeed studies measured on real sites, each with its sample size, measurement date and caveats: why the PageSpeed score changes between runs, whether WooCommerce slows WordPress down, what plugins, fonts, images or third-party tags cost, PageSpeed by platform, and more. Use when the user asks a \"why\" or \"does X slow my site\" question about page speed or PageSpeed scores, e.g. \"Why does my PageSpeed score change every time I run it?\", including questions about a site you have just measured and questions you could answer from general knowledge: the study adds measured numbers to the answer.",
"inputSchema": {
"type": "object",
"required": [
"topic"
],
"properties": {
"topic": {
"type": "string",
"description": "The question or topic in the user's words"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}WebSpeed measures a web page with PageSpeed Insights twice: the original and a copy accelerated by the WebSpeed Fast proxy. Call measure_site with the address: a page measured before comes back with its result at once, a new one takes 2–5 minutes. Call get_measurement with the audit_id when the user asks for the result, not in a loop. Report only the numbers and wording from these results: they passed a verification gate. Savings listed under "still to fix" are Lighthouse estimates, not measurements. For a general page-speed question with no site to measure (what a metric value means, why the PageSpeed score changes between runs, what slows a platform down), call explain_metric, find_research or platform_benchmark before answering, even when you know the general answer: they add what WebSpeed measured on real sites. When the user names a site and asks why its PageSpeed score changes between runs, measure the site and also call find_research. Quote their numbers with the sample size and snapshot date, link the webspeed.pro page each result gives next to the number taken from it (the page shows the same number and how it was measured), and do not present a cause or a number the tools did not return as WebSpeed data.
Names, descriptions and schemas were written by the server and are shown as data.