Page Size Checker

Discover the exact weight of any web page and every resource it loads. Our Page Size Checker breaks down the total size of HTML, CSS, JavaScript, images, fonts, and third-party resources so you can identify what is bloating your pages and slowing down load times. Page weight is one of the most fundamental factors affecting both user experience and search engine performance. A lighter page loads faster, consumes less bandwidth, and delivers a better experience on every device and connection speed. Use this tool to audit, optimize, and monitor your page weight.

Key Features of Our Page Size Checker

Complete Resource Breakdown

View the size of every individual resource loaded by your page, categorized by type: HTML, CSS, JavaScript, images, fonts, and third-party scripts. Identify exactly which files contribute most to your total page weight.

Compressed vs Uncompressed Sizes

See both the transfer size after server compression and the decoded size the browser must process. This dual view reveals whether your server compression is effective and where CPU-intensive decompression may be affecting rendering speed.

HTTP Request Count Analysis

Count the total number of HTTP requests your page generates during loading. Excessive requests add latency overhead that slows rendering, especially on mobile connections where each round trip introduces significant delay.

Resource Type Distribution

Visualize what percentage of your total page weight comes from images, scripts, stylesheets, fonts, and other resource categories. This distribution chart makes it immediately clear where optimization efforts should be focused.

Oversized Resource Detection

Automatically flag individual resources that exceed recommended size thresholds. The tool highlights images larger than 200 kilobytes, JavaScript files exceeding 150 kilobytes, and other resources that are disproportionately heavy.

Compression Status Verification

Check whether your server is properly applying Gzip or Brotli compression to text-based resources. Uncompressed HTML, CSS, and JavaScript files can be two to five times larger than their compressed equivalents.

Third-Party Weight Isolation

Separate the weight of third-party resources from your own first-party content. Analytics scripts, ad networks, social widgets, and tracking pixels often contribute a surprising percentage of total page weight.

Mobile Weight Estimation

Estimate how your page weight translates into real-world mobile download times across different connection speeds, from fast 5G to slower 3G connections still used in many markets worldwide.

How to Use the Page Size Checker

01

Step 1

Navigate to the Page Size Checker tool and enter the complete URL of the web page you want to analyze in the input field.

02

Step 2

Click the check button to initiate the analysis, which will load the page and measure every resource the browser downloads during rendering.

03

Step 3

Review the total page weight summary, which shows the combined transfer size and the number of individual HTTP requests made by the page.

04

Step 4

Examine the resource breakdown table to identify which categories, such as images, JavaScript, or CSS, consume the most weight.

05

Step 5

Focus on the flagged oversized resources list to find specific files that should be compressed, resized, or replaced with lighter alternatives.

06

Step 6

Implement the recommended optimizations on your server and re-check the page to verify that total weight has been reduced to acceptable levels.

Ready to Analyze?

Try Page Size Checker now — completely free, no registration required

Use Tool Now

What Is a Page Size Checker and How Does It Work?

A page size checker is an analysis tool that calculates the total file size of a web page, including all the individual resources the browser must download to fully render that page. When a visitor navigates to a URL, their browser does not simply download a single file. It downloads the HTML document, then parses it and fetches every linked resource: stylesheets, JavaScript files, images, web fonts, video files, favicons, and any third-party resources loaded by advertising, analytics, or social media scripts.

Our Page Size Checker works by requesting your URL exactly as a browser would, following all redirects and loading every resource referenced in the page source. It then measures and categorizes each resource by type and size, producing a detailed breakdown that reveals where your page weight is concentrated. The tool reports sizes in both compressed (transfer size) and uncompressed (decoded size) formats, since most modern servers deliver text-based resources using Gzip or Brotli compression.

Understanding the distinction between these measurements is important:

  • Transfer size: The actual number of bytes sent over the network. This is what affects download time and bandwidth consumption. It reflects compression applied by the server.
  • Decoded size: The uncompressed size of the resource after the browser decompresses it. This is what the browser must parse and process, affecting CPU usage and memory consumption.
  • Total page weight: The sum of all transfer sizes for every resource loaded by the page. This is the primary metric most people refer to when discussing page size.

The tool also counts the total number of HTTP requests made during the page load. Each request introduces latency, particularly on mobile connections where round-trip times are higher. A page that makes 150 individual requests will generally load slower than a page of the same total weight that makes only 40 requests, because the overhead of establishing connections and waiting for responses accumulates with each additional request.

Beyond raw numbers, the Page Size Checker identifies specific resources that are disproportionately large relative to their function. An unoptimized hero image that weighs 3 megabytes, an unused JavaScript library consuming 500 kilobytes, or a web font loading 12 weights when only 2 are used are the types of specific, actionable findings the tool delivers. This transforms abstract page weight data into concrete optimization targets.

Why Page Size Matters for SEO and Performance

