My intuition is that it's uncommon for web content to actually care about the Attribute nodes that can be obtained via getAttributeNode. Since we create one Attribute per content attribute during parsing, this could lead to nontrivial memory used on nodes that might never be accessed. If we only stored the content attribute values, and constructed Attribute nodes lazily instead, we might observe lower memory usage and slightly more efficient parsing.