Core Web Vitals over 25 weeks
https://seolyticize.com /api/v1/tools/get_vitals_history Core Web Vitals as Chrome measured them, week by week for the last 25 weeks, from the Chrome UX Report History API: p75 LCP, INP, CLS, TTFB and FCP (good at 1.8 s or less, poor over 3 s) for the client's origin, or one URL (url) when it has enough traffic, by form factor (phone, desktop or all). Regressions name a metric that got worse by more than 10% over the last four weeks or crossed into a worse rating; trends compare the first four weeks with the last four (within ±5% is stable). lcpBreakdown splits the newest image LCP into Chrome's four subparts (time to first byte, resource load delay, load duration, render delay) and names any at 40% of p75 LCP or more, with what to fix. Also the audits' Lighthouse runs per template, for the lab side. Without a Chrome UX Report key it says so and shows what is stored; nothing is estimated. Answers 'did our Core Web Vitals get worse', 'when did LCP regress' and 'are we passing on mobile'. Free.
Parameters
Idempotency-KeystringheaderRequest body
application/json
clientIdstringrequiredurlstringformFactorstring{
"clientId": "string",
"url": null,
"formFactor": "phone"
}Code samples
cURL
curl -X POST "https://seolyticize.com/api/v1/tools/get_vitals_history" \
-H "Authorization: Bearer $SEOLYTICIZE_API_KEY" \
-H "Idempotency-Key: <value>" \
-H "Content-Type: application/json" \
-d '{"clientId":"string","url":null,"formFactor":"phone"}'TypeScript
Python
Go
PHP
Ruby
Java
Responses
data, and its meta.Example
{
"data": {},
"meta": {
"requestId": "string",
"costMicros": 0,
"cached": true,
"cachedFrom": "string",
"dataAsOf": "string",
"sources": [
"string"
],
"partial": true,
"next": [
{
"tool": "string",
"args": {},
"why": "string"
}
],
"nextCursor": "string",
"dryRun": true
}
}Schema
datarequiredmetaobjectrequiredShow child parameters
requestIdstringrequiredcostMicrosintegerrequiredcachedbooleanrequiredcachedFromstringdataAsOfstringsourcesstring[]partialbooleanrequirednextobject[]requiredShow child parameters
toolstringargsobjectwhystringnextCursorstringdryRunbooleanX-RateLimit-LimitintegerX-RateLimit-RemainingintegerX-RateLimit-ResetintegerX-Request-IdstringExample
{
"error": "string",
"code": "string",
"next": "string",
"requestId": "string"
}Schema
errorstringrequiredcodestringnextstringrequestIdstringX-RateLimit-LimitintegerX-RateLimit-RemainingintegerX-RateLimit-ResetintegerSame as 400 · POST /api/v1/tools/get_vitals_history
WWW-AuthenticatestringSame as 400 · POST /api/v1/tools/get_vitals_history
X-RateLimit-LimitintegerX-RateLimit-RemainingintegerX-RateLimit-ResetintegerSame as 400 · POST /api/v1/tools/get_vitals_history
X-RateLimit-LimitintegerX-RateLimit-RemainingintegerX-RateLimit-ResetintegerSame as 400 · POST /api/v1/tools/get_vitals_history
X-RateLimit-LimitintegerX-RateLimit-RemainingintegerX-RateLimit-ResetintegerSame as 400 · POST /api/v1/tools/get_vitals_history
X-RateLimit-LimitintegerX-RateLimit-RemainingintegerX-RateLimit-ResetintegerSame as 400 · POST /api/v1/tools/get_vitals_history
X-RateLimit-LimitintegerX-RateLimit-RemainingintegerX-RateLimit-ResetintegerRetry-AfterintegerSame as 400 · POST /api/v1/tools/get_vitals_history
X-RateLimit-LimitintegerX-RateLimit-RemainingintegerX-RateLimit-Resetinteger