Page Weight Analyzer - Page Size & Performance Hints

Page Weight Analyzer — page size, resource counts & performance hints

Estimate a page's weight and get actionable performance hints from a single fetch — no headless browser. Returns HTML size, transfer (compressed) size, counts of scripts/styles/images/ fonts, render-blocking resources, and specific fixes. Single URL or bulk. $0.001 per page. Failed fetches are recorded free.

What you get

• HTML + transfer size (KB), with detected compression.
• Resource counts: external/inline scripts, external/inline styles, images, fonts.
• Render-blocking scripts + stylesheets in <head>, and scripts missing async/defer.
• Inline JS/CSS weight and an estimated request count.
• Hints — concrete, prioritized fixes.
• Fail-soft: an unreachable URL returns {ok:false, error} and is never charged.

Input

{ "url": "https://github.com", "urls": ["https://example.com"], "maxUrls": 25 }

Output (real run, 2026-08-07)

{
  "ok": true, "url": "https://github.com/", "status": 200,
  "htmlKb": 559.37, "transferKb": 559.37, "compression": "gzip",
  "counts": { "scripts": 15, "styles": 42, "images": 24, "fonts": 1 },
  "inlineJsKb": 132.57, "renderBlocking": 30, "renderBlockingStyles": 30,
  "estimatedRequests": 76,
  "hints": ["30 render-blocking stylesheet(s) in <head> — inline critical CSS and lazy-load the rest.", "…"]
}

Example

A real run on 2026-10-31 with the input this page's form is prefilled with:

{
  "url": "https://github.com",
  "urls": [
    "https://github.com",
    "https://wikipedia.org"
  ]
}

It finished in 2 seconds and returned 2 results. It was charged for 2 page-scanned events ($0.002 on the Free plan). The first result (long text and lists cut for display):

{
  "ok": true,
  "url": "https://github.com/",
  "finalUrl": "https://github.com/",
  "status": 200,
  "contentType": "text/html",
  "htmlKb": 517.71,
  "transferKb": 517.71,
  "compression": "gzip",
  "counts": {
    "scripts": 16,
    "scriptsExternal": 8,
    "scriptsInline": 8,
    "styles": 43,
    "stylesExternal": 42,
    "stylesInline": 1,
    "images": 22,
    "fonts": 1
  },
  "inlineJsKb": 142.33,
  "inlineCssKb": 0.12,
  "renderBlocking": 29,
  "renderBlockingScripts": 0,
  "renderBlockingStyles": 29,
  "scriptsMissingAsyncDefer": 0,
  "estimatedRequests": 74,
  "hints": [
    "29 render-blocking stylesheet(s) in <head> — inline critical CSS and lazy-load the rest.",
    "Large inline JavaScript (142.33KB) — extract to a cacheable external file.",
    "HTML document is large (517.71KB) — minify markup and reduce server-rendered bloat.",
    "… 2 more"
  ],
  "fetchMs": 79,
  "scrapedAt": "2026-10-31T23:40:51.949Z"
}

Pricing — $0.001 per page

A lightweight HTML-only analyzer, priced far below the Lighthouse-style actors on the Apify Store (measured 2026-08-07: nexgendata/page-speed-analyzer $0.1/item · miccho27/seo-analyzer $0.03/item · alizarin pagespeed-insights $0.02/url-analysis). Those render the page in a headless browser; this one parses the served HTML, so it is ~20–100× cheaper for a fast weight + hints pass.

Limits (honest ones)

• Analyzes the served HTML — it does not download each sub-resource or run JavaScript, so sizes for external JS/CSS/images are counted, not summed. Use a headless Lighthouse actor for fully-rendered metrics.
• Transfer size uses the server's Content-Length, or a gzip estimate when absent.
• maxUrls capped at 50 per run.

FAQ

• Does it run Lighthouse? No — it is a fast HTML-only pass (counts, sizes, render-blocking, hints). That is what makes it cheap.
• Does it measure external file sizes? It counts external resources and measures inline JS/CSS; it does not fetch each external file.
• What about a dead URL? You get an {ok:false, error} record, uncharged.

Use from code or AI agents

curl -X POST "https://api.apify.com/v2/acts/EliAI~webpage-page-weight-analyzer/runs?token=YOUR_APIFY_TOKEN" \
  -H 'content-type: application/json' -d '{"url":"https://github.com"}'

Callable as an agent tool through the Apify MCP server (mcp.apify.com).

Who uses it

• Performance engineers finding pages with many render-blocking scripts
• SEO agencies flagging heavy templates across a client's key URLs
• Developers comparing HTML and transfer size before and after a build change
• Sustainability teams estimating page weight across a site
• Consultants benchmarking resource counts on competitor homepages

Changelog

• 2026-11-01: Page text only: an Example section from a real run. Code, output and price are unchanged.