PageSpeed Remediation Backlog Builder
Pricing
from $10.50 / 1,000 remediation reports
Turn a PageSpeed Insights / Lighthouse audit batch into an evidence-linked remediation queue, one report per unique URL+strategy, with honest thresholds-crossed evidence and no invented ROI.
You can access the PageSpeed Remediation Backlog Builder programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in API & Integrations in Apify Console.
# Set API token$API_TOKEN=<YOUR_API_TOKEN>
# Prepare Actor input$cat > input.json << 'EOF'<{< "items": [< {< "input": "https://www.bbc.com/",< "sourceUrl": "https://www.googleapis.com/pagespeedonline/v5/runPagespeed",< "found": true,< "status": "ok",< "resultCount": 1,< "partial": false,< "error": "",< "warnings": [],< "checkedAt": "2026-09-23T05:03:23.591Z",< "schemaVersion": "1.0",< "url": "https://www.bbc.com/",< "strategy": "mobile",< "finalUrl": "https://www.bbc.com/",< "performanceScore": 0.56,< "LCP": 7170.740664599693,< "CLS": 0.11022084164631413,< "TBT": 315,< "FCP": 3021.000657027039,< "SI": 6007.5946841464975,< "metricSource": "lab",< "metricUnits": {< "LCP": "ms",< "CLS": "unitless",< "TBT": "ms",< "FCP": "ms",< "SI": "ms"< },< "fetchTime": "2026-09-23T05:03:03.710Z",< "lighthouseVersion": "13.5.0",< "topOpportunities": [< {< "id": "bootup-time",< "title": "Reduce JavaScript execution time",< "description": "Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to reduce Javascript execution time](https://developer.chrome.com/docs/lighthouse/performance/bootup-time/).",< "displayValue": "1.5 s",< "estimatedSavingsMs": 550,< "estimatedSavingsBytes": 0,< "metricSavings": {< "TBT": 550< }< },< {< "id": "unused-javascript",< "title": "Reduce unused JavaScript",< "description": "Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/).",< "displayValue": "Est savings of 494 KiB",< "estimatedSavingsMs": 450,< "estimatedSavingsBytes": 505401,< "metricSavings": {< "LCP": 450,< "FCP": 0< }< },< {< "id": "cache-insight",< "title": "Use efficient cache lifetimes",< "description": "A long cache lifetime can speed up repeat visits to your page. [Learn more about caching](https://developer.chrome.com/docs/performance/insights/cache).",< "displayValue": "Est savings of 664 KiB",< "estimatedSavingsMs": 450,< "estimatedSavingsBytes": 0,< "metricSavings": {< "LCP": 450,< "FCP": 0< }< },< {< "id": "mainthread-work-breakdown",< "title": "Minimize main-thread work",< "description": "Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to minimize main-thread work](https://developer.chrome.com/docs/lighthouse/performance/mainthread-work-breakdown/)",< "displayValue": "2.4 s",< "estimatedSavingsMs": 300,< "estimatedSavingsBytes": 0,< "metricSavings": {< "TBT": 300< }< },< {< "id": "font-display-insight",< "title": "Font display",< "description": "Consider setting [`font-display`](https://developer.chrome.com/docs/performance/insights/font-display) to `swap` or `optional` to ensure text is consistently visible. `swap` can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).",< "displayValue": "Est savings of 50 ms",< "estimatedSavingsMs": 50,< "estimatedSavingsBytes": 0,< "metricSavings": {< "FCP": 50,< "INP": 0< }< }< ],< "categoryScores": {< "performance": 0.56< }< }< ]<}<EOF
# Run the Actor using an HTTP API# See the full API reference at https://docs.apify.com/api/v2$curl "https://api.apify.com/v2/actors/zinin~pagespeed-remediation-backlog/runs?token=$API_TOKEN" \< -X POST \< -d @input.json \< -H 'Content-Type: application/json'Below, you can find a list of relevant HTTP API endpoints for calling the PageSpeed Remediation Backlog Builder Actor. For this, you’ll need an Apify account. Replace <YOUR_API_TOKEN> in the URLs with your Apify API token, which you can find under API & Integrations in Apify Console. For details, see the API reference.
https://api.apify.com/v2/actors/zinin~pagespeed-remediation-backlog/runs?token=<YOUR_API_TOKEN>Note: By adding the method=POST query parameter, this API endpoint can be called using a GET request and thus used in third-party webhooks. Please refer to our Run Actor API documentation.
https://api.apify.com/v2/actors/zinin~pagespeed-remediation-backlog/run-sync-get-dataset-items?token=<YOUR_API_TOKEN>Note: This endpoint supports both POST and GET request methods. However, only the POST method allows you to pass input data. For more information, please refer to our Run Actor synchronously and get dataset items API documentation.
https://api.apify.com/v2/actors/zinin~pagespeed-remediation-backlog?token=<YOUR_API_TOKEN>For more information, please refer to our Get Actor API documentation.
Actors can be used to scrape web pages, extract data, or automate browser tasks. Use the PageSpeed Remediation Backlog Builder API programmatically via the Apify API.
You can choose from:
You can start PageSpeed Remediation Backlog Builder with the Apify API by sending an HTTP POST request to the Run Actorendpoint. An Actor’s input and its content type can be passed as a payload of the POST request, and additional options can be specified using URL query parameters. The PageSpeed Remediation Backlog Builder is identified within the API by its ID, which is the creator’s username and the name of the Actor.
When the PageSpeed Remediation Backlog Builder run finishes you can list the data from its default dataset(storage) via the API or you can preview the data directly on Apify Console.