Web Page Transfer Size Checker
Measure the resources transferred during a real browser page load.
Run the web page transfer size checker
Rendered browser checkWhat web page transfer size checker helps you do
Measure the resources transferred during a real browser page load. Separate HTML, scripts, images and fonts when investigating a large transfer. A single oversized hero image may matter more than many small cached icons.
Prepare a useful input
Example input: https://example.com/ Save the original input alongside the result so another person can reproduce the check and judge whether a proposed change addresses the same page or file.
Read the result before making changes
Results depend on cache state, viewport, load timing and third-party availability. They are not field performance percentiles. Record the checked URL and observation time. Compare the evidence with the intended page behavior, then verify the affected page again after a change instead of assuming the issue is resolved.
Find the resource responsible for the weight
A page transferring five megabytes may be dominated by one image or by many scripts; the total alone does not identify the fix. Compare resource types and the largest individual transfers. Keep compressed transfer size separate from decoded resource size, because browsers download one representation and process another. A warm cache can make a repeat visit look lighter without changing the first-visit experience. Record viewport and cache conditions with the sample. After reducing an asset, verify visual quality and the network result together; deleting an essential resource is not a successful performance improvement.
Verify the result and continue
Keep a cold-load sample for comparison after changing an image or bundle. Review the resource breakdown as well as the total so a cache effect is not mistaken for an optimization. Confirm that the page still renders essential content and interactions before accepting a reduction in transferred bytes. Continue with the image optimization checker or explore the performance tool cluster.
How this tool works
Measure the resources transferred during a real browser page load. A real browser visits the public URL and records the relevant rendered or network evidence. Results represent the sampled visit and are not fabricated field metrics.
What the result does and does not establish
Results depend on cache state, viewport, load timing and third-party availability. They are not field performance percentiles.
Use this check as part of a repeatable website review. Record what you found, make a specific change and run the same check again.
Browse all toolsContent and technical review workflow