---
title: "Page Size Checker - Test Page Weight & Resource Breakdown Free · Unlighthouse"
canonical_url: "https://unlighthouse.dev/tools/page-size"
last_updated: "2026-06-30T08:48:13.401Z"
meta:
  description: "Free page size checker. Analyze total page weight, resource breakdown by type, third-party script weight, unused code, and compression efficiency. Compare against HTTP Archive percentiles."
  "og:description": "Free page size checker. Analyze total page weight, resource breakdown by type, third-party script weight, unused code, and compression efficiency. Compare against HTTP Archive percentiles."
  "og:title": "Page Size Checker - Test Page Weight & Resource Breakdown Free · Unlighthouse"
---

</h1>

```

Unlighthouse on GitHub

# **Page Size **Checker

Analyze page weight, resource breakdown, third-party scripts, and unused code with real Lighthouse data.

**Page Size Analysis**

Enter a URL to check page size

## **Why Page Weight Matters **

Page weight directly impacts **Largest Contentful Paint (LCP)** and **Time to Interactive**. The median mobile page now weighs 2.5 MB, growing ~10% per year. But median doesn't mean good — sites in the **bottom 25th percentile** (under 1 MB) consistently score higher on Core Web Vitals.

JavaScript is the most expensive resource type: every 50 KB of JS costs ~100ms of parse/compile time on mid-range phones. Images are cheaper byte-for-byte since they don't block the main thread, but unoptimized images are the largest contributor to total page weight.

### **Page Weight Benchmarks (Mobile) **

**P10**

489.0 KB

**P25**

1.0 MB

**P50**

2.5 MB

**P75**

5.0 MB

**P90**

8.1 MB

Source: HTTP Archive, 2025-2026 mobile data

## **How to Reduce Page Weight **

### **Optimize Images **

Use AVIF (50% savings over JPEG) or WebP (30% savings). Serve responsive sizes with srcset. Lazy-load below-fold images.

### **Trim JavaScript **

Tree-shake unused code. Code-split routes. Audit npm dependencies — many bundles ship 30-50% unused code.

### **Enable Brotli **

Brotli compresses 15-25% better than gzip for text resources. Most CDNs and reverse proxies support it out of the box.

### **Audit Third Parties **

Third-party scripts average 30-50% of total page weight. Remove unused trackers, defer non-essential scripts, and use lightweight alternatives.

### **Variable Fonts **

Replace multiple font files with a single variable font. Subset to only the characters you need. Use WOFF2 format.

### **Set Budgets **

Set a performance budget (e.g., 200 KB JS, 500 KB images). Use Lighthouse CI to enforce budgets in your CI pipeline.

**Was this tool helpful? **

Your feedback helps us improve

## **Frequently Asked Questions **

<details>

<summary>**01**### **What is a good page size?**

</summary>

Under 1 MB total transfer size is excellent. 1-2 MB is acceptable for content-rich pages. 2-3 MB is heavy and will impact mobile users. Over 3 MB is considered poor — the median web page is around 2.5 MB on mobile, but that doesn't mean it's good. Aim to be in the bottom 25th percentile.

</details>

<details>

<summary>**02**### **How does page size affect performance?**

</summary>

Larger pages take longer to download (hurting LCP) and require more CPU to parse JavaScript (hurting TBT and INP). 50% of mobile sites take over 14s to become interactive, with a median mobile Total Blocking Time (TBT) of 1,916ms. Every 100 KB of JavaScript costs roughly 100ms of parse time on mid-range phones. Images are less CPU-expensive than JavaScript byte-for-byte.

</details>

<details>

<summary>**03**### **What is the average web page size in 2026?**

</summary>

According to HTTP Archive data, the median mobile page weighs about 2,559 KB (~2.5 MB), growing roughly 10% year-over-year. Desktop median is about 2,862 KB. At the 90th percentile, pages exceed 8 MB. JavaScript and images are the two largest contributors.

</details>

<details>

<summary>**04**### **Does page size affect SEO?**

</summary>

Indirectly, yes. Page size impacts Core Web Vitals (LCP, INP, CLS). While only 48% of mobile sites pass all CWVs and speed has a weak direct correlation to organic rank, a 1-second delay can lead to a 7% drop in conversions. Very large pages also affect crawl budget and have a larger carbon footprint — a median 2.5MB page correlates linearly with higher energy use in data transfer.

</details>

<details>

<summary>**05**### **What is the difference between transfer size and uncompressed size?**

</summary>

Transfer size is the actual bytes sent over the network after gzip or brotli compression. Uncompressed size is the raw content before compression. Text-based resources (HTML, CSS, JS, JSON) typically compress 3-5x. Images are already compressed so transfer and uncompressed sizes are similar.

</details>

<details>

<summary>**06**### **How do I reduce my page size?**

</summary>

Compress images with AVIF/WebP (30-50% savings over JPEG). Tree-shake and code-split JavaScript. Remove unused CSS. Enable brotli compression on your server. Lazy-load images below the fold. Audit third-party scripts — they often account for 30-50% of total page weight.

</details>

Explore more performance tools

[**Full PSI Report **](https://unlighthouse.dev/tools/pagespeed-insights-performance) [** LCP Finder **](https://unlighthouse.dev/tools/lcp-finder) [** HAR Viewer **](https://unlighthouse.dev/tools/har-viewer) [** JSON Size **](https://unlighthouse.dev/tools/json-size)