That’s a major difference, I would say, as uhtml never clone again anything for the same container/rendered element, and what you see is literally what you get, nothing is stripped out, nodes reachable via [name="thing"] out of the box for CSS, so it plays well with the rest of the Web stack.

Once again, uhtml is basically lighterhtml in a nutshell, without any of the lighterhtml extra features, but hey … size might matters to many.

Possible improvements is to provide a parser to have something similar to lighterhtml in less than 3K, hopefully around 2K, but that’s a whole new challenge.