HTML size, extracted text and transferred data
Use these measurements when investigating a specific content or performance need. A large saved file alone is not an SEO problem requiring reduction.
What the findings mean
This measurement describes the saved HTML and extracted text available to the inspection, or why a size could not be measured. It can distinguish bytes in a saved UTF-8 file from characters or words in extracted text.
What the evidence cannot establish
Saved-file size is not the amount transferred over the network. Compression, response encoding and resource delivery require separate network measurements. The size check does not use a generic large-file threshold to produce an SEO failure, and missing source material prevents meaningful comparisons.
How to prioritise
Use these measurements when investigating a specific content or performance need. A large saved file alone is not an SEO problem requiring reduction.
What to do
- Read which metric the result reports and which saved material it covers.
- For an investigation of HTML overhead, compare the same source and measurement method. For text quality, inspect the extracted main text and actual reader need.
- If the goal is faster loading, measure network transfer and loading behaviour separately before choosing a change.
- Remove only code or text that is genuinely unnecessary, preserving useful content, structure and accessibility support.
Check the result
Repeat the same measurement with the same method and explain the change in that metric. Do not describe a smaller saved file as verified lower network transfer without measuring transfer separately.
Need help with a particular finding?
Contact us →