Page Weight & Request Count Checker Tool Online

Last updated: Jul 12, 2026

Estimate known transfer weight from returned HTML and a bounded resource sample. See missing sizes and scan coverage before confirming the result in a browser network report.

Enter a URL to check page weight:

How the Page Weight Checker Works

The tool fetches the initial HTML, extracts common resource URLs, and estimates transfer size by resource type.

Safe URL validation, the page host and each resource host are checked before requests are made.
HTML parsing, the API finds images, srcset candidates, scripts, stylesheets, inline style URLs, videos, and sources.
Resource sizing, each unique resource is checked with HEAD or a small ranged GET when needed.
Breakdown report, results are grouped into HTML, CSS, JavaScript, images, fonts, and other assets.

Why Page Weight Matters

Heavy pages slow down users, crawlers, AI answer engines, and conversion paths.

LCP impact, oversized hero images and fonts can delay the largest visible content.
INP impact, large JavaScript bundles keep the main thread busy and make pages feel sluggish.
Crawl efficiency, lean pages are easier for search and AI systems to retrieve and process.
Mobile conversion, smaller pages perform better on slower networks and older devices.

Page Weight Thresholds

Total weight	Verdict	Action
Under 1 MB	Strong	Keep monitoring images, scripts, and fonts.
1 to 2 MB	Acceptable	Optimize top images and remove unused JavaScript.
Over 2 MB	Heavy	Audit images, third-party scripts, CSS, and font loading.

Start with images by using our image compressor, then compare improvements with the Core Web Vitals Checker and run a full server-side audit with the Website Performance Checker. Our Core Web Vitals guide explains how page weight feeds into LCP, INP, and CLS.

Page weight budget by resource type

A single total can hide the real problem, so set a budget per resource type. These are practical starting targets for a fast marketing or content page. Heavier pages can still convert, but each category above its budget is worth a closer look.

Resource	Suggested budget	Tip
Total page	Under 1 to 2 MB	Aim under 1 MB for marketing pages and treat 2 MB as the upper limit before it hurts mobile load.
Images	Roughly 500 KB to 1 MB	Use WebP or AVIF, size to display dimensions, and lazy-load below the fold.
JavaScript	Under about 300 KB compressed	Audit third-party tags and unused bundles. Heavy JS is the top cause of poor INP.
CSS	Under about 100 KB	Remove unused rules and inline only the critical above-the-fold styles.
Fonts	Around 100 KB or less	Self-host, subset to needed characters, and limit to two or three weights with font-display: swap.

Want help hitting these budgets across a whole site? See our website speed and performance optimization service or request a free website audit.

Next steps

Page Weight Checker related tools and articles

Continue with the closest follow-up checks and guides based on this tool's topic, crawl intent, and optimization workflow.

Image Compressor

Performance Checker

Core Web Vitals Checker

Core Web Vitals: What They Are and How to Fix Them

Website Speed Optimization Pricing: How Much It Costs in 2026?

Image SEO: Alt Text, File Names, Compression, and More

Page Weight Checker: FAQ

What does Total known weight include?

It adds the UTF-8 size of the fetched HTML to resource sizes that could be determined from headers. Resources are deduplicated by resolved URL and grouped as CSS, JavaScript, images, fonts, or other.

How are resource sizes determined?

For each public resource the endpoint tries HEAD first. If HEAD returns a response that is not successful or lacks Content-Length, it tries a GET with Range: bytes=0-0 and reads Content-Range or Content-Length. A network error or timeout ends that resource check without the GET retry.

What does Unknown sizes mean?

It counts resources whose total size could not be derived, including blocked, failed, timed-out, chunked, or header-poor responses. Unknown bytes are excluded from Total known weight, so that total can be an underestimate.

Which resources are discovered?

The static HTML scan finds common img, script, stylesheet link, video, and source URLs, srcset candidates, and url() references. It checks at most 40 unique resources within a 35-second overall budget and includes the HTML request in the displayed count.

Which page-weight resources can the checker miss?

It does not render JavaScript, scroll, interact, parse downloaded CSS imports, or observe browser caching and content negotiation. Runtime chunks, lazy assets, third-party calls, preloads, API responses, and resources after the 40-item cap may be absent.

How should I interpret Strong, Acceptable, and Heavy?

The labels use simple known-byte thresholds: under 1 MB, under 2 MB, or 2 MB and above. They are prioritization hints, not Core Web Vitals or user-experience grades, and unknown sizes can make the label optimistic.

What should I optimize first?

Start with the largest known category and high-impact above-the-fold resources, but verify in a browser waterfall. Resize and encode images appropriately, remove unused code, split or defer noncritical work, and preserve caching and compression.

What data is sent during the check?

The submitted URL is sent to Web Aloha's server, which fetches the public HTML and requests size headers for discovered resources. The endpoint does not include application logic that stores bodies or the report, though hosting logs may record requests.

Free 48-Hour Website Audit

Not sure what to fix first on your own website? We'll review it and tell you, in plain English. Free & non-obligatory.

Get My Free Audit 💪

Need to Reduce Page Weight?

We optimize images, JavaScript, fonts, CSS, and content delivery for fast business websites.

Explore Speed Optimization 🚀