Page size checker online: measure your web page weight instantly

Find out exactly how heavy your web page is with the page size checker online at ToolHQ. Enter any URL and get a breakdown of total page weight across HTML, CSS, JavaScript, images, and fonts, so you know exactly which assets are slowing your site down.

A page size checker fetches a URL and measures the total number of bytes the browser must download to display the page. This includes every resource the page requests: the HTML document, all linked stylesheets, JavaScript files, images, web fonts, and any third-party embeds.

Heavy pages frustrate users and damage rankings. Google's Core Web Vitals framework measures real-world page speed, and large page weight is one of the primary reasons pages fail Largest Contentful Paint (LCP) and Interaction to Next Paint (INP) thresholds. Checking page weight is the fastest first step in any performance audit.

Key Takeaways

• Total page weight includes HTML, CSS, JS, images, fonts, and all third-party resources
• Google's recommended page size budget is under 500KB for fast loading; under 2MB is acceptable
• Images are the largest contributor to page weight on most websites
• Large pages directly correlate with poor Core Web Vitals scores and lower rankings
• Only the URL you enter is fetched, no personal data stored

---

What page size is and how the checker works

When a browser loads a web page, it does not just download a single file. It parses the HTML, then discovers and fetches every resource referenced by that page: CSS files for styling, JavaScript bundles for interactivity, image files for visuals, and font files for typography. The total of all these files, measured in kilobytes or megabytes, is the page weight.

According to the HTTP Archive State of the Web report, the median desktop page weight is approximately 2.2MB and the median mobile page weight is around 2.0MB. However, median performance is not a target to aim for: it is a warning sign. Pages that load fastest convert better and rank higher.

The web.dev page weight guidance from Google recommends keeping total page weight under 500KB for an optimal experience, particularly on mobile connections. Pages under 2MB are considered acceptable. Beyond 2MB, users on 3G or 4G connections experience visible delays, and Google's ranking systems penalise slow-loading pages through the Core Web Vitals signals.

ToolHQ's page size checker fetches the URL you enter and returns a full asset breakdown. Only the URL you enter is fetched, no personal data stored.

---

When you need a page size checker

Page weight auditing belongs in several workflows.

Pre-launch review: Before taking a new website live, run every key page through a size checker to catch uncompressed images, unminified JS bundles, and redundant third-party scripts that were added during development.

Performance regression detection: After a content or code update, compare page weight before and after. Even small additions (a new analytics script, an embedded widget) can balloon total weight significantly.

Diagnosing poor Core Web Vitals scores: If your Google Search Console shows failing LCP scores, page weight is one of the first things to investigate. Large, unoptimised hero images are responsible for LCP failures in the majority of cases.

Client reporting: A page size check provides concrete, easy-to-understand numbers that demonstrate performance problems to non-technical stakeholders.

Mini-story: A web developer was tasked with improving a landing page's conversion rate. She ran the URL through ToolHQ's page size checker and discovered the page was 4.8MB, nearly all of it a single uncompressed hero image at 3.9MB. After converting the image to WebP and serving it at the correct display size, total page weight dropped to 0.7MB. The page's LCP improved from 6.2 seconds to 1.4 seconds, and the conversion rate increased by 23% in the following month.

Audit your own page now at ToolHQ's page size checker.

---

How to use the page size checker step by step

1. Open the tool. Visit ToolHQ's page size checker.
2. Enter the URL. Paste the full URL of the page you want to measure, including the protocol (https://).
3. Run the check. Click "Check Page Size". The tool fetches the page and all its resources.
4. Review the total weight. Check the headline number against the targets below: under 500KB is excellent, under 2MB is acceptable.
5. Find the largest assets. Look at the breakdown by resource type. Images are almost always the biggest category. Identify the single largest file and start there for optimisation.

---

Page size targets and asset breakdown

Use this reference to evaluate your results and prioritise optimisation work.

Asset type	Typical share of page weight	Optimisation method
Images	50–70%	Compress to WebP/AVIF; serve at correct display size; use lazy loading
JavaScript	15–30%	Minify; remove unused libraries; code-split; defer non-critical scripts
CSS	5–15%	Minify; remove unused rules; inline critical CSS
HTML	2–5%	Minify; remove comments; enable server-side compression (gzip/Brotli)
Fonts	2–10%	Subset fonts; use WOFF2 format; limit font families
Third-party scripts	Variable	Audit each embed; remove unused trackers and widgets

Key benchmarks:

• Under 500KB total: Excellent. Page will load fast on most connections.
• 500KB to 1MB: Good. Minor optimisation opportunities exist.
• 1MB to 2MB: Acceptable but improvable. Check image sizes.
• 2MB to 4MB: Heavy. Users on slower connections will experience delays.
• Over 4MB: Critical. Immediate optimisation needed for performance and rankings.

Mini-story: An e-commerce manager noticed the product category pages were loading slowly on mobile. A page size check revealed the pages were 5.1MB, with 38 product images loading at full resolution rather than at thumbnail size. After implementing image resizing and lazy loading, page weight dropped to 1.1MB and mobile session duration increased by 18%.

---

Frequently asked questions

What is the ideal page size for SEO? Google does not publish a single number, but the general recommendation from web.dev is under 500KB for fast load and under 2MB to remain competitive. Pages over 2MB frequently fail Core Web Vitals thresholds, which are used as ranking signals.

Do third-party scripts count toward page size? Yes. Every resource the page requests, including Google Analytics, chat widgets, ad tags, social sharing buttons, and any embedded iframes, contributes to total page weight and load time.

What is the fastest way to reduce page size? Compressing and resizing images to the correct display size delivers the largest reduction for most websites, since images typically represent 50 to 70% of page weight. After images, removing unused JavaScript libraries and minifying CSS and JS provide the next biggest gains.

How does page size relate to Core Web Vitals? Page size affects all three Core Web Vitals. Large images delay Largest Contentful Paint (LCP). Heavy JavaScript delays interactivity, increasing Interaction to Next Paint (INP). Unoptimised resources that load asynchronously can cause layout shifts, hurting Cumulative Layout Shift (CLS).

Does compression count in the page size measurement? Most page size checkers report the compressed (transferred) size, which is what the browser actually downloads over the network. The uncompressed size (how much the browser uses in memory) is larger. Both are useful metrics; the transferred size is what determines network load time.

---

The short version

Page weight is the total size of every asset your browser must download to display a web page. The target is under 500KB for fast performance and under 2MB to remain in acceptable range for Google's Core Web Vitals. ToolHQ's page size checker fetches any URL and shows you the full breakdown by asset type, making it simple to identify the largest files and prioritise which to optimise first. Images are almost always the culprit. Start there.

Check your page size now at ToolHQ.

Related tools: HTTP headers checker | Website screenshot | SSL checker | Redirect checker