Free technical SEO performance preview

Page Size Checker for page-weight clarity

Measure total page weight, asset breakdown, requests and compression status. Enter one public page URL to understand which resources make a page heavy before deeper speed diagnostics.

Page weight

Transferred and uncompressed size

Asset map

HTML, CSS, JS, images, fonts

Compression

gzip, Brotli, missing or unknown

Page Size Checker

Measure total page weight, asset breakdown, requests, and compression status.

Public settings

Choose how the public checker should discover and measure page resources.

Free public checks are limited to 3 uses/day. CAPTCHA may appear for rendered analysis.

Total page sizeRequest countHTML sizeCSS weightJavaScript sizeImage weightFont sizeThird-party weightCompression statusResource waterfallTransferred sizeUncompressed sizeTotal page sizeRequest countHTML sizeCSS weightJavaScript sizeImage weightFont sizeThird-party weightCompression statusResource waterfallTransferred sizeUncompressed size
What you can check

Find the assets that make a page heavy

Use Wranker’s Page Size Checker as a lightweight page-weight diagnostic before running deeper performance and Core Web Vitals checks.

Use it during internal linking audits, content optimisation, technical SEO reviews, website migrations and content hub planning.

Weight summary

Measure total page size

Review total transferred size and uncompressed size where available, so heavy pages can be identified quickly.

Asset distribution

Break down resource categories

Separate HTML, CSS, JavaScript, images, fonts, other resources and third-party weight to see what contributes most.

Compression QA

Check gzip and Brotli coverage

Spot text-based resources where compression is good, partial, missing or unknown before deeper performance work.

Largest resources

Preview the heaviest files

Use the public waterfall preview to focus on large files, first-party assets, third-party resources and uncompressed text assets.

Why it matters

Page weight is the first signal before

A page can feel slow for many reasons, but heavy images, JavaScript, CSS, fonts, third-party scripts and uncompressed text assets are common places to start. This checker helps you decide what to optimise first without turning the landing page into a full performance report.

Prioritise the right fixes

See whether images, JavaScript, CSS, fonts, compression or third-party assets deserve attention first.

Start audits with clearer context

Use page-weight diagnostics before running Page Speed Insight Checker or Core Web Vitals Checker.

Create practical next steps

Turn basic size signals into rule-based actions like resizing images, reducing bundles, limiting fonts and reviewing scripts.

How it works

Run a public size check in

Keep the landing-page workflow simple: enter the URL, configure public settings, run the tool and review results in the output view.

01

Enter a page URL

Add one public HTTP or HTTPS URL. Plain domains are normalised to HTTPS after submit.

02

Choose analysis mode

Use Fast fetch for quick checks or Rendered preview for fuller browser-style discovery where available.

03

Set public options

Include third-party resources, measure compression, choose result depth and keep waterfall rows enabled.

04

Run the size check

Open the dashboard-style output to review total size, requests, categories, compression and resource rows.

When to use it

Useful for audits, QA and

Use Page Size Checker when you need a quick public view of page weight before deciding whether image, code, compression or third-party work is needed.

Technical SEO audits

Quickly answer whether a landing page is too heavy before deeper speed and Core Web Vitals diagnostics.

Performance reviews

Find which asset categories increase page weight and where optimisation work should start.

Migration QA

Compare page-weight signals after redesigns or deployments to catch heavier assets early.

Client reporting

Show page-weight issues, request counts and compression opportunities before full performance work.

Frequently asked questions

Page Size Checker FAQs

Clear answers about page weight, transferred size, compression and how this tool fits into performance diagnostics.

Page size is the total amount of data a webpage transfers when its HTML, CSS, JavaScript, images, fonts and other resources are loaded or discovered.

Enter a public page URL and click Run Size Check. Wranker measures the page and shows total size, request count, asset breakdown, compression status and the largest detected resources.

As a public guideline, a page up to 1.5 MB is treated as Good, 1.5–3 MB as Warning and more than 3 MB as Poor. Final thresholds may vary by page type, business goal and performance requirements.

Large images, oversized JavaScript bundles, unused CSS, too many fonts, third-party scripts, ads, embeds and missing compression are common causes of heavy pages.

No. Page Size Checker focuses on asset weight and requests. Use Core Web Vitals Checker or Page Speed Insight Checker for LCP, INP, CLS and performance diagnostics.

Transferred size is the amount of data downloaded by the browser after compression is applied. It is often smaller than uncompressed size.

Uncompressed size is the original size of a resource before gzip, Brotli or other compression is applied.

Yes, for most reviews. Third-party scripts, fonts, analytics, ads and widgets contribute to real page weight and should be included when evaluating the loaded page.

Some resources may be blocked, missing size headers, hidden by CORS restrictions, affected by redirects, protected by bot systems or unavailable in fast fetch mode.

Yes. Where export is available, you can download the public result as CSV or PDF.

Tool CTA

Check how heavy your page is

Enter one page URL to measure total page weight, request count, asset breakdown, compression status and the heaviest detected resources.

Free Web Page Size Checker & Performance Analyzer | WRanker