Page size, also called page weight, is the total number of bytes a browser has to download to render your page, and it is one of the biggest levers you have over load time. The total weight in KB or MB and the number of HTTP requests both push directly on how fast a page feels and on your Core Web Vitals scores. Here is how to measure both and where to cut.
Why page size and requests matter
Every byte and every request costs time. A heavy page makes the browser fetch, parse, and paint more, which delays the moment a visitor sees and can use your content. Two numbers tell most of the story:
- Total page weight: the combined size of HTML, CSS, JavaScript, images, fonts, and everything else.
- Request count: how many separate files the browser has to fetch. Each request adds connection and round-trip overhead.
Both feed into Core Web Vitals. A bloated page tends to score worse on Largest Contentful Paint and can hurt interactivity too. In almost every audit, images are the heaviest part of the page by a wide margin, followed by JavaScript and third-party scripts.
What the analyzer reads
The Page Size & Request Analyzer works from a HAR file, the request log your browser can export from its DevTools Network tab. It does not fetch a URL for you. You capture the page yourself, export the HAR, and drop it in. The tool then reads that file and shows total page weight, request count, and a full breakdown by resource type and by domain, so you can see exactly which files and which third parties are weighing you down.
Because it analyzes the export you provide rather than crawling the live site, the numbers reflect the real session you recorded, including cache state and any scripts that actually ran.
How to analyze your page weight
- Open your browser DevTools, go to the Network tab, reload the page, then right-click and export as HAR.
- Open the Page Size & Request Analyzer and drop in the HAR file.
- Read the total page weight, request count, and the breakdown by type and domain to spot the heaviest offenders.
Everything runs entirely in your browser. The HAR file never leaves your device.
Where to cut weight
Once you know the breakdown, the fixes are usually clear. Compress and resize images, since they are almost always the heaviest items. Minify CSS and JavaScript. Lazy-load offscreen images so they do not block the initial paint. Cut or defer third-party scripts, which add both bytes and requests. Bundling related files reduces request count.
Rough targets to aim for: keep total page weight under about 1 to 2 MB where you can, and keep request counts modest rather than in the hundreds. These are guidelines, not hard rules, but a page well inside them tends to load fast and score well.
Related tools
- Gzip & Deflate Size Calculator: see how much smaller a file gets once compressed.
- .htaccess Gzip Compression Generator: enable compression on Apache servers to shrink transfer size.
- Nginx Gzip Configuration Generator: do the same on Nginx with a ready-to-paste config.
Export your HAR, drop it in, and let the breakdown tell you exactly what to trim.