Run results for: textcontent vs nodevalue vs content:after

Run details:

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36

Browser: Chrome 131

Operating system: Windows

Device Platform: Desktop

Date tested: one year ago

Test name	Executions per second
textcontent	4801942.0 Ops/sec
nodevalue	4837433.5 Ops/sec
setAttribute	2221605.2 Ops/sec

Script Preparation code:

var newBody = document.createElement("div");


for (let i; i < 1000; i++) {
	var foo = document.createElement("div");
  	foo.innerText="abc";
	newBody.appendChild(foo);
}

Tests:

textcontent
var case1 = document.getElementsByTagName("div"); for (var i = 0; i < case1.length; i++) { case1[i].textcontent="ABC"; }
nodevalue
var case2 = document.getElementsByTagName("div"); for (var i = 0; i < case2.length; i++) { case2[i].nodevalue="ABC"; }
setAttribute
var case3 = document.getElementsByTagName("div"); for (var i = 0; i < case3.length; i++) { case3[i].setAttribute('data','ABC'); }

Run results for: textcontent vs nodevalue vs content:after

textcontent

nodevalue

setAttribute