Web Data

Page weight and resource API

Find out what makes a page heavy. Load it in a real browser and get total bytes, requests by type, the largest files, third-party weight, render-blocking resources and load timings, with findings for common problems.

View documentation Try the free tool Explore all APIs

Endpoints Active

GET /v1/page-weight

Example request

curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/page-weight?url=example.com"

Example response 200 OK

{
  "status": "ok",
  "summary": { "requests": 86, "total_bytes": 3412887, "third_party_bytes": 1210554 },
  "by_type": [
    { "type": "image", "requests": 31, "bytes": 1840221 },
    { "type": "script", "requests": 28, "bytes": 1120334 }
  ],
  "timing": { "ttfb_ms": 180, "first_contentful_paint_ms": 1240, "load_ms": 3890 },
  "findings": ["page_weight_ove
...

Example request GET /v1/page-weight

Key Features 4

Frequently asked questions 4

HTTP status codes 200 / 400 / 401 / 402 / 429

Category Web Data

Endpoints 1

Key Features 4

Frequently asked questions 4

Used by people at these companies

Trust signals before you integrate

Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.

Live Service status

Check live service health and documented failure responses before you integrate.

OpenAPI API artifacts

OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.

API keys Protected access

Authenticated endpoints use API keys with clear credit costs before you call them.

10,000 Free allowance

Start with 10,000 monthly credits and upgrade only when usage grows.

What this API helps you ship

Use this page as a production brief: endpoints, examples, response shape, and the workflow pieces needed to plug DomScan into your own product.

Product workflows

Embed domain checks, DNS intelligence, risk signals, or enrichment into onboarding, search, and internal tools.

Analyst automation

Replace repeated manual lookups with scheduled jobs, alerting, and reproducible investigation steps.

Clean JSON data

Use predictable fields, documented status codes, and credit costs instead of scraping provider pages.

AI and ops tooling

Feed agents, dashboards, SOAR playbooks, and CRMs through OpenAPI, SDK, Postman, or MCP.

Integration workflow

A simple path from first request to repeatable production usage.

Authenticate once

Send your API key with the documented header and keep requests consistent across services.

Query with examples

Start from the curl and HTTP samples, then map the parameters into your application code.

Operate and monitor

Use status codes, credit costs, and response fields to build retries, logs, and alerts.

Developer kit

Jump from this page into machine-readable docs, request collections, SDKs, or agent tooling.

OpenAPI schema

Generate clients or inspect every request and response shape.

Postman collection

Import ready-made requests for manual testing and team handoff.

SDKs and CLI

Use maintained packages and command-line workflows instead of writing boilerplate.

MCP integration

Expose domain intelligence to AI agents and internal assistant workflows.

Parameters and response map

Scan the inputs, output fields, and status codes before wiring the endpoint into your client.

Request parameters

Parameter

url

Response fields

Example response

statussummarysummary.requestssummary.total_bytessummary.third_party_bytesby_typetimingtiming.ttfb_mstiming.first_contentful_paint_mstiming.load_msfindings

Status coverage

HTTP status codes

200400401402429

Endpoints

GET /v1/page-weight

Credits: 6Authentication: Authentication required

Trust signals before you integrate

Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.

Service status API artifacts

OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.

API keys Protected access

Authenticated endpoints use API keys with clear credit costs before you call them.

Free allowance Sign up for free

Start with 10,000 monthly credits and upgrade only when usage grows.

Active Example request

Start from the curl and HTTP samples, then map the parameters into your application code.

Key Features

Bytes by type

Requests and bytes for documents, scripts, stylesheets, images, fonts and data requests.

Largest resources

The ten heaviest files with their type and size, so you know what to compress first.

Third-party weight

Bytes and requests per third-party domain, and the share of the page they add.

Render blocking and timings

Stylesheets and synchronous scripts that block the first render, plus time to first byte, first contentful paint and load time.

Example request

GET /v1/page-weight?url=example.com bash

curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/page-weight?url=example.com"

Example response

200 OK json

{
  "status": "ok",
  "summary": { "requests": 86, "total_bytes": 3412887, "third_party_bytes": 1210554 },
  "by_type": [
    { "type": "image", "requests": 31, "bytes": 1840221 },
    { "type": "script", "requests": 28, "bytes": 1120334 }
  ],
  "timing": { "ttfb_ms": 180, "first_contentful_paint_ms": 1240, "load_ms": 3890 },
  "findings": ["page_weight_over_3mb", "images_over_200kb", "render_blocking_resources"]
}

Frequently asked questions

Is this the same as a Lighthouse score?

No. It measures what the page downloads in one load. Use it together with lab and field speed data to plan fixes.

Why is a page measurement truncated?

Loads stop after 8 MB, 200 requests or 20 seconds. The finding measurement_truncated tells you the page is heavier than measured.

Which findings are reported?

Pages over 3 MB, over 100 requests, images over 200 KB, render-blocking resources and third parties over half of the bytes.

How many credits does it cost?

Six credits per page. Blocked or failed pages are refunded.

Related tools and resources

HTTP status codes

These are the HTTP status codes to handle, so you can tell apart successful responses, auth issues, credits, rate limits, missing data, and upstream failures.

OK 200

Request successful

Bad Request 400

Invalid parameters

Unauthorized 401

Missing or invalid API key/session.

Payment Required 402

Not enough credits to run this request.

Too Many Requests 429

Rate limit exceeded

Measure page weight

Start free View documentation Try the free tool