About the Page Size & Requests Checker
Every image, script, stylesheet and font a page loads adds bytes and requests. This page size checker uses a Lighthouse run through PageSpeed Insights to list each request a public page makes, with its resource type, transfer size and timing, then totals them by type and highlights the heaviest files.
The breakdown quickly shows where weight comes from: often uncompressed hero images, large JavaScript bundles, several web fonts or third-party tags such as chat widgets and trackers. Heavier pages take longer on slow mobile connections and cost visitors more data. Start with the largest files, compress or resize images, remove unused scripts and fonts, and load non-essential third-party code later.
How to use it
- Enter a public page URL.
- Review total page weight and request count.
- Check totals by resource type and sort by size.
- Optimize or remove the heaviest files first.
Frequently asked questions
What is a good page size?
There is no official limit. Lighter pages generally load faster, especially on mobile networks. Rather than chasing a number, compare your page with similar pages and focus on files that are larger than they need to be, such as oversized images and unused JavaScript.
Why are third-party requests listed?
Scripts and assets from other domains, such as analytics, ads, chat widgets and embedded videos, are part of what visitors download. They are often among the heaviest and slowest resources and are worth reviewing to see whether each one is still needed.
Is transfer size the same as file size?
Not always. Transfer size is what travels over the network, which is smaller when text files are compressed with gzip or Brotli. Resource size is the uncompressed size the browser processes. Large differences show compression is working. If both numbers are identical for CSS and JavaScript files, check whether compression is enabled on your server.