Page size is the foundation upon which all other performance metrics rest. No amount of server optimization, caching, or CDN deployment can fully compensate for a page that is fundamentally too heavy. Understanding why page weight matters for SEO requires examining its cascading effect on multiple ranking signals and user experience metrics.

Direct Impact on Load Time

The relationship between page size and load time is straightforward: larger pages take longer to download. On a typical 4G mobile connection delivering approximately 10 megabits per second, a 5-megabyte page requires at least 4 seconds to download, before accounting for DNS resolution, TLS handshake, server processing, and rendering time. On slower 3G connections still common in many regions, the same page could take 15 seconds or more. Since Google considers load time a ranking factor, excessive page weight directly undermines your SEO performance.

Core Web Vitals Connection

Page weight influences all three Core Web Vitals. Heavy images and media inflate Largest Contentful Paint by increasing the download time for the largest visible element. Large JavaScript bundles increase First Input Delay and Total Blocking Time by requiring more main-thread processing. Unoptimized resources without proper dimensions contribute to Cumulative Layout Shift when they load at unpredictable times and push visible content around.

Mobile User Experience

With Google's mobile-first indexing, your mobile page weight determines your ranking baseline. Mobile users frequently operate on metered data connections where every megabyte costs money. A bloated page not only loads slowly but literally costs your visitors money, increasing the likelihood of abandonment. Research shows that the median mobile web page now exceeds 2 megabytes, yet the fastest and highest-ranking pages consistently stay well below this threshold.

Crawl Efficiency

Search engine crawlers allocate a finite crawl budget to each website. When pages are excessively large, crawlers spend more time and resources downloading each page, which reduces the total number of pages they can crawl per session. For large websites with thousands of pages, this means that new or updated content may take longer to be discovered and indexed.

Server Resources and Hosting Costs

Heavier pages consume more bandwidth and server resources. For high-traffic websites, the difference between a 1-megabyte page and a 3-megabyte page translates into significantly higher hosting and CDN costs. Optimizing page size is not just a performance improvement; it is a cost reduction strategy that pays dividends as your traffic grows.

Who Should Use a Page Size Checker?

Page size analysis is a foundational skill for anyone involved in building, managing, or optimizing websites. The following roles and scenarios benefit most from regular page weight auditing.

Front-End Developers

Developers need precise measurements to validate their optimization work. After implementing image compression, code splitting, tree shaking, or lazy loading, a page size checker provides the objective before-and-after measurements that confirm whether the changes achieved the intended reduction. It is also an essential tool during code reviews to catch resource bloat before it reaches production.

SEO Specialists

Technical SEO audits always include page weight analysis as a key diagnostic metric. SEO professionals use page size data to identify performance problems that affect Core Web Vitals, build prioritized optimization roadmaps for clients, and track the impact of technical changes on overall site performance over time.

Digital Marketing Teams

Landing pages for advertising campaigns must load quickly to maximize quality scores and conversion rates. Marketing teams use page size checkers to audit campaign pages before launch, ensuring that heavy images, unnecessary scripts, or bloated templates do not undermine advertising ROI.

E-Commerce Managers

Product pages with high-resolution images, interactive elements, and third-party integrations can easily exceed recommended page weight limits. E-commerce managers use size checking to balance rich product presentation with fast loading performance, particularly for mobile shoppers who represent the majority of e-commerce traffic.

Website Owners and Bloggers

Even non-technical site owners benefit from understanding their page weight. Knowing that a blog post weighs 4 megabytes because of unoptimized images is the first step toward fixing the problem. Page size checking gives website owners the awareness they need to make informed decisions about themes, plugins, and media handling.

Understanding Your Page Size Results

Interpreting your page size report correctly is crucial for making effective optimization decisions. Here is how to read and act on the key data points in your results.

Total Page Weight Benchmarks

As a general guideline, aim for a total page weight of under 1.5 megabytes for content pages and under 2 megabytes for media-rich pages. The median web page in 2025 weighs approximately 2.2 megabytes on desktop and 2 megabytes on mobile. However, the fastest websites that dominate search rankings consistently maintain page weights well below these medians.

Resource Category Analysis

Images typically account for 50 to 70 percent of total page weight on most websites. If your image percentage is higher than 70 percent, image optimization should be your top priority. JavaScript typically accounts for 15 to 25 percent. CSS and HTML usually account for less than 10 percent combined when properly compressed. Fonts should ideally stay under 100 kilobytes total.

Request Count Guidelines

Aim for fewer than 50 HTTP requests per page. While HTTP/2 multiplexing reduces the per-request overhead compared to HTTP/1.1, each request still introduces latency and consumes connection resources. Pages exceeding 100 requests almost always have optimization opportunities through resource consolidation, lazy loading, or removal of unused assets.

Compression Verification

If the tool shows that text-based resources like HTML, CSS, and JavaScript are not being served with compression, enabling Gzip or Brotli compression on your server is typically the single highest-impact change you can make. Compression reduces text file sizes by 60 to 80 percent with minimal server overhead.

Best Practices for Reducing Page Size

Reducing page size is a systematic process that requires attention to every resource category. The following best practices address the most common and impactful sources of page bloat.

Optimize Images Aggressively

Images are almost always the largest contributors to page weight. Use WebP or AVIF formats instead of traditional JPEG and PNG, achieving 25 to 50 percent smaller file sizes at equivalent visual quality. Resize images to match their display dimensions rather than relying on CSS to scale down oversized originals. Use responsive images with the srcset attribute to serve different sizes based on viewport width. Implement lazy loading with the loading attribute set to lazy for all images below the fold.

Minify and Bundle Efficiently

Run all CSS and JavaScript through minification tools that strip whitespace, comments, and unused code. Use tree shaking in your build process to eliminate dead code from JavaScript bundles. Consider whether large libraries can be replaced with smaller alternatives or custom code that only includes the functionality you actually use.

Enable Server Compression

Ensure that Brotli or Gzip compression is enabled for all text-based resources including HTML, CSS, JavaScript, SVG, and JSON. Brotli provides better compression ratios than Gzip and is supported by all modern browsers. Most web servers and CDNs support both compression methods and can negotiate the best option automatically.

Audit Third-Party Scripts

Regularly review every third-party script loaded on your pages. Remove scripts for services you no longer use. Replace heavy widget libraries with lighter alternatives. Load non-critical third-party scripts with the defer or async attribute, or load them only after user interaction to prevent them from inflating the initial page weight.

Optimize Web Font Loading

Limit the number of font families and weights you load. Each additional font weight adds approximately 20 to 50 kilobytes. Use font-display: swap to prevent invisible text during loading. Subset fonts to include only the character sets your content requires. Consider using system font stacks for body text and reserving custom fonts for headings only.

Implement Lazy Loading Strategically

Lazy load not only images but also iframes, videos, and heavy interactive components that appear below the fold. This ensures that the initial page weight reflects only the resources needed for above-the-fold content, dramatically reducing the perceived weight for users who do not scroll the entire page.

Remove Unused CSS and JavaScript

Modern websites built with frameworks and template libraries often include significant amounts of unused code. Use coverage analysis tools to identify CSS rules and JavaScript functions that are never executed on the page, then remove them from your production bundles. Even removing 50 kilobytes of unused CSS can improve both page weight and rendering performance.

Frequently Asked Questions

Everything you need to know about Page Size Checker

A good total page size is under 1.5 megabytes for standard content pages and under 2 megabytes for image-heavy or interactive pages. The fastest-ranking websites typically keep their pages well below the median of 2.2 megabytes. Lighter pages load faster, consume less bandwidth, and perform better in search engine rankings.

Page size affects SEO by directly influencing load time and Core Web Vitals scores, which are Google ranking factors. Larger pages take longer to download and render, resulting in slower LCP scores and potentially higher bounce rates. They also consume more crawl budget, which can delay the indexing of new content.

Unoptimized images are the most common cause of excessive page weight, often accounting for 50 to 70 percent of total size. Other frequent causes include large JavaScript bundles, unused CSS, uncompressed text resources, excessive web font weights, and third-party scripts from analytics, ads, and social media widgets.

Page size matters significantly for mobile users because mobile connections are typically slower and often metered. A heavy page takes longer to download on 4G or 3G connections and can literally cost users money on limited data plans. Google uses mobile-first indexing, so your mobile page weight determines your baseline ranking performance.

The fastest way to reduce page size is to compress images using WebP or AVIF format, enable Gzip or Brotli compression on your server, and remove unused JavaScript and CSS. These three actions alone can typically reduce total page weight by 40 to 60 percent without requiring any changes to your page design or functionality.

Page size measures the total weight of all resources downloaded to render a page, expressed in kilobytes or megabytes. Page speed measures how quickly those resources are downloaded, processed, and rendered into visible content. Page size is one input that affects page speed, but speed is also influenced by server response time, caching, and rendering efficiency.

You should prioritize checking your highest-traffic pages, landing pages, and template pages first. If your site uses consistent templates, checking one page per template type gives you representative data. For large sites, automated monitoring tools can track page weight across all pages and alert you to significant increases.

Server compression reduces the transfer size, which is the number of bytes sent over the network, but not the decoded size that the browser must process. Gzip typically reduces text file sizes by 60 to 80 percent during transfer. Brotli achieves even better compression. Both methods significantly improve download times without changing the actual file content.

Related SEO Tools

Explore other tools to improve your SEO strategy

Popular

Page Speed Checker

Test your page loading time and performance metrics

Responsive Design Checker

Test how your website looks on different screen sizes and devices

Code to Text Ratio Checker

Analyze the ratio of visible text content to HTML code