Body Tag Size Kilobytes reports the measured size, in kilobytes, of the page’s parsed body-tag content. In the current live implementation the legacy-compatible body parser captures an empty string, so this factor returns 0 for every page — treat it as an observation, not an optimization target.
| Factor ID | RG-SIZ-004 |
|---|---|
| Family | Page Size |
| Measurement | Kilobytes |
| Measured zone | Parsed body-tag content |
What it measures
This factor reports the measured size of parsed body-tag content in kilobytes. It is meant to describe how much content lives inside the page’s body region, expressed as a weight rather than a character count.
How RankGear measures it
RankGear parses the body tag from the page body, counts the UTF-16 code units in the captured value, and divides that count by 1,024 to produce a kilobyte figure. Because the legacy-compatible body parser currently captures an empty string, the counted length is zero, and this factor therefore returns 0 for every page under the live implementation.
body_tag_size_kb = utf16_length(parsed_body_content) / 1024
// legacy body parser captures "" → utf16_length = 0 → result = 0 for every pageHow to optimize it
Do not alter a page to try to move this factor while the live implementation is constant — it will read 0 regardless of what the body actually contains. Use RankGear’s other size and content factors to evaluate the real weight of a page’s body, and treat this value as a fixed observation rather than a lever.
Important considerations
- The measurement divides a UTF-16 length by 1,024; it is not a network-transfer byte measurement, so it will not match the transferred size a browser or CDN reports.
- Compare the factor with ranking and user-performance evidence rather than assuming larger or smaller body content is always better — this is a descriptive signal that relates to a page within a measured result set, not a cause of ranking, and no factor guarantees a position.
- Minification, compression, external resources, and runtime behavior may not be reflected in this value.
- Preserve useful content and functionality while improving efficiency; do not strip meaningful body content chasing a smaller number.
Related factors
Part of the Factors reference · how RankGear measures · glossary.