Head Size Kilobytes reports how large a page’s parsed <head> content is, expressed in kilobytes. In the current live implementation the head parser captures an empty string, so this factor returns 0 for every page — read it as a fixed observation, not a lever to move, and it relates to position within a measured result set rather than causing any ranking.
| Factor ID | RG-SIZ-009 |
|---|---|
| Family | Page size |
| Measurement | Kilobytes |
| Measured zone | Parsed head-tag content |
What it measures
This factor reports the measured size of parsed head-tag content in kilobytes. It is a size signal for the document’s <head> region — the block that holds metadata, title, links, and inline styles or scripts — rather than a measure of the visible body or the full page.
How RankGear measures it
RankGear parses the head tag from the raw rendered HTML, counts the UTF-16 code units in the captured value, and divides by 1,024 to convert to kilobytes. This is a length-based measurement, not a network-transfer byte count. Note that the legacy-compatible head parser currently captures an empty string, so in the live implementation this factor returns 0 for every page.
head_size_kb = utf16_code_units( parsed_head ) / 1024
current live parser: parsed_head = "" => head_size_kb = 0 (every page)How to optimize it
Do not alter a page to optimize this factor while the live implementation returns a constant 0. There is no page change that will move it, and it is not a target to chase. For decisions about head-region weight, use the specific metadata, CSS, JavaScript, and resource measurements instead, and treat this value as an observation about the current parser, not a goal.
Important considerations
- RankGear divides UTF-16 length by 1,024; this is a code-unit length measurement, not a network-transfer byte measurement.
- The legacy-compatible head parser currently captures an empty string, so the live factor returns 0 for every page.
- Compare this factor with ranking and user-performance evidence rather than assuming larger or smaller is always better.
- Minification, compression, external resources, and runtime behavior may not be reflected in the value.
- Preserve useful content and functionality while improving efficiency.
- Correlation is not causation: this measurement relates to position within a measured result set and is a prioritization signal, not a lever that makes a page rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.