Page Weight Audit avatar

Page Weight Audit

Pricing

$250.00 / 1,000 completed audits

Go to Apify Store
Page Weight Audit

Page Weight Audit

A performance read without a headless browser: parse the HTML, measure every script, stylesheet, and image by transfer size, total the page weight, and flag render-blocking resources, uncompressed assets, and oversized images. Charged only on completed audits.

Pricing

$250.00 / 1,000 completed audits

Rating

0.0

(0)

Developer

Chris Arsenault

Chris Arsenault

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

5 days ago

Last modified

Share

How heavy is this page, and what is making it heavy — without spinning up a headless browser. It parses the HTML, finds every script, stylesheet, and image, measures each one's transfer size, totals the page weight, and flags the usual culprits: render-blocking resources in the head, uncompressed JavaScript and CSS, and oversized images.

What you get

Summary plus one row per resource:

{
"url": "https://example.com",
"total_transfer_mb": 2.8,
"html_compressed": true,
"script_count": 24, "script_bytes": 1180000,
"image_count": 18, "image_bytes": 1420000,
"render_blocking_count": 6,
"fixes": [
"Page transfers about 2.8 MB (measured); most pages should target under 2 MB.",
"6 render-blocking resources in <head>; defer scripts and inline critical CSS."
]
}
{ "kind": "image", "url": "https://.../hero.png", "bytes": 840000, "encoding": "none", "render_blocking": false }

Why "without a headless browser" matters

Most performance tools boot Chrome, which is slow, expensive, and overkill when the question is "what does this page ship and how big is it." This runs in a second on plain HTTP, which makes it cheap enough to schedule across a whole site.

Use cases

  • Performance budgets: schedule it on key templates; alert when total weight or render-blocking count creeps up.
  • Agencies: a concrete, byte-level weight breakdown for site audits, no Lighthouse setup.
  • Agents optimizing sites: pipe the resource rows into a compression or lazy-loading workflow.

Honesty notes

  • Weight is measured from real transfer sizes (Content-Length / ranged requests), capped at 60 resources per page for politeness; the summary reports anything unmeasured or truncated.
  • This measures what the page ships (its resource payload); it is not a Core Web Vitals field-data or rendering-timeline tool, and the listing will not pretend otherwise.
  • Unreachable pages report cleanly and you are not charged; billing is per completed audit.

Built by 1450 Enterprises